Inside this article

Valid trading days in a challenge: counting trades, dates and time zones correctly

“Five trading days” does not necessarily mean five orders, five sessions at a screen or five dates in your local calendar. The exact criterion belongs to the rules of a particular edition. Some challenges count a date with at least one closed trade; others use account activity within a time window, a minimum volume or a recorded outcome. Before planning a Disciply Trading Challenge, read the current definition of a valid day in the rules. If it is unpublished or unclear, do not assign your own meaning to the counter.

The Prepare for the Challenge page directs readers to check the round calendar, its terms, valid days and leaderboard criteria. This guide explains how to verify a count without asserting an official minimum or claiming that a prize competition is open. A public test using simulated trades and a possible future official contest have to be assessed as different editions. Sample leaderboard figures do not certify that any participant has earned a valid day.

What event makes a day valid?

Find four elements in the applicable text: required event, reference clock, edition window and data source. “At least one trade” might mean an opening, a closing, an executed deal or an outcome above a threshold. Moving a stop does not automatically create a new trading day. An order submitted but never filled is not a position. A position opened on one date and closed on the next might count once on a date different from the one you expected, or follow a special rule that cannot be inferred from a visual history alone.

Write down the exact definition and version before counting. If the program asks for activity “during the day,” determine whether it uses broker server time, UTC or a local zone. If it requires a closed trade, use the provider's execution timestamp for the close, not the moment you opened your journal page. Similar wording at another prop firm is not evidence that the two programs share a rule.

UTC, Italian time and the MT5 server

Your phone and MT5 can show different dates for the same event. For example, a close at 23:30 UTC on November 5 is 00:30 on November 6 in Italy during standard time. Under a UTC rule, that close belongs to November 5, even though an Italian calendar shows November 6. The broker server may use yet another clock. Counting from phone date headings can therefore move a trade between days without any change in the transaction.

Preserve each original timestamp, its stated zone and the conversion applied. Do not always add or subtract a fixed hour: daylight saving changes during the year. A robust record keeps UTC date and time as the technical reference and displays local time separately. If the program explicitly uses broker server time, document the server offset for that period. The daily loss reset and the valid-day boundary may be different; do not assume they coincide.

Three cases with different answers

Case A: you open and close three positions on November 5 within the same rule-defined day. If the rule says “at least one eligible close per date,” this is one day, not three. Case B: you open a trade on November 5 and close it on November 6. If the closing date counts, only November 6 may qualify; a rule based on executed opening activity could give another answer. Case C: one position closes at 23:58 UTC and another at 00:03 UTC. They fall on two UTC dates five minutes apart. A UTC-date rule may see two days, but do not assume that short trades opened just to increase a counter meet substantive or anti-abuse conditions.

These are hypothetical illustrations, not Disciply's current official rules. Their purpose is to reveal the questions you must ask of the actual text. If a program requires net profit, minimum holding time or a minimum number of trades, add those columns; if it does not, do not invent official requirements. Group only eligible events by date in the prescribed time zone and count distinct date keys.

Build a checkable record

Make a row for each relevant deal or transaction with account, ticket, symbol, event type, original timestamp, UTC time, rule-defined date, volume and result when required. Add a “criterion met” column explaining why, instead of a bare yes. If several deals belong to one order or partial close, reconcile them before grouping. MT5 distinguishes orders, deals and positions; equating the number of history rows to the number of valid days is a category error.

Record account assignment time and the round window as well. A trade before the start or on a different account does not become eligible merely because it appears in the same terminal. Keep deposits, withdrawals, adjustments and broker credits separate from trade results. When data are missing because of a disconnection, mark “requires review” instead of inventing an eligible date or silently dropping it. A dashboard counter is something to compare with provider records, not self-sufficient proof.

A day count does not replace risk controls

A day that counts for participation could still violate a loss limit or another edition rule. Before placing an order simply to “make the day,” compare equity, daily reference, total floor and other open positions. The prop challenge planner models limits and drawdown using manual inputs; it does not decide whether a day is officially valid. The lot and risk calculator can estimate size after you verify contract, pip, conversion and broker costs. Neither tool justifies increasing risk to complete a count.

If a hypothetical edition requires five separate dates and your table shows four, the appropriate step is to verify a fifth under the actual rules, rather than multiply orders on the fourth. If a profit target has already been reached, trading solely for a day requirement introduces extra risk that needs assessment. A target and a valid-day count may be separate conditions.

Before calling a result final

Compare your calculation with the personal Challenge page and provider history. Record time-zone differences, partial fills, missing intervals and the rule version. If the count still differs, ask support with ticket references and timestamps without posting credentials or private information in Disciply Network. A public leaderboard labelled as a preview cannot settle a dispute about an actual account.

The method requires a written definition, a consistent clock, eligible events and distinct dates inside the round window. This educational guide does not certify unpublished criteria, entry, awards or returns. Always consult the edition's current status and rules before participating.