A session map is a clock layer—not a trading signal.
FX is decentralised and trades through a network of dealers and venues rather than one central exchange. The working day moves from Asia-Pacific centres into Europe and then North America. The BIS describes the market as operating around the clock for roughly five and a half days a week. [1]
This example shows a UK-winter / US-winter day while Sydney is on daylight saving. The bars are a clock map, not an exchange schedule or a forecast.
Swipe the clock left and right to inspect all 24 hours.
- Sydney08:00–17:00 Sydney
- Tokyo08:00–17:00 Tokyo
- London08:00–17:00 London
- New York08:00–17:00 New York
- OverlapLondon + New York
Write “08:00 Europe/London,” not just “London open.”
The date decides whether London, New York or Sydney is on daylight saving.
Only after UTC is known should you translate the window into broker-server bars.
Sydney, Tokyo, London and New York describe participation—not personality.
Marks the return of Asia-Pacific business after the weekend and the start of a new regional working day.
- Reference
- 08:00–17:00 Sydney
- Clock issue
- NSW changes daylight saving; Queensland and Western Australia do not follow the same rule.
A stable time anchor because Japan does not currently change clocks seasonally. Other Asian centres remain active around it.
- Reference
- 08:00–17:00 Tokyo
- Clock issue
- Do not rename the whole Asian region “Tokyo”; Singapore, Hong Kong and others have their own calendars.
A major global FX centre. The 2025 BIS survey again ranked the United Kingdom as the largest geographical FX hub.
- Reference
- 08:00–17:00 London
- Clock issue
- GMT in winter, BST (UTC+1) in summer.
Overlaps the European afternoon and then continues after London’s reference window ends.
- Reference
- 08:00–17:00 New York
- Clock issue
- EST (UTC−5) in winter, EDT (UTC−4) in summer.
These reference hours make charts comparable; they do not claim every bank, venue or broker keeps the same hours. Sydney's daylight-saving rules also vary across Australian states. [2][5]
The pair tells you which two currencies are being compared.
one unit being priced
amount paid for one base unit
London and New York are obvious windows to compare, but the pair is not “closed” outside them.
Tokyo and New York provide useful regional context. A session label still says nothing about direction.
Sydney and Tokyo can both matter. Different holiday calendars and daylight rules still need checking.
More active centres can change conditions, but they do not choose a direction.
The London–New York overlap puts two major centres inside their local working-day windows at the same time. That can change participation, but “overlap” does not guarantee a larger range, tighter spread or a profitable breakout. OTC prices and costs can differ by dealer, account and moment. The market is also highly fragmented. [1][2]
Retail tick activity is not the whole FX market. Compare the same data source throughout a test.
Record range or ATR using a fixed formula. A quiet overlap is still an overlap.
Scheduled releases, rollover, dealer conditions and account type can change execution.
Use market structure, a pattern or another written trigger for long, short or no-trade.
Local city → UTC → UK, visitor and broker time.
Use one source of truth: the city's IANA zone on the historical date. Never convert London straight to a remembered broker offset. UTC in the middle makes the calculation visible and checkable.
- 01Choose the exact date
“13 August 2026,” not “summer.” Historical tests use the historical offset.
- 02Write the city window
Example: London 08:00–17:00 in
Europe/London. - 03Convert it to UTC
On this date London is BST (UTC+1), so the window is 07:00–16:00 UTC.
- 04Create the UK and visitor views
UK is 08:00–17:00 BST. A visitor in
Asia/Kolkatasees 12:30–21:30 IST. - 05Measure broker-server offset
At the same instant, compare the platform clock with UTC. If it reads UTC+3, add three hours.
- 06Save all four fields
Date, city/IANA window, UTC window and broker bars belong in the replay record.
- London
- 08:00–17:00 BST
- New York
- 08:00–17:00 EDT
- UTC overlap
- 12:00–16:00 UTC
- UK visitor
- 13:00–17:00 BST
- India visitor
- 17:30–21:30 IST
- Example broker
- 15:00–19:00 at UTC+3
London and New York do not change clocks on the same Sunday.
In 2026, US daylight saving began on 8 March and UK summer time began on 29 March. The UK returned to GMT on 25 October; the US returned to standard time on 1 November. That changes a UK-viewed New York window by one hour during the gaps. [3][4]
Overlap: 13:00–17:00 UK
Overlap: 12:00–17:00 UK
Overlap: 13:00–17:00 UK
The autumn mismatch runs from the UK change on 25 October 2026 until the US change on 1 November. On the trading days in between, the same reference overlap is again 12:00–17:00 UK. [3][4]
Europe/London and America/New_York update with regional clock rules.
“New York = UTC−5” is wrong while EDT is in force. “London = UTC” is wrong during BST.
A broker may have changed its server policy. Derive each date from timestamps or documented history.
MT4, MT5 and TradingView handle time differently.
- Click the clock/timezone at the bottom of the chart, or open Chart settings → Symbol.
- Use UTC for clean testing, or your visitor zone for everyday reading.
- Add “Trading Sessions” on an intraday chart if useful.
- For session inputs, prefer
Europe/London,America/New_YorkandAsia/Tokyoover fixed GMT offsets. - Write the chosen chart zone on screenshots and exports.
TradingView says its IANA session zones adjust for regional time changes; a fixed GMT offset does not. [6][7]
- Open Market Watch and display the quote arrival time.
- Compare that timestamp with a reliable UTC clock at the same instant.
- Record the offset, such as UTC+2 or UTC+3; do not infer it from your computer clock.
- Use the crosshair or Data Window to read each bar's date and time.
- Ask the broker how its server offset changes and note any symbol-specific hours.
MT5 Help states that the Market Watch quote time uses the broker trading server's time zone. [8][9]
- Read the bar timestamp from the chart's horizontal axis and crosshair.
- Compare the terminal clock/timestamp with UTC at the same instant.
- Write the measured offset beside the broker and server name.
- Check again after UK, US or broker clock changes.
- Show the Ask line when a spread-sensitive rule needs both sides of the price.
MT4's official chart help explains its bar time axis and that bars are built from Bid prices while the Ask line can be displayed. [10]
Before, during and after: one session routine you can repeat.
- Write date, pair, timeframe and setup version.
- Convert the session to UTC, visitor and broker time.
- Mark prior range, structure and no-trade boundaries.
- Check scheduled events and broker symbol hours.
- Write maximum spread, entry, invalidation, size and session stop time.
- Confirm the candle belongs to the intended broker-time window.
- Read current spread before treating price as tradable.
- Wait for the exact completed-bar trigger.
- Skip entries inside the written event block.
- Stop evaluating when the session window or daily risk cap ends.
- Save a screenshot with chart timezone visible.
- Record planned and filled prices plus costs.
- Mark signal, rejected setup or no-trade.
- Separate a timing error from a strategy loss.
- Review several comparable sessions before changing the rule.
One valid evaluation and one correct no-trade.
- 11:30
- 12:00
- 12:30
- 13:00
- 14:15 UTC
London 08:00–17:00 BST converts to 07:00–16:00 UTC. New York 08:00–17:00 EDT converts to 12:00–21:00 UTC.
The shared window is 12:00–16:00 UTC, which is 13:00–17:00 UK and 15:00–19:00 on this fictional UTC+3 broker chart.
The made-up plan bans new entries from 12:20 to 12:40 UTC. The price move inside that band is observed, not chased.
A later completed close meets the fictional range rule and costs are inside its limit. The session allowed evaluation; it did not create the signal.
- Prepare
Tokyo reference window begins at 23:00 UTC. The written demo rule allows no more than a 1.0-pip spread.
- Window opens
Market Watch shows 1.7 pips on the fictional feed. Pair and session match; the cost rule does not.
- Price breaks the range
The candle looks attractive, but the spread remains above the fixed limit. No order is allowed.
- Record the skip
Save “no trade — cost gate failed.” A later move does not turn the skipped entry into a mistake.
This example shows why “Tokyo session” is not a complete method. A usable plan still needs a setup, trigger, invalidation, size, cost limit and stopping rule.