Advertisement IC Markets

Previous Day High/Low on the Daily Close: Why Server Time Changes the Levels

Discuss 1-minute to 15-minute price action setups, fading intraday momentum, key support/resistance zones, and proven short-term trading methodologies.
Post Reply
FXS Prop Desk
Posts: 1689
Joined: Wed Oct 07, 2026 9:52 am

Previous Day High/Low on the Daily Close: Why Server Time Changes the Levels

Post by FXS Prop Desk »

The previous day's high and low are only as good as the definition of "day". Two brokers can show different levels on the same pair because their daily candle closes at different times.

Common setups:
  • GMT+2/+3 servers: the day closes at 17:00 New York, giving five daily candles per week. This matches how most institutional desks see the day.
  • GMT servers: the day closes at midnight London, and a small Sunday candle appears. That Sunday candle distorts Monday's "previous day" levels.
  • Charting platforms: TradingView and others may use yet another session definition depending on the data source.
Practical consequences:
  • A level that held "perfectly" on one chart may be a few pips off on another.
  • Monday's previous-day levels are most affected. Using Friday's high and low is often cleaner.
  • If you backtest PDH/PDL setups, use the same day definition as your live platform.
Which daily close does your platform use, and have you noticed level differences between charts?
FXS Official Team | The Idea Lab & Strategy
Recommended broker for automated trading & scalping IC Markets
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

Re: Previous Day High/Low on the Daily Close: Why Server Time Changes the Levels

Post by Fairman »

FXS Prop Desk wrote: If you backtest PDH/PDL setups, use the same day definition as your live platform.
This one matters more than it sounds, because a lot of free historical data is stored in UTC, so if you download it and build daily bars yourself you get a UTC midnight day by default, Sunday stub and all, even if your live platform runs on a New York close. Then the backtest is testing levels you never actually see live. A quick sanity check is to pull a handful of daily highs from your platform and compare them with the ones your backtest generated for the same dates. If they don't match on Mondays and around the clock change weeks, the definitions are out of line. Those weeks are sneaky because US and UK clocks change on different dates, so the 17:00 New York close shifts relative to London for a week or two.
It’s Fairman :geek:
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Previous Day High/Low on the Daily Close: Why Server Time Changes the Levels

Post by Shadow Trader »

I lost a clean Monday fade last month because my TradingView daily closed at midnight London while the broker daily closed at 17:00 New York. The previous day high I marked was Friday evening Asia, not the New York close high the platform was using for stops.

Fairman is right about UTC downloads. When I rebuilt daily bars from a free tick dump without forcing New York close, Monday PDH was wrong on 11 of 20 sample weeks.
img_13483_r1.png
img_13483_r1.png (76.63 KiB) Viewed 137 times
The illustration overlays New York close PDH against a midnight London daily on the same EURUSD week. The gap is often 4 to 9 pips, which is enough to turn a scalp stop into noise.

Does your live server match the platform you mark levels on? I keep a standing 5 pip buffer when they disagree, and Friday high low is my Monday default when a Sunday stub exists.
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Previous Day High/Low on the Daily Close: Why Server Time Changes the Levels

Post by Shadow Trader »

Fairman's point about the clock change weeks is the one I would underline, since the autumn one starts on 25 October. Britain shifts to winter time a week before America does, and in that window the broker's New York close falls an hour earlier on a London clock.
img_13483_r2.png
img_13483_r2.png (104.88 KiB) Viewed 123 times
The chart shows a Tuesday from that kind of week on EURUSD, with a late spike to 1.0858 at 21:20 London after a session high of 1.0852. A daily built with a fixed 22:00 London cut puts that spike into Tuesday, while the broker's real New York close at 21:00 pushes it into Wednesday.

So on Wednesday morning one screen says the previous day high is 1.0858 and the other says 1.0852. Six pips is bigger than my whole stop on a London open fade, and the disagreement only exists for five sessions.

My fix is boring. The backtest now reads the broker's own daily bars instead of rebuilding them from a clock rule, and where that is impossible I convert every timestamp to New York time first and cut the day at 17:00 there.

The spring mismatch is the worse one, usually two or three weeks long. Does anyone drop those weeks from their PDH stats, or just accept the noise?
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Previous Day High/Low on the Daily Close: Why Server Time Changes the Levels

Post by Shadow Trader »

Broker servers run on different time zones, and the choice affects where daily candles open and close. Many brokers use a New York close configuration, with the server rolling over at 5 PM Eastern, while others use GMT or a fixed offset such as GMT+2 or GMT+3 with daylight saving adjustments.

For scalpers, this matters most when a strategy references session opens, daily highs and lows, or time-based filters. A rule such as "avoid trading in the first 15 minutes of the London session" can quietly shift by an hour if the server clock and the strategy clock disagree, especially in the weeks when the United States and Europe change daylight saving on different dates.

Those mismatched weeks, usually in March and late October to early November, are a classic source of unexplained backtest drift. Converting all timestamps to UTC before analysis removes the ambiguity. Any time-based rule should be defined in UTC or in a named session with explicit daylight handling.
Post Reply