Insights from ChartsWatcher
Why Two Stock Scanners Show Different Relative Volume Numbers
Different relative-volume readings are not automatically a data error. Two scanners can use the same label while comparing different periods, sessions or historical baselines.
This guide is for reconciling two readings. If you are choosing between candle-based and time-matched measurements, start with relative volume versus relative volume at time.
Check these six items first
| Check | Why the readings can differ |
|---|---|
| Units | A ratio of 2.0 may be displayed as 200% elsewhere. |
| Candle length | One-minute activity is not the same observation as five-minute activity. |
| Historical window | Averaging 10 candles can produce a different baseline from averaging 15. |
| Session | Including or excluding extended hours changes the comparison. |
| Candle status | An unfinished candle contains only the volume accumulated so far. |
| Data timing and coverage | A delayed or differently consolidated feed can report a different numerator. |
A numerical example
Suppose both scanners observe 60,000 shares in the current candle. Scanner A uses a historical average of 20,000 shares; Scanner B uses 30,000.
- Scanner A reports 3.0 times, or 300%.
- Scanner B reports 2.0 times, or 200%.
Both calculations are internally consistent. The disagreement comes from the denominator, not necessarily the observed shares.
A documented platform difference
ChartsWatcher's Relative volume reference uses the current candle against an average of the preceding 15 candles on the selected timeframe, expressed as a percentage.
TradingView's screener documentation describes a 10-period baseline for its ordinary relative-volume calculation and excludes extended hours for that field. This description applies to that documented screener field—not every TradingView indicator or community script.
Matching the ticker and timeframe therefore does not necessarily make those two values directly comparable. Neither definition is universally preferable; each answers the question implied by its calculation.
Reconcile one observation before copying thresholds
Record the symbol, timestamp, timezone, session, timeframe, field name and units on both platforms. Inspect whether the current candle is complete, then compare the documented baseline and data delay.
If a mismatch remains, keep the screenshots and settings together for a support question. Do not adjust a threshold merely until the numbers happen to agree.
The practical rule is simple: copy the meaning of a condition, not just its number. Relative volume describes activity against a chosen reference. It does not establish buying pressure, price direction or future returns.