Global Trading Session Planner
Convert four fixed UTC planning windows to your selected zone and compare their overlaps. This is a daily clock model, not a live broker calendar or a stock-exchange schedule.
Four Planning Windows
London, New York, Tokyo and Sydney label fixed UTC inputs. The table states the inputs so you can inspect the conversion.
Overlap Detection
See every intersection between the model windows, including windows spanning midnight. No market liquidity is measured.
Current Local Offset
The selected display zone uses its current UTC offset. City windows remain fixed; preferences save locally when available.
What are Trading Sessions?
Session labels help organize a trading day, but an instrument’s actual availability comes from its venue or broker. This page supplies a fixed-clock illustration and does not request live market status.
Inspect the model assumptions
- Sydney: 21:00 to 06:00 UTC, crossing midnight.
- Tokyo: 00:00 to 09:00 UTC.
- London: 08:00 to 17:00 UTC.
- New York: 14:00 to 23:00 UTC.
These illustrative nine-hour windows are fixed throughout the year. They are not sourced exchange sessions. For example, NYSE lists its core equity session as 09:30–16:00 Eastern Time and publishes holidays and early closes in its official calendar. The New York model row above does not represent that calendar.
Forex brokers publish their own availability and closures. See, for example, OANDA’s hours of operation, then check the notices applicable to your own account and instrument. Those sources explain why a daily clock diagram cannot confirm an order will be accepted.
Read overlaps as intersections
For these inputs, Sydney–Tokyo intersects at 00:00–06:00 UTC, Tokyo–London at 08:00–09:00, London–New York at 14:00–17:00, and Sydney–New York at 21:00–23:00. The tool derives these intervals from the model; it does not rank them by spreads, volatility or trading opportunity.
How to use the clock model
- Choose a listed time zone. A supported browser zone is detected on load; otherwise the tool starts in UTC. Stored valid preferences take priority.
- Read the UTC inputs beside their local labels. Conversion uses the selected zone’s offset right now, not a historical or future date.
- Inspect the 24-hour diagram and overlaps. A range that wraps around midnight appears in two segments; date labels are not provided.
- Verify the actual date, broker hours and instrument calendar separately. Different cities change clocks on different dates; this fixed-UTC model does not shift city windows to match.
Frequently Asked Questions
What does this planner calculate?
It converts four fixed UTC model windows to the selected zone using its current offset, and intersects every pair of windows. City names label illustrative planning inputs, not verified market opening events.
Does a highlighted window mean I can trade?
No. The model repeats every day without weekend, holiday, maintenance or early-close rules. It does not query a broker or exchange. Check the specific instrument and venue calendar before placing an order.
What does DST adjustment cover?
The selected display zone uses its current offset from the browser time-zone database. Sydney, Tokyo, London and New York model windows stay fixed in UTC; they do not follow each city’s seasonal business hours. There is no date selector, and the timeline is not an exact calendar for a clock-change day.
Do overlaps identify the best trading time?
No liquidity, spread, volatility or strategy performance data is loaded. An overlap is just a time-window intersection, not an alert or a recommendation.
Are preferences retained?
The selected time zone and 12/24-hour format are saved in local browser storage when available. If storage is blocked or full, the page reports that preferences could not be retained. Clearing site data removes them.
Specify Session Rules Before Testing
Describe the intended exchange, session and time zone when asking Pineify to draft Pine Script. Check the generated rules against actual chart bars and test costs and fills. Strategy orders are simulated; live execution requires separate integration and product access depends on your plan.