Renko vs Time-Based Charts: What Changes for an Automated Strategy?

The same market, divided by different rules

A conventional time-based bar develops over a specified interval. Its open, high, low and close describe the prices included in that interval. Intraday time bars also depend on the trading-hours definitions selected for the data series.

Renko uses a different completion rule. NinjaTrader describes a new brick as forming when price exceeds the previous brick’s high or low by the configured brick size. The detailed construction and reversal rules belong to the selected Bars type, not to the word “Renko” alone.

These differences follow from the construction rules, not from a claim that either chart type produces better signals.

For brick-size mechanics and NinjaTrader-specific setup details, see Renko Charts in NinjaTrader 8: What Automated Traders Need to Know. This guide focuses on what changes when the two inputs are compared.

Regular time intervals do not mean regular trading signals

On a time-based chart, the interval remains fixed whether the market moves a little or a lot. That gives a bar-based strategy a time-structured input, but it does not require the strategy to find a signal at every close.

On Renko, the pace depends on whether price movement satisfies the brick-construction rules. Bricks can form rapidly during a sufficiently large move, while a developing brick can remain unfinished when movement is insufficient. Equal visual spacing between bricks therefore should not be read as equal elapsed time.

An important distinction follows: more completed bars are not the same thing as more trades. Entries still require the strategy’s programmed conditions to be satisfied. A faster stream of Renko bricks may give a bar-close strategy more evaluation points, but the entry logic determines whether those points produce an order.

Nor is brick formation a direct measure of transaction count or volume. Renko’s trigger is price movement. NinjaTrader’s Tick and Volume bars use different construction criteria. A market can receive many updates without completing another Renko brick if those updates do not meet its price threshold.

Bar formation and calculation timing are separate settings

The chart defines the bars. The strategy’s calculation mode defines how often its bar-update logic runs. NinjaTrader distinguishes OnBarClose, OnEachTick and OnPriceChange.

For a strategy using OnBarClose, changing the Bars type changes the events that bring the next bar-close evaluation. On time bars, those events follow time intervals. On Renko, they follow price-based formation.

A strategy using intrabar updates is not necessarily waiting for another completed candle or brick. Its current-bar values can develop while it is running. This is why “Renko signals are slower” or “Renko trades more often” cannot be treated as universal rules. Both the input series and the strategy’s calculation logic must be considered.

For the broader distinction between data processing, signals and orders, read Inside an Automated NinjaTrader Strategy.

Historical bars and real-time formation are not interchangeable

There are two separate issues to examine: how the bars were constructed and how orders were simulated.

First, a reloaded historical chart may differ from the chart built in real time. NinjaTrader identifies provider filtering, throttling, timestamps and session settings as factors that can affect bar construction. Time-based charts are not exempt from those differences.

Standard Renko adds a specific historical limitation. NinjaTrader documents that a reversal can remove the last bar and replace it with a new opening price. A conventional historical test sees bars that are already built and cannot reproduce that operation in the same way.

Second, a historical order-fill estimate is not the same process as an order filling against incoming real-time data or in a live brokerage account. NinjaTrader explicitly distinguishes those models. The appearance of a completed chart alone does not establish the sequence in which an entry, exit or fill could have occurred.

Tick Replay is not a universal solution. NinjaTrader states that its system Renko Bars type cannot use Tick Replay, and that Tick Replay is not intended to reproduce live strategy results in backtests. Its guidance identifies Playback as a way to test standard Renko formation and reversals. Playback should still be distinguished from live brokerage execution, rather than presented as a guarantee of identical fills.

The practical question is: does the chosen test represent the Bars type, calculation timing and order-handling behavior that the strategy actually uses?

Why unchanged parameters do not preserve an unchanged strategy

An indicator calculated over a fixed number of bars does not necessarily describe the same market window after switching chart types. On time bars, the lookback spans time-defined intervals. On Renko, it spans a sequence whose elapsed duration varies with price movement.

The same distinction applies to rules expressed as “consecutive bars,” “bars since entry” or a maximum holding period measured in bars. Their unit remains a bar, but what that unit represents has changed.

Consequently, retaining the same indicator periods and entry thresholds does not establish equivalent behavior. The underlying sequence of bar values and evaluation times is different. Horizon Algo’s existing Renko guide likewise treats switching Bars types as a change requiring redesign and testing, not as a neutral display adjustment.

A different color scheme is a visual preference. Replacing the series a strategy reads is a change to its inputs.

When the product’s specified setup decides the choice

For a published automated product, start with its documented setup rather than choosing a chart by appearance. Horizon Algo’s NinjaTrader collection distinguishes Renko-based products from time-based products and directs traders to follow the individual product page.

Review the specified instrument and contract, exact Bars type, interval or brick size, trading-hours template and any additional setup requirements. Do not assume that a similarly named custom Renko type is interchangeable with standard Renko. NinjaTrader documents materially different behavior in some custom implementations.

If the product specifies Renko, a time-based chart is not an equivalent substitute. If it specifies a time interval, Renko is not an equivalent substitute. Treat an alternative as a configuration requiring explicit product support and separate evaluation, not as a cosmetic adjustment.

The NinjaTrader strategy collection is the starting point for current product setups. For the role of chart setup in development and evaluation, see the research and testing methodology.