Advertisement IC Markets

The server time confusion that ruins session stats

Optimize MetaTrader 4, MetaTrader 5, cTrader, and TradingView for speed. Discuss Level II Market Depth (DOM), custom hotkeys, and volume indicators.
Post Reply
Amanhasnoname
Posts: 1506
Joined: Fri Oct 30, 2026 9:45 am

The server time confusion that ruins session stats

Post by Amanhasnoname »

Most retail brokers run server time on something like GMT+2 or GMT+3, shifting with daylight saving in New York terms. That sounds harmless until a trader tags trades by session and finds out half the data is filed in the wrong bucket.

A 'London open' trade at 08:00 London time might show up as 10:00 or 11:00 on the platform, depending on the season. When both the US and the UK change clocks on different weekends, there are a few weeks each year when the gap between server time and local sessions is off by an extra hour.

That can create phantom findings, like a profitable window at 15:00 that is really just the NY open mixed with the end of London.

The cure is boring. Convert everything to UTC before analysis, and record the offset in use whenever a journal entry is made. Do not trust the platform clock for anything except trade order.

A single wrong offset can make a good session look bad, or hide a leak.

Has a time zone mistake ever distorted a conclusion from your journal or backtests?
Recommended broker for automated trading & scalping IC Markets
Post Reply