RTH vs ETH: when your chart and Volume Profile trading hours disagree

**RTH vs ETH: when your chart and Volume Profile trading hours disagree**

I keep running into the same confusion in profile-based discussions: two traders post “yesterday’s value area” for the same contract, but their POC, VAH, and VAL differ by several ticks.

Often neither calculation is necessarily wrong. They may simply be profiling different parts of the session.

In NinjaTrader, there are two settings worth separating:

1. **The chart Data Series → Trading Hours setting.**
This determines which market data is available on the chart in the first place.

2. **The Order Flow Volume Profile → Trading hours setting.**
This can further filter the data used by the profile.

The important part is that the second setting is a filter. It cannot restore data that the chart never loaded.

For example, an ETH chart can contain the full session while the Volume Profile itself is filtered to an RTH template. But if the chart itself is RTH-only, switching the profile to an ETH template cannot magically add the missing overnight data.

That distinction matters more than it may seem.

**Conceptual ES example**

Suppose the overnight session trades heavily in a range below the previous RTH close. Then RTH opens higher and spends most of the day rotating above that overnight range.

A full-session ETH profile may place its POC lower because substantial overnight volume occurred there.

An RTH-only profile may instead place its POC inside the daytime rotation, with a different VAH and VAL.

Both profiles can be useful. They are answering different questions.

The problem starts when two traders both say “yesterday’s POC” or “yesterday’s value” without specifying the session basis.

A rule such as value-area re-entry, POC rejection, POC-as-magnet, or one of the various “80% rule” interpretations can therefore produce different reference levels depending on whether the underlying profile is RTH or ETH.

**Where this becomes especially important**

- **Composite profiles:** an RTH-based multi-day composite and an ETH-based composite can produce different distributions because they are aggregating different data.
- **Backtests:** if a strategy or Strategy Analyzer run uses a different Trading Hours template from the chart used during discretionary review, the strategy may be calculating from a different session definition.
- **Holidays and unusual sessions:** Trading Hours templates also define session and holiday boundaries, so it is worth checking them before treating every trading day as equivalent.
- **Playback testing:** when using Playback to review a setup, I want the chart and profile Trading Hours configuration to match the configuration I am trying to reproduce.

**A simple reproducible check**

1. Open two charts of the same instrument over the same dates and use the same bar type.
2. Set Chart A to an ETH Trading Hours template.
3. Set Chart B to the corresponding RTH Trading Hours template.
4. Apply the same Order Flow Volume Profile configuration to both and compare POC, VAH, and VAL over several sessions.
5. On Chart A, change only the Volume Profile’s Trading hours filter to the RTH template and compare it with Chart B.

If the two RTH results still differ, then I would start checking the remaining construction variables: profile resolution, tick vs minute source data, ticks-per-level, loaded history, and bar construction.

My own habit is simple: whenever I save or discuss a profile level, I include the session basis in the label — for example, **RTH POC**, **ETH VAL**, or **RTH VAH**.

That small detail removes a lot of ambiguity.

**Question for the thread:**
For those trading ES/NQ or other index futures using profile levels, do you normally use RTH or ETH for prior-session references? And if you have tested both approaches side by side, how much did the choice change your levels or trade triggers?
[AI-assisted] I used AI to help organize and edit parts of this post, together with my own trading/platform experience.