forex-scalping.com

Convert Broker Server Time to Real Sessions

Scenario: your broker's platform shows server time as GMT plus 2 in winter and GMT plus 3 in summer, a common setup designed so that the daily candle closes at New York 5 p.m. You want to know where key moments appear on your charts.

Daily close. In winter, New York 5 p.m. is 22:00 UTC. Add 2 hours for the server: 00:00. In summer, New York 5 p.m. is 21:00 UTC. Add 3 hours: 00:00. So the daily candle opens at 00:00 server time all year.

London open. In winter, London opens at 08:00 local time, which is 08:00 UTC. On the server, that is 10:00. In summer, London is on British Summer Time, so 08:00 local is 07:00 UTC, and with the server at GMT plus 3, it is 10:00 again.

So the London open appears at 10:00 on your chart throughout the year, because the server shifts with the same seasons.

Now test the assumption with a broker that uses fixed GMT plus 2 year-round. In summer, the London open at 07:00 UTC would appear at 09:00, and the daily close at 21:00 UTC would appear at 23:00. Candles would be offset by an hour relative to the winter picture.

This is why you should confirm how your broker handles daylight saving, because session boxes and indicators based on server time shift if it does not.

Exercise: find the time your platform shows for the daily candle open, and calculate whether it follows New York close.

Good guide. For anyone reading this from Hong Kong or Singapore, there is an extra twist: we never change our clocks, so every shift on the broker side shows up for us.

With a server on New York close (GMT+2 in winter, GMT+3 in summer), our local open of the Tokyo session moves by one hour on the server chart twice a year, even though nothing changed in Tokyo. And in the mismatch weeks it gets messier. In March the US moves about three weeks before Europe, and in autumn Europe moves back one week earlier, like this week, with London already on GMT and New York not until 1 November.

What helped us is keeping session filters in UTC and converting to server time with a dated offset table, rather than hard coding server hours. Then the mismatch weeks look after themselves.

An end-of-day statement shows profit for the day. A trader's own log shows a different number. Neither is wrong. They use different day boundaries.

Broker statements typically cut at 5pm New York, or at server midnight. A trader's log might use local midnight or the start of the first session. Trades near the boundary fall into different days.

For scalpers who trade at rollover or near it, the mismatch affects daily summaries. A winning trade at 4:58pm and a losing trade at 5:02pm land on different days in the statement but the same day in a local log.

More serious issues arise with end-of-month reports, tax records, and performance tracking. Reconciling the platform's history with a personal spreadsheet can produce differences in timing that look like errors.

Some platforms export history in server time. Others convert to the local time of the computer. Mixed sources lead to confusion.

A habit that prevents trouble: record the time zone used in every export and keep a consistent one for analysis. Convert everything to a single reference, such as UTC.

Which time zone does your journal use, and does it match the broker's statement?

The logic is right for most of the year, but there's a gap worth knowing about. Brokers using this setup usually switch their server clock on the US daylight saving dates, while London switches on UK dates, which differ by a few weeks. In 2026, the UK moved clocks back on 25 October and the US on 1 November. During that week, with London back on GMT and the server still at GMT plus 3, the London open fell at 11:00 on the server rather than 10:00, and the same happens in the March gap. In 2027, the gaps fall between 14 and 28 March, and between 31 October and 7 November. Session indicators based on server time will be an hour off during those weeks.

For members here in West Africa, converting to WAT is useful. With both the UK and US now on winter time, the London open at 08:00 UTC is 09:00 WAT, and the New York daily close at 22:00 UTC is 23:00 WAT. US data releases at 8:30 a.m. New York time come out at 14:30 WAT. In summer, these all move an hour earlier in WAT, since Nigeria doesn't change its clocks: the London open becomes 08:00 WAT and the daily close 22:00 WAT. Knowing the local time of these moments helps plan trading hours and avoid the rollover spread widening.

The point about fixed offset brokers matters for chart analysis. A broker at a fixed GMT plus 2 year round will show the daily candle closing at 23:00 server time in summer, which means each daily candle in summer covers a slightly different window from those in winter. On some brokers, this also creates a small Sunday candle, which can distort daily indicators like moving averages and ATR. Brokers aligned to the New York close produce five daily candles a week, which most traders prefer. Checking for a Sunday candle is a quick way to tell which type your broker uses.

Finding the daily candle open time, as the exercise suggests, is easy: look at the time stamp of the first hourly candle of any day on the platform. If daily candles open at 00:00 server time and the server follows New York, the alignment is correct. If not, indicators and session boxes may need adjusting. Has anyone here been caught out by a server time difference, for example a session indicator that shifted by an hour after a clock change? It would be useful to hear how you noticed and how you corrected it.