Forex Trading Sessions: Local Time, DST and MT4 Server Time

Documentation checked: 13 October 2026. The dated examples use the published 2026 clock-change rules. Session windows are planning conventions; the broker's instrument schedule determines when your account can trade.

A London setup can appear an hour late after a clock change even though the market followed the same local routine. Before changing the strategy, check which clock defined it. London business time, your wall clock and an MT4 candle timestamp can all describe the same moment with different numbers.

This guide shows how to translate between them, with a worked example for the UK–US daylight-saving mismatch in October 2026. The aim is a repeatable trading schedule and a journal you can compare across seasons. Knowing the session alone does not establish a profitable entry.

Forex Sessions and DST headline beside clocks, a trading desk and an illuminated globe. — AI-generated editorial illustration. The clocks and screen graphics are symbolic, not live session data.

What a forex session actually means

Spot foreign exchange is an over-the-counter market with many venues and counterparties. It does not have one worldwide opening bell. The BIS overview of the FX market describes this distributed structure. Retail access also depends on the contract and trading service supplied by the broker.

Names such as Sydney, Tokyo, London and New York describe broad regional business-hour windows. OANDA's session guide uses those four centres. Different session clocks can choose slightly different boundaries, so an apparent disagreement may be a difference in convention rather than a timezone error.

Separate three questions: which financial centres are active, whether your broker accepts orders, and whether current conditions fit your method. A coloured “open” session box answers only the first. It cannot establish that a particular symbol is tradable or that its spread is suitable.

For example, OANDA's own operating-hours page publishes a daily forex break and specific weekly opening and closing times. Those are that provider's conditions, not a universal forex timetable. Check the exact instrument for holidays, maintenance and temporary changes.

Use local session names and a dated UTC conversion

Write a city timezone next to each session rule. “London 08:00” means something different from “08:00 UTC” during British Summer Time. Likewise, New York time means the local civil clock; the abbreviation EST specifically means standard time, not every month of the year.

NIST lists New York's Eastern offsets as UTC−5 in standard time and UTC−4 in daylight time. BMKG identifies WIB as UTC+7. Jakarta does not make a seasonal DST adjustment, so a foreign clock change still moves the session on a WIB timetable.

The following table defines this article's model explicitly: Sydney 08:00–17:00, Tokyo 09:00–18:00, London 08:00–17:00 and New York 08:00–17:00, each in its own local time. These are illustrative business-hour windows, not regulated market hours or a claim that every session tool uses the same settings.

Planning windows for the local business day Monday, 2 November 2026
Centre	Local window	Offset that day	UTC window	WIB window
Sydney	08:00–17:00	AEDT, UTC+11	21:00 Sun 1 Nov–06:00 Mon 2 Nov	04:00–13:00 Mon 2 Nov
Tokyo	09:00–18:00	JST, UTC+9	00:00–09:00 Mon 2 Nov	07:00–16:00 Mon 2 Nov
London	08:00–17:00	GMT, UTC+0	08:00–17:00 Mon 2 Nov	15:00 Mon 2 Nov–00:00 Tue 3 Nov
New York	08:00–17:00	EST, UTC−5	13:00–22:00 Mon 2 Nov	20:00 Mon 2 Nov–05:00 Tue 3 Nov

The date labels matter. Sydney's Monday morning falls on Sunday in UTC, while New York's Monday afternoon extends into Tuesday in WIB. A journal that records only “04:00” cannot reliably identify the session or even the intended trading day.

Japan's NICT explains JST's nine-hour UTC offset. Sydney follows New South Wales rules: the NSW government lists UTC+10 standard time and UTC+11 daylight time. Its annual rule starts DST on the first Sunday in October and ends it on the first Sunday in April. Do not apply a northern-hemisphere “summer” switch to Sydney.

For day-to-day orientation, open the FOREXSIGNAL24 Forex Market Sessions tool. Its page describes indicative business-hour sessions with local DST adjustment and explicitly excludes holidays and broker breaks. Use it alongside your instrument schedule. A Sydney business window can begin before your provider's weekly trading service opens.

Why 26–30 October 2026 has a different London–New York overlap

The UK and United States change clocks on different Sundays. GOV.UK confirms the UK change on 25 October 2026, when 02:00 BST returns to 01:00 GMT. NIST gives 1 November 2026 as the US end of DST, at 02:00 local daylight time.

For New York, that transition is 06:00 UTC, or 13:00 WIB, on 1 November. Someone reading at 09:00 WIB that Sunday is still four hours before it. The trading-week table for 2–6 November uses the post-change offset; it should not be applied to the preceding Friday.

Calculated overlaps using the same 08:00–17:00 local model in both cities
Business dates	London in UTC	New York in UTC	Overlap in UTC	Overlap in WIB
19–23 Oct 2026	07:00–16:00	12:00–21:00	12:00–16:00	19:00–23:00
26–30 Oct 2026	08:00–17:00	12:00–21:00	12:00–17:00	19:00–00:00 next day
2–6 Nov 2026	08:00–17:00	13:00–22:00	13:00–17:00	20:00–00:00 next day

The five-hour middle row follows from those chosen windows and the different change dates. It is not a forecast of five hours of strong liquidity. Moving the assumed London close changes the overlap length; a news event can change trading conditions within any of the rows.

Consider a method that observes only London's first hour. On 23 October, its 08:00–09:00 London window converts to 14:00–15:00 WIB. On 26 October it converts to 15:00–16:00 WIB. Keeping the old WIB alarm would silently test a different hour. When following a time-based method such as our London-open setup guide, retain the original observation window in the rule sheet and convert it for each date.

The same issue affects economic-calendar entries. A hypothetical event scheduled for 08:30 New York time converts to 19:30 WIB while New York uses EDT, but 20:30 WIB under EST. Read the event's own date and timezone setting; do not reuse a screenshot from a different month.

Find the MT4 server offset instead of assuming one

MT4 server time is not automatically London time, your computer time, or a universal GMT+2/GMT+3 schedule. The timestamp comes from the connected trading server. A correct conversion for one account can be wrong for another, and a provider may change its offset seasonally.

On desktop MT4, open View → Market Watch, or use Ctrl+M. MetaQuotes documents the quote-time field alongside Bid and Ask. Compare a freshly updating quote time with a reliable UTC clock, recording the date as well as the hour. Do this during an active, connected market rather than from a stale weekend display.

Select a symbol that is receiving fresh quotes and note the connected server name.
Record its server timestamp and UTC as close together as practical. A few seconds of observation delay is not a timezone change.
Subtract UTC from the server time, including any date difference.
Check that offset against the provider's published server-time policy and repeat after its announced change date.

As a hypothetical check, suppose a fresh quote is stamped 14:05:10 server time while a synchronized clock shows 12:05:10 UTC on the same date. The observed server offset is +2 hours. The matching WIB time is 19:05:10. This observation does not prove that the server used +2 in August or will use it next March.

What the MQL4 clock functions do

TimeCurrent() returns the last known server time. In an OnTick handler it uses the handled tick; in other handlers it can reflect the latest quote for another symbol in Market Watch. It is not an independent wall clock that advances normally without incoming quotes.

TimeLocal() uses the computer's local time, while TimeGMT() calculates GMT using the computer's clock and timezone rules. A wrong computer setting can therefore corrupt an offset calculation. In Strategy Tester, MetaQuotes documents simulated-time behaviour for these functions; a live offset-detection shortcut cannot simply reconstruct historical server offsets.

Build a schedule that survives a clock change

Define the strategy's reference first. “Observe London's first hour” should stay anchored to London civil time. “Evaluate the 08:00 UTC candle” should stay anchored to UTC. Those are different specifications, and neither should be rewritten merely because the local alarm moved.

Suppose the first rule applies on 2 November and the server offset has been verified as UTC+2. London's 08:00–09:00 becomes 08:00–09:00 UTC, 10:00–11:00 server time and 15:00–16:00 WIB. Enter those labels in the plan before marking the chart. If the method instead refers to a server candle, preserve that original definition until you deliberately revise and retest it.

A short checklist before the trading week
Check	Record	Why it matters
Rule	Session city or fixed UTC window	Prevents silently changing the tested method.
Date	Business date and timezone offset	Resolves seasonal changes and midnight crossings.
Broker	Server name, observed offset and symbol hours	Separates the chart clock from actual order availability.
Events	Release time converted for that date	Keeps the observation window distinct from news risk.
Conditions	Current spread and your written limits	A correct time does not make every trade suitable.

Choose a window you can follow consistently. If your available hour no longer overlaps the tested window after DST, document the missed opportunity rather than relabelling a different hour as the same session. A sustainable schedule is more useful than a wide timetable that encourages constant monitoring.

Keep session comparisons consistent in the journal

Record the original server timestamp, its verified offset, the converted UTC timestamp and the session definition. The MT4 trading-journal guide provides the wider review workflow. Add the timing evidence to your notes without replacing the original broker record.

When reviewing “London trades”, compare the same local window, pair and setup version. Keep clock-change weeks identifiable. A change in results could reflect different hours, transaction costs or market conditions; the session label alone cannot identify the cause. Small subgroups also make a strong-looking average easy to overinterpret.

Different server boundaries can group the same underlying price sequence into different H4 or daily candles. That matters when a rule uses candle opens, highs or closes. The MT4 backtesting guide explains why data and rule definitions need to be preserved. Record timezone assumptions with the test instead of shifting historical candles by today's offset.

Before saving a new session filter, check several dates on both sides of each relevant clock change. Confirm one opening boundary, one closing boundary and a midnight crossover by hand. You are verifying a timetable, not proving the strategy; performance still needs a separate evaluation with realistic execution and costs.