Why Your Opening Range Levels Differ on TradingView

If your opening range high and low differ from another TradingView chart, start by comparing the exact contract, range window, timezone and included candles. Two indicators can use the same “15-minute opening range” label while measuring different prices or different minutes.

The quickest check is to reconstruct one completed range by hand. Write down its start and end times, identify every candle that belongs inside it, then compare the highest high and lowest low with the indicator. That gives you a specific discrepancy to investigate.

For Nasdaq futures traders, a useful troubleshooting example is 09:30–09:45 in America/New_York. The 15-minute length is an illustration, not a recommendation that this duration is best.

Decide which opening you mean

The Nasdaq Stock Market’s regular session opens at 09:30 Eastern Time. CME describes E-mini Nasdaq-100 futures as offering nearly 24-hour access. A futures opening range anchored to the cash market open therefore measures a chosen segment of a much longer futures trading session. Nasdaq trading hours and CME E-mini Nasdaq-100 overview.

Before comparing charts, finish this sentence:

“My range is the highest traded high and lowest traded low from 09:30 inclusive to 09:45 exclusive, in New York time, for this specific futures contract.”

That definition settles several questions immediately. Overnight prices are outside this example’s window. A range beginning with the evening futures session is a different measurement. A 30-minute range ending at 10:00 also answers a different question.

Record the date alongside the definition. An unlabeled screenshot with two horizontal lines is difficult to audit, even when both traders believe they are looking at the same morning.

Separate the chart clock from the calculation clock

Distinguish three time-related concepts in TradingView:

• Chart timezone controls the displayed clock labels

• Exchange timezone belongs to the symbol and is the default for Pine time functions that accept a timezone

• A script can specify another calculation timezone, sometimes through an indicator input

Changing the chart timezone alone does not change Pine Script calculations. Scripts cannot read that chart preference. For example, displaying New York time does not establish that an indicator’s session input is being interpreted in New York time. TradingView time documentation.

Open the indicator’s settings and look for its session and timezone inputs. If their meaning is unclear, check the author’s documentation. Ask which timezone interprets the range start and end, rather than asking only whether the indicator uses “New York open.”

Rebuild a 15 minute range from three candles

Use a standard five-minute candlestick chart with bar boundaries at 09:30, 09:35, 09:40 and 09:45 New York time. For the defined 09:30–09:45 window, include the three bars opening at 09:30, 09:35 and 09:40. Exclude the bar opening at 09:45.

Here is a hypothetical dataset, created solely to demonstrate the calculation:

The completed opening range high is 20,052.50. The low is 20,006.50. The fourth row is outside the chosen measurement period, so its 20,061.00 high does not belong in the result.

If an indicator plots 20,061.00, investigate whether it included the 09:45 candle. If it plots 20,010.00 as the low, investigate whether it stopped before processing the 09:40 candle. These are diagnostic clues from this example, not proof of a particular coding error.

Also distinguish the bar’s opening label from its closing time: the 09:40 bar completes at 09:45. Compare completed data after that point. Before completion, a candle’s high and low can still develop. TradingView chart data documentation.

A timeframe that crosses the range boundary makes this audit harder. A chart bar spanning 09:40–09:50 contains prices from both sides of the cutoff. Its full high and low cannot tell you which prices occurred before 09:45. A script may obtain lower-timeframe data, but you need to verify that behavior. TradingView specifically recommends aligning custom session boundaries with chart-bar boundaries. TradingView session documentation.

Check daylight saving with two known dates

For a New York anchor, a region-based timezone such as America/New_York follows daylight-saving changes. A fixed UTC offset stays fixed. TradingView recommends region-based IANA identifiers when calculations need to follow a location’s observed time. TradingView timezone guidance.

NIST confirms that U.S. daylight saving time began on March 8 in 2026. That produces a useful two-date test: NIST daylight saving rules.

• Friday, March 6, 2026: 09:30 New York corresponds to 14:30 UTC

• Monday, March 9, 2026: 09:30 New York corresponds to 13:30 UTC

Those conversions follow New York’s change from UTC−5 to UTC−4. A range permanently anchored at 14:30 UTC would begin at 10:30 New York after the change.

Inspect those two mornings on historical charts. If the indicator follows 09:30 New York on both, it passes this particular clock check. If it shifts by an hour, inspect the timezone definition before changing the start time manually. A manual correction for one season can leave the other season wrong.

Match the contract and chart session

When the clock checks out, compare the underlying data. Copy the full symbol identifier, including its exchange or provider and contract month. Avoid treating every chart labeled “Nasdaq” as interchangeable.

For continuous futures, record whether back-adjustment is enabled. TradingView’s adjustment changes earlier contract data to remove rollover gaps. An older opening range on an adjusted continuous series can consequently have different absolute levels from an unadjusted view. TradingView continuous-futures adjustment guide.

Also match Electronic Trading Hours and Regular Trading Hours. TradingView documents ETH as the instrument’s main full session and RTH as a reduced intraday session for supported CME Group futures. TradingView futures-session guide.

A session difference deserves inspection, but it does not automatically explain every mismatch. If both charts supply identical bars inside your explicit window and the script uses only those bars, their range arithmetic should agree. Check whether the script instead starts at the first available session bar or carries an earlier value forward.

Use ordinary candles for the manual comparison. Heikin Ashi prices are synthetic, so their displayed extremes can differ from standard candles. Check the chart’s data status too: a delayed chart may not yet contain the same completed morning data as a real-time chart. TradingView non-standard chart guidance and TradingView market-data guidance.

Use this mismatch checklist

Work through one completed trading date before testing several weeks:

1. Save the full symbol, contract, date and chart type

2. Write the exact window and calculation timezone

3. Mark the first included bar and first excluded bar

4. List the included highs and lows, then calculate the two extremes

5. Compare chart session, data status and continuous-contract adjustment settings

6. Change one setting at a time and repeat the calculation

7. Check a date on the other side of a daylight-saving change

If the mismatch remains, send the indicator author a reproducible example: symbol, date, timeframe, settings, expected high and low, and actual high and low. A screenshot helps, but the written values make the problem much easier to locate.

Frequently asked questions

Does the 09:45 candle belong in a 09:30 to 09:45 range?

The candle opening at 09:45 is excluded under the end-exclusive definition used here. On the aligned five-minute chart, the 09:40 candle is the final included bar.

Should I change my range whenever the clocks change?

First verify how the indicator handles its timezone. Test both seasons before deciding that a manual change is necessary.

Can two opening range indicators both be correct?

Yes, if they intentionally use different windows or price datasets. Establish one written definition before judging either result.

Keep that definition with your chart template. It turns the next disagreement into a repeatable calculation instead of a visual guess.