Who is it for?
Users who review market context before a setup Anyone with sufficient time or OHLC data
Market Time
Forex Market Sessions & Overlap Dashboard
View Sydney, Tokyo, London, and New York forex sessions, date-aware timezone conversion, DST changes, and session overlaps.
FreeNo installationEducational & analytical
Calculate without signing in
No account requiredForex Market Sessions & Overlap Dashboard
See the result first; sign in only to save
Inputs and results are processed in this browser and are not saved to an account. Sign in for saved scenarios, profiles, or an account and Journal workflow.
Tool guide
What does a forex sessions dashboard show?
FX is an OTC, decentralized market; this dashboard treats sessions as conventional activity windows for major trading centers. Active/overlap state is calculated from the selected time and DST rules and is not the status of one centralized exchange.
Logic / formula
Session state comes from reference trading-center windows converted with date-specific IANA rules. Range, ADR, holiday or early-close claims require a verified data/calendar source.
Read the output
The primary output is time context, conventional active sessions and overlaps. Do not infer direction, volatility or setup quality from an active session alone.
TT-FT-030 · versioned engine market-sessions-dashboard@2.0.0 · educational/analytical use; not investment advice.
Full guide, examples, and sources
When should you not rely on it?
Entering solely from one algorithmic output Incomplete, stale, or incorrectly timed data
Logic, formula and methodology
FX is an OTC, decentralized market; this dashboard treats sessions as conventional activity windows for major trading centers. Active/overlap state is calculated from the selected time and DST rules and is not the status of one centralized exchange. Session state comes from reference trading-center windows converted with date-specific IANA rules. Range, ADR, holiday or early-close claims require a verified data/calendar source.
IANA timezone conversion, automatic DST, Sydney/Tokyo/London/New York sessions, London and New York kill zones, active-session overlap, live one-second countdown, Forex/Metal/Index weekday handling, Crypto weekend handling, OHLC session ranges, ADR usage, and Asia-range break statistics.
Worked example
Example
Asian range 18 and ADR 85
Asia Range relative to ADR can add range context, but only when both are calculated from trusted market data.
Asia Range relative to ADR can add range context, but only when both are calculated from trusted market data.
How to read the result
The output is probabilistic context, not a certain signal. Data quality and parameters affect the result.
Read active lanes, countdowns and overlap states separately. Session high/low, ADR and Asia-range statistics only make sense with a trusted OHLC or data source; without one they should remain source-required.
What the TupTrader version adds
The value of this version is not cosmetic; the result, assumptions and workflow are connected to the practical capabilities below.
- Sydney/Tokyo/Frankfurt/London/New York clocks
- 24h timeline
- Overlap windows
- Countdown to open/close
- User/Broker/Exchange clocks
- DST/Holiday/Early close/Weekend
- Maintenance/Rollover context
- Crypto 24/7 mode
Turn the result into a workflow
Related tool →Cross-check context with a complementary tool. Define invalidation and risk. Choose Wait when context is unclear.
Common mistakes and limitations
- Ignoring the higher timeframe
- Treating a score as win probability
- Using unordered or incomplete data
- For crypto, sessions are not exchange open/close times but financial-center activity windows. Holidays, early closes and rollover rules can require separate calendar or broker sources.
Frequently asked questions
What is the London/New York overlap useful for?
It is useful for scheduling and studying instrument behavior during simultaneous activity, not as a directional signal.
What is a kill zone?
A configurable analysis window around certain times; its definition should be explicit rather than treated as a universal rule.
Why did a session time change from last week?
DST or civil-time rule changes can alter offsets; IANA time zones are used to handle this.
Sources and research method
This guide combines the tool’s versioned specification, the earlier TupTrader educational page and the authoritative sources below. External sources are used for definitions and scientific boundaries, not for signals.
- IANA — Time Zone DatabaseLocal-time and DST rules updated as governments change civil-time policy.
This tool is for education, scenario analysis and process control. It is not investment advice, a buy/sell signal or a guarantee of future performance.
Market time
Forex session hours in Tehran time
This example uses Thursday, 10 September 2026 and Asia/Tehran. The tool applies date-aware IANA rules; change the date to account for DST changes in London, New York, and Sydney.
| Trading center | Conventional Tehran window |
|---|---|
| Sydney | 01:30–10:30 |
| Tokyo | 03:30–12:30 |
| London | 10:30–19:30 |
| New York | 15:30–00:30 next day |
London/New York overlap
On this date, the conventional London/New York overlap is 15:30–19:30 Tehran time. An overlap is timing context, not a directional signal.
Why times move
Iran does not observe DST, while the UK, US, and Australia change clocks on different dates. Session offsets can temporarily move by one hour during transition weeks.
From time to plan
Choose the session, cap risk with the position-size calculator, and review the decision in the trading journal.
These are conventional financial-center windows. Holidays, broker maintenance, rollover, and instrument hours can differ.