Advertisement IC Markets

Server Time vs Local Time: Avoiding Prop Rule Mistakes Around the Daily Reset

Navigate the rules, daily drawdown limits, and consistency guidelines of prop trading firms. Discuss how to pass funded account challenges using scalping strategies.
Post Reply
FXS Prop Desk
Posts: 1689
Joined: Wed Oct 07, 2026 9:52 am

Server Time vs Local Time: Avoiding Prop Rule Mistakes Around the Daily Reset

Post by FXS Prop Desk »

Most prop rules — daily loss reset, trading days, news windows — refer to server time, and server time is rarely your local time.

Typical setups:
  • Many MT servers run on GMT+2 / GMT+3 (aligned so that the daily candle closes at New York 17:00).
  • Some firms reset the daily limit at midnight CE(S)T, others at 17:00 New York.
  • Daylight-saving changes in the US and Europe happen on different dates, so for a few weeks a year the offset shifts by an hour.
Mistakes this causes:
  • Trading a "new day" that is still the old day for the firm, so a loss counts against an already damaged daily limit.
  • Counting a trading day that the firm does not count.
  • Misjudging a news window when the calendar is in a different time zone.
Simple fix: put a second clock with server time on your chart or desk, and add the reset time to your trading plan.

When does your firm's daily reset happen in your local time?
FXS Official Team | The Idea Lab & Strategy
Recommended broker for automated trading & scalping IC Markets
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Server Time vs Local Time: Avoiding Prop Rule Mistakes Around the Daily Reset

Post by Shadow Trader »

This year the mismatch week falls between 25 October, when Europe goes back, and 1 November for the US. On a server pinned to the New York close, midnight server time moves from 22:00 London to 21:00 London for that week, then back again.

A firm that resets at midnight Central European time stays at 23:00 London all year, because both clocks shift together. So two accounts that are normally an hour apart sit two hours apart for that week.

The detail that bites more than the hour itself is the snapshot. Several firms set the daily baseline from the higher of balance and equity at reset, so 300 dollars of floating profit at midnight raises the bar and can turn a normal pullback into a breach.

I close or flatten anything open in the last 15 minutes before reset for that reason. It costs the odd good trade.

Trading day counts have a similar edge case. A trade opened at 23:55 server and closed at 00:05 usually counts on the day it opened, while some firms count it only on the close date.

What time zone does your firm's news window use? Mine is quoted in server time, which is not what my calendar shows.
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Server Time vs Local Time: Avoiding Prop Rule Mistakes Around the Daily Reset

Post by Shadow Trader »

Sunday is another place the server clock changes the count. On a GMT+2 or GMT+3 server the week opens at midnight Monday server time, so there is no Sunday bar at all, but a firm whose server runs on GMT shows a short Sunday session from 22:00.

A trade placed in that window can count as a trading day on its own. That sounds helpful for minimum day rules, yet it also splits a Sunday loss and a Monday loss across two daily limits.

Exported history is the next thing to check. The platform statement uses server time, while the firm's breach email may quote UTC or its own head office time, so matching a breach to a specific trade takes some care.

When I review a day I convert everything to one zone before reading it. I picked UTC because it never shifts for daylight saving.

The phone clock caught me once as well. Travelling across a border moved my reset reminder by an hour, and I now read the reset time off the platform's server clock instead.

Mine only states the reset in New York time. Does your firm publish its server offset anywhere in the rules, or did you have to work it out from candle times?
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Server Time vs Local Time: Avoiding Prop Rule Mistakes Around the Daily Reset

Post by Shadow Trader »

Not all delays come from the trader's own connection. Broker servers can become overloaded, causing delayed quotes, slow order processing, or temporary disconnections. These events often coincide with heavy trading activity, such as major news or sudden market stress.

Stale quotes are particularly dangerous. A price that appears current but is a second or two old can lead to entries at prices that no longer exist, resulting in requotes, rejections, or poor fills.

Monitoring the timestamp of the latest tick relative to the local clock reveals delays. Many platforms display a tick time or allow adding it to the chart. Large gaps between consecutive ticks during active periods suggest problems. Keeping a record of incidents, with times and details, supports complaints and broker comparisons. Where delays occur repeatedly in the same circumstances, the venue may not be suitable for a speed-dependent strategy. Having an alternative broker account ready provides a fallback when conditions deteriorate.
Post Reply