How to Track Forex Session Performance

Forex trades at 03:00 UTC are a different game from trades at 13:00 UTC. Volatility, spread, liquidity, and trend behavior all shift dramatically across the four major sessions — yet most traders aggregate their entire history into a single win rate and wonder why their results feel inconsistent. Breaking performance down by session is one of the highest-leverage analysis moves an intermediate trader can make. This guide walks through the exact process of tagging, aggregating, and acting on session-level data.

Step 1: Map the Four Major Sessions to Your Local Time

Before tagging a single trade, establish a consistent session reference in your own timezone. The standard UTC windows are:

Session	UTC Open	UTC Close
Sydney	22:00	07:00
Tokyo	00:00	09:00
London	08:00	17:00
New York	13:00	22:00

The London-New York overlap runs 13:00–17:00 UTC and is worth tracking as its own sub-session — it typically accounts for 35–40% of daily EUR/USD volume.

Convert these to your local time once, write them down, and use the same labels everywhere: Sydney, Tokyo, London, NY, London-NY. Inconsistent labeling — mixing “London” with “EU” or “LDN” — will break any filter or pivot you try to run later.

Step 2: Tag Every Trade with a Session Label

Open your trade log and add a session column if one doesn’t exist. For each closed trade, assign the session based on your entry time, not exit time. A trade entered at 08:15 UTC is a London trade even if it closes at 14:00 UTC.

If your broker exports show entry timestamps, this is mechanical work — no judgment required. For manual loggers, check the entry time against your session map and apply the label before moving on.

For trades entered during overlap windows (e.g., entry at 13:30 UTC falls in both London and New York), tag them as London-NY. This keeps the category meaningful rather than forcing an arbitrary choice.

Going forward, tag every trade at entry. Retroactively tagging a history of 200+ trades is tedious but worth doing once. See how to journal forex trades for a structured logging workflow that makes this easier from day one.

Step 3: Build a Session Performance Breakdown Table

With tagged data, aggregate into a summary table. For each session, calculate:

• Trade count — sample size check
• Win rate — % of winning trades
• Average winner — in pips
• Average loser — in pips
• Expectancy — (Win rate × Avg winner) − (Loss rate × Avg loser)
• Net pips — total P&L contribution

A realistic example for 90 trades across three months might look like this:

Session	Trades	Win Rate	Avg Win	Avg Loss	Expectancy
Tokyo	12	42%	+18 pip	−22 pip	−5.2 pip
London	38	58%	+24 pip	−18 pip	+6.2 pip
London-NY	28	61%	+31 pip	−20 pip	+11.1 pip
New York	12	44%	+20 pip	−19 pip	−1.9 pip

This table alone contains more actionable information than a year of gut-feeling review. Positive expectancy means you have edge; negative expectancy means you’re paying to participate.

Step 4: Identify Your High-Edge and Low-Edge Windows

Look at your expectancy column. Any session with negative expectancy is costing you money regardless of your overall win rate. In the example above, Tokyo (−5.2 pip) and late New York (−1.9 pip) are destroying value.

Cross-reference with trade count to confirm statistical weight. If Tokyo shows 12 trades, the sample is thin — hold conclusions until you reach 30. If London-NY shows 28 trades and a +11.1 pip expectancy, that is a real signal.

Also check for session-by-pair interactions. Filter your London trades to EUR/USD only, then to GBP/USD only. A 58% win rate across all London pairs might mask a 70% win rate on EUR/USD and a 43% rate on GBP/USD — two very different situations. See how to measure trading edge for the full expectancy framework.

Step 5: Adjust Your Schedule and Risk Allocation

Once you know where your edge lives, take action. Three concrete moves:

Stop trading low-edge sessions entirely. If Tokyo has negative expectancy after 30+ trades, remove it from your schedule. Not “trade less” — stop. Every Tokyo trade is expected to lose you pips on average.

Increase position sizing in high-edge windows. If London-NY is your strongest session, allocate 1.5x your standard risk per trade there versus 1x during plain London. Use a position size calculator to set exact lot sizes.

Set hard daily cutoffs. If your data shows performance degrades after 16:00 UTC, set a hard stop at that time regardless of open setups. Self-discipline rules are easier to follow when they’re backed by your own numbers.

Revisit your session table every 4–6 weeks as part of your weekly trade review process. Edge shifts as market conditions change.

Pro Tips

• Track session performance separately for trending and ranging market conditions. London edge often evaporates during low-volatility summer months (July–August) when average daily range on EUR/USD drops below 60 pips.
• Use news filters within sessions. NFP Fridays (New York, 13:30 UTC) behave nothing like normal New York sessions — tag high-impact news days separately to avoid contaminating your baseline data.
• Monitor spread costs per session. Tokyo spreads on GBP/USD can run 2–3 pips wider than London spreads. A +8 pip average winner becomes a +5 or +6 pip net winner after spread — enough to flip edge negative.
• Review session performance by trade duration. A 20-minute scalp in the London open requires different conditions than a 4-hour London swing. Split by holding time if your style mixes both.
• If you travel across time zones, re-anchor your session labels to UTC rather than local time. Consistency in the data matters more than convenience.

Common Mistakes to Avoid

1. Labeling trades by exit time instead of entry time. A trade entered in Tokyo and held through London is a Tokyo trade — that’s when your decision was made and the spread was paid. Always use entry time.

2. Drawing conclusions from fewer than 30 trades per session. With 10 Tokyo trades, a single +50 pip outlier can push win rate from 30% to 40% and make a losing session look breakeven. Wait for statistical weight before acting on the data.

3. Ignoring the overlap session as a separate category. Lumping London-NY overlap into either London or New York distorts both. The overlap has distinct characteristics — tighter spreads, higher volume, stronger momentum continuation — and deserves its own row.

4. Optimizing for win rate instead of expectancy. A session with 65% win rate but tiny winners and large losers has worse expectancy than a 50% win rate session with a 1.5:1 reward-to-risk ratio. Always calculate expectancy, not just win rate.

5. Making schedule changes after one bad week. Session performance needs to be evaluated over a minimum of 30 trades per session, typically 8–12 weeks of data. Reacting to short-term noise with structural changes is one of the fastest ways to abandon a working edge.

How PipJournal Helps

PipJournal automatically tags each trade with its session based on entry timestamp, so you don’t need a separate spreadsheet column or manual lookup. The analytics dashboard breaks down win rate, average pip gain/loss, and net P&L by session in a single view — updated every time you log a trade. Tag filtering lets you cross-reference session with pair, strategy, or setup type to find your highest-conviction combinations. If your Tokyo session is quietly draining your account, PipJournal surfaces that in the session breakdown before it does serious damage to your equity curve.