HVNs and LVNs: Reading Acceptance and Thin Trading Zones

Traded volume and available liquidity differ

A profile records completed transactions. A depth ladder displays currently visible orders. A wide profile bar does not mean there are still thousands of contracts waiting to buy at that price. Positions may have changed hands repeatedly and the original participants may have left.

Conversely, a historically thin price can currently have substantial displayed liquidity. That liquidity can trade, cancel, or be replaced. CME's market-by-order overview explains the difference between order-level and aggregated book information. Profile history and order-book observations answer complementary questions, and should not be treated as interchangeable measurements.

When using both, label your claim precisely: “this price was a thin historical region” is observable from the profile; “sellers are currently replenishing offers here” requires current order and trade evidence. “A large institution must defend it” goes beyond either view.

Work through an invented two-node example

Imagine a profile with an HVN around 100, another around 108, and an LVN near 104. Price returns from below to 104 after spending an hour near 100. The first test trades briefly at 104 and falls back. That is a rejected test, but it does not prove that every later test should fail.

On a second test, price holds above 104, and volume begins building around 105 and 106. The old valley is filling. A trader committed to the original LVN narrative may keep fading, while an evidence-based journal records that the distribution is changing. A later retest from above may help distinguish a new accepted region from a temporary excursion.

If the market instead races directly to 108, the next question concerns behavior at the upper node. An old HVN can act as a location for two-sided trade, but new information can carry price through it. Predefined invalidation matters more than the aesthetic appeal of the historical shape.

Research the sequence, not the screenshot

Save the profile before the retest and record the first, second, and later interactions separately. Note how much time elapsed and whether a scheduled announcement intervened. The response on a fifth test should not be merged uncritically with the response on a first test.

Compare results across nearby row sizes. If a supposed edge exists only at one arbitrary aggregation setting, investigate whether the sample is too small or the rule overfitted. A robust structural observation should survive reasonable presentation changes, although its exact boundaries may shift.

Add footprint evidence or a breakout and retest framework only when it answers a defined question. Explore available OrderMap views as a read-only workspace, with source coverage and provider entitlements checked for your market.

Compare first contact with a changed distribution

Suppose an invented LVN at 104 contains only 200 contracts in the saved morning profile. On the first return, another 50 contracts trade there and price rejects. On the second return, 1,500 contracts accumulate across 103.75 through 104.25 while price remains nearby. The old description of a thin region is becoming stale.

The added volume does not establish which side will win. It does establish that the current auction has spent more activity in the region than the original map implied. Record the new distribution and ask whether the valley still exists at the same aggregation scale.

For a useful exercise, preserve both versions side by side. Describe what changed without using directional language, then separately write the continuation and rejection scenarios. This keeps a historical reference from becoming an identity that price is expected to honor indefinitely. Nodes are features of evolving samples, and useful interpretation should evolve with the sample.

Explore OrderMap analytics