What does 10R mean on a range bar chart?

It means ten minimum price increments. If the tick size is 0.25, the range distance is 2.50 price points. It is neither ten trades nor ten minutes.

Are range bars the same as tick bars?

No. Range bars use price distance. Tick bars group a chosen number of successive ticks. Both can have variable duration, but their bar boundaries answer different questions.

Are phantom bars evidence of traded prices?

No. They visualize gaps with virtual bars. Use independent execution data to assess whether a price was available for an order.

Can Pine Script run on TradingView Range charts?

TradingView documents Range chart detection and strategy use. Verify your specific script and requests. The documented ticker constructors do not include a native Range constructor for requesting that feed from another chart.

Can I use Bar Replay or standard OHLC fills to validate a Range strategy?

The current Replay guide excludes Range, and the standard OHLC fill option applies to Heikin Ashi. Neither supplies a documented shortcut for validating native Range execution. Use separately specified standard-chart tests and forward observations with their limits recorded.

TradingView chart workflows

Range bars: price distance, construction and limitations

A range bar chart builds bars from price movement rather than elapsed time or a count of trades. TradingView defines one range as one minimum price increment. With a 0.25 tick size, 10R represents 2.50 price points. Bars can take different amounts of time to form. Treat the chart as a price-based view, and check its construction and fill assumptions before using strategy results.

See the decision guide

Convert the range setting into a price distance

Read the minimum tick size for the exact exchange-prefixed symbol before selecting a range interval. The same number of ranges can represent very different price distances across instruments. These hypothetical examples show the unit conversion, not recommended trading settings.

For a hypothetical 0.25-tick instrument, a 5.00-point target corresponds to 5.00 / 0.25 = 20 ranges. This arithmetic does not establish which custom intervals your account permits.
Price points are not account profit or loss. Contract multipliers, position size, currency conversion and execution costs are separate calculations.
Record both values, such as "10R, tick size 0.25, distance 2.50", so a saved setup does not depend on an ambiguous label.

Minimum tick size	Range setting	Price distance	Meaning
0.01	10R	10 × 0.01 = 0.10	Ten cents for a dollar-quoted share
0.25	10R	10 × 0.25 = 2.50	2.50 quoted price points, not ten points
0.00001	100R	100 × 0.00001 = 0.00100	A quote-price distance; do not substitute a pip convention

Range bars, tick bars and time bars sample different events

The word tick has two meanings in this comparison: a minimum price increment and an observation counted by a tick chart. Confusing them turns a price threshold into a trade-count rule. TradingView tick intervals group successive ticks; range intervals use price increments.

Suppose repeated trades occur at 100.00. A tick chart can keep producing bars while a range chart waits for a sufficient price move. The range setting does not count those trades.
Suppose one range bar develops over two seconds and another over eight minutes. A 20-bar indicator weights both as one observation; it does not represent a fixed 20-minute window.
When comparing indicators, preserve dates and session settings and record signal timestamps. Matching only the indicator length does not create equivalent samples.

Chart	Bar-building input	What is not fixed
Range, such as 10R	A specified price range	Elapsed time and number of observations
Tick, such as 10T	Ten successive ticks	Price range and elapsed time
Time, such as 1 minute	A clock interval	Price range and activity within that interval

Inspect construction, projections and gaps

TradingView's 2018 construction explanation describes a bar expanding until high minus low reaches the selected range. Its close can then move inside those bounds; a move beyond them starts the next bar. Reaching the span and beginning the next bar are distinct events in that description.

Worked construction example: with a 2.50 range, a hypothetical bar whose low is 100.00 and high is 102.50 has reached its span. An observation at 101.50 is still inside it. Do not assume that touching 102.50 alone establishes the next bar's timestamp.
Projection bars use the currently forming source bar. Record an observation while it develops and after confirmation before treating it as a stable signal.
Phantom bars draw virtual bars through untraded price gaps. A visible bar at a skipped level does not prove that an order could have filled there.

Check historical data and current TradingView limits

Official documentation was checked on October 17, 2026. The launch article names one-minute OHLC as the Range source data. The current Range help article does not restate that granularity or promise complete historical tick reconstruction. Treat the older statement as documented construction history, not a fresh account-level data audit.

Two hypothetical paths, 100 → 103 → 99 → 101 and 100 → 99 → 103 → 101, share the same OHLC. Their order of threshold crossings differs. That is why a reconstructed chart cannot, by itself, prove the original execution sequence.
For a live-versus-history check, save the symbol, session, range size, projection/phantom settings and timestamps. Compare the same region after reload. Record any change rather than assuming the live sequence was preserved.
A bar-count history limit is not a calendar duration. Measure the earliest available date for the selected setup; no signed-in account or live-feed test is claimed here.

Feature	Documented position	Research consequence
Selection	Choose Range in chart type or a range interval in the interval menu; the interval guide lists 1, 10, 100 and 1000 ranges	Record the exact setting and symbol
Bar Replay	The current Replay guide explicitly excludes Range	Do not plan a native Range replay experiment
Historical path	The older construction article describes OHLC input rather than a full tick stream	OHLC alone cannot recover every intrabar move
Custom intervals and access	The launch article uses old plan names	Check current account controls; this page makes no plan entitlement claim

Pine support does not validate Range backtests

The current Pine manual documents chart.is_range, and TradingView's strategy help explicitly includes Range among charts where strategies can run. This is different from requesting a native Range feed from another chart: the documented non-standard ticker constructors cover Heikin Ashi, Renko, Line Break, Kagi and Point & Figure, with no Range constructor listed.

Do not invent a ticker.range() function or assume that typing a Range label into a data request makes it supported. A custom OHLC-based approximation must be labeled with its input data and construction rules.
TradingView warns that strategies on non-standard charts use chart OHLC for simulated fills and can produce results that do not represent market conditions. A valid script and a profitable report do not establish that the displayed price was tradable at the assumed time.
The standard OHLC fill option is documented for Heikin Ashi. It is not a general correction for Range charts.
Test the exact indicator on the selected chart, including its timeframe inputs and external data requests. Keep any strategy report labeled with its chart type, range setting, date coverage, costs and fill assumptions.

Write a test specification before asking for a script

Pineify AI Coding Agent can help draft or revise Pine Script from explicit rules. It does not unlock TradingView data or supply an undocumented native Range request. For an execution baseline, define a separate rule on standard time-based candles and label it as a different experiment.

Specify the exchange-prefixed symbol, session, chart type, range count and tick size. State whether the condition is measured on completed bars.
Describe the observable event and invalidation condition. Ask for timestamped signal markers before introducing orders, so data differences can be inspected separately.
For a standard-chart baseline, define its own timeframe and entry/exit rules. Compare signal timing over overlapping dates; do not claim it reproduces native Range bars.
Review generated code, check its syntax, and run it on the supported target chart. A syntax check tests code acceptance, not data equivalence or future returns.

Where Pineify fits

Pine Script AI Coding Agent

Bring a written rule and the intended chart context. Draft a supported Pine script or a separately labeled standard-chart baseline, then inspect its signals in TradingView.

Draft a chart-aware script

Related resources

TradingView workflows Tick chart data and script limits Backtest accuracy and execution assumptions Pine Script AI Coding Agent

Frequently asked questions

Educational chart and programming guidance, not investment advice. Numerical paths and tick sizes are hypothetical. No account-level chart test, execution result or profitability claim is presented.

Sources and verification

Last verified: 2026-10-17

Published by Pineify. Pineify is an independent product and is not affiliated with TradingView. Sources support the technical explanations; examples do not establish trading performance.