Server time versus your own clock
Posted: Fri Oct 30, 2026 11:40 pm
A surprising number of "the setup stopped working" complaints turn out to be a time offset problem. Broker servers usually run on GMT+2 or GMT+3 with a daylight saving shift that follows New York rather than London. That detail matters twice a year, because the US and Europe change clocks on different weekends.
For about two or three weeks in March and again in late October or early November, the gap between server time and local time is different from what it normally is. Anyone who built rules around "the 10:00 bar" or "the first five minutes after the London open" can find that the bar has quietly slid an hour relative to the real market event.
The same applies to indicators that mark session boxes or Asian range highs. If the script assumes a fixed offset, the box is drawn at the wrong hours during those weeks, and the range it reports contains the wrong data.
Even a lot of experienced scalpers treat the time axis as fixed. It isn't. Time zones, brokers' own conventions, and platform settings all move independently.
A quick sanity check works well: open the chart on the day of the data release, look at where the spike actually printed, and compare it to the published release time. If they line up, the offset is right. If they don't, everything built on session timing is off.
There's a quick way to catch this in the act. On a day when the clock changes in one region but not the other, open a chart with session boxes drawn and compare the box edges with the actual first spike of the London open. If the spike lands a full hour before or after the box, the script is still on the old offset.
Scripts that hard-code hours are the usual culprits, while ones that read the broker's GMT offset from the platform adapt on their own.
Has a clock change ever shifted a setup on you without you noticing straight away?
For about two or three weeks in March and again in late October or early November, the gap between server time and local time is different from what it normally is. Anyone who built rules around "the 10:00 bar" or "the first five minutes after the London open" can find that the bar has quietly slid an hour relative to the real market event.
The same applies to indicators that mark session boxes or Asian range highs. If the script assumes a fixed offset, the box is drawn at the wrong hours during those weeks, and the range it reports contains the wrong data.
Even a lot of experienced scalpers treat the time axis as fixed. It isn't. Time zones, brokers' own conventions, and platform settings all move independently.
A quick sanity check works well: open the chart on the day of the data release, look at where the spike actually printed, and compare it to the published release time. If they line up, the offset is right. If they don't, everything built on session timing is off.
There's a quick way to catch this in the act. On a day when the clock changes in one region but not the other, open a chart with session boxes drawn and compare the box edges with the actual first spike of the London open. If the spike lands a full hour before or after the box, the script is still on the old offset.
Scripts that hard-code hours are the usual culprits, while ones that read the broker's GMT offset from the platform adapt on their own.
Has a clock change ever shifted a setup on you without you noticing straight away?