Trading session
Trading session — The regional market hours a trade falls into — and one of the few breakdowns where a statement usually shows a real, actionable difference.
Of all the ways to slice a trading record, session is among the most likely to show something real — liquidity genuinely differs by hour, and so do spreads, ranges and the character of moves. It is also among the easiest to get wrong, because it depends entirely on a timezone your statement does not state.
In plain English
The forex day is conventionally split into Asian, European and North American hours, named after Tokyo, London and New York. They overlap; the London/New York overlap in the early afternoon UK time is the most liquid window of the day and carries the tightest spreads and the largest ranges.
The differences are not folklore. Asian hours are typically quieter with narrower ranges, which suits mean-reversion and punishes breakout strategies. London’s open produces the day’s first large directional move on European pairs. The overlap concentrates volume. Late New York into the rollover is thin, and spreads widen accordingly.
The catch is that MetaTrader timestamps are in server time, which is usually a European time close to UTC+2 or UTC+3 and is not written anywhere in the file. Assume the wrong offset and every trade lands in the wrong session, and the analysis becomes confidently misleading rather than obviously broken.
The formula
UTC hour = server-time hour − server UTC offset session = the bucket that UTC hour falls into
- Tokyo 00:00–08:00 UTC · London 08:00–13:00 · London/NY overlap 13:00–17:00 · New York 17:00–22:00 · Off-session 22:00–00:00.
- These buckets are a non-overlapping partition, so every hour belongs to exactly one. Real sessions overlap; a breakdown cannot, or trades would be counted twice.
The offset is a setting, not a guess we make for you. Get it from your broker or by comparing a trade’s timestamp against when you know you placed it.
Worked example — the demo account
The bundled demo account, 96 closed trades, bucketed by the hour each position OPENED.
| Bucketing basis | open time, not close | |
|---|---|---|
| Server offset assumed | UTC+3 | the TapeSheet default; adjustable in Settings |
| Effect of a wrong offset | every trade shifts bucket | |
| Average hold | 7h 29m | short enough that open and close usually share a session |
Sessions are assigned from the OPEN time, because that is when the decision was made — and the entry conditions are what the breakdown is trying to describe.
That choice matters more for swing trading than for this account. With an average hold of 7h 29m, most of these trades open and close inside the same session, so the two bases would broadly agree. A position held four days has an open session and a close session with nothing in common, and bucketing it by close would attribute the result to a session the trader was probably asleep for.
The caution to carry into the breakdown: with 96 trades across five buckets, some buckets hold very few trades. A session showing a spectacular win rate on seven trades is showing you seven trades.
Every figure above is from the demo account TapeSheet ships with — 96 closed trades, generated from a fixed seed. Open the same account →
What this does not tell you
The caveat is the part worth reading. Most tools put it in a footer, if they print it at all.
- It depends entirely on the server offset being right, and the file does not contain it. A wrong offset does not produce an obviously broken chart; it produces a plausible chart about the wrong hours.
- Sample sizes get small fast. Five session buckets and a few hundred trades means some buckets hold a handful, and a handful is not evidence.
- It is a classic over-fitting trap. With five buckets, one will look best by chance. Acting on "I only trade the London session now" from a single quarter of data is fitting noise, and it is one of the most common ways a working strategy gets damaged.
- Nothing about why. A session performing well may reflect the strategy suiting those conditions, or simply that you were rested and at your desk. Both are real; they need different responses.
Where TapeSheet shows it
A session breakdown on the Analysis view, with net result, trade count and win rate per session, and the server-time offset set in Settings. Changing the offset re-buckets everything immediately, which makes the sensitivity visible rather than theoretical.
Questions
What server time is my broker on?
Most are on a European time around UTC+2 in winter and UTC+3 in summer, so their daily candles close at the New York close. It is not in the statement, so either ask your broker, check the platform’s market-watch clock against your own, or take a trade you remember placing and see what the file says the time was.
Should I bucket by open time or close time?
Open time, if the question is about entry conditions — which it usually is, because the entry is the decision the session was supposed to influence. Close time is the right basis for a question about exits and management. TapeSheet uses open time for the session breakdown and says so on the chart.
My results are much better in one session. Should I only trade that one?
Not on one quarter of data. Check the sample size in that bucket first; then check whether the difference survives if you split the period in half. A genuine session effect usually has a mechanical explanation you can state — a strategy needing volatility that only exists in the overlap, say. If you cannot state the mechanism, treat it as noise until a second sample agrees.
Related terms
See your own statement, analyzed
Drop an MT4 or MT5 statement on the page and the whole dashboard renders in about three seconds. No signup, no upload — the file is parsed inside your browser tab and never leaves your device.
Analyze my statementAll glossary terms ·Free trading journal ·MT4 statement analyzer ·MT5 report analyzer