NinjaTrader backtest fill resolution: Standard, High and Tick Replay

Standard and High change the data used for fills

Standard builds three virtual price segments from each bar. If the open is nearer the high, the assumed path runs through the high first; if nearer the low, it runs through the low first. Those segments represent a fill assumption, not a recovered tick sequence.

When a bar spans both a stop and a target, its OHLC values alone do not establish which level was reached first. That is why a plausible chart can still hide an uncertain historical fill.

Finer fill data does not make the strategy calculate every tick

Calculate controls OnBarUpdate timing. With ordinary historical bars, NinjaTrader processes that method at bar close even when the script selects OnEachTick or OnPriceChange. A more detailed fill series does not by itself supply intrabar signal calculations.

Tick Replay reconstructs historical events for code designed to use them. NinjaTrader explicitly separates that purpose from accurate order-fill and execution-sequence simulation. Turning it on is not evidence that a backtest now matches live trading.

High is not available for every strategy design

High cannot be combined with multi-timeframe or multi-instrument strategies, or with Tick Replay. Treat that as a compatibility limit, not a reason to change unrelated settings.

For a custom multi-series approach, NinjaTrader's intrabar reference sample separates the series used to find a signal from the finer Bars series used to submit orders. That requires strategy code; selecting a dropdown is not equivalent to implementing that order routing.

Check limit-touch and slippage assumptions separately

In the Strategy Analyzer backtest settings, expand Historical fill processing to review Order fill resolution, Fill limit orders on touch and Slippage. Keep the instrument, dates, trading-hours template and primary data-series settings fixed when comparing configurations, so a different data range is not mistaken for a fill-model effect.

Fill limit orders on touch controls whether a single touch of the limit price is enough for a modeled fill. This assumption can change a result independently of the selected resolution.

Enter Slippage in ticks. The Summary display reports slippage in points, so those numbers need not match numerically. Neither field is a measured estimate of your future live costs.

Why a more detailed backtest can still differ from live trading

NinjaTrader describes three different processes: historical fills based on bar data and assumptions, real-time simulation using incoming price and volume, and live executions governed by actual market conditions. More historical detail does not make those processes identical.

Bar construction also matters. Small tick-data differences can change tick-based bars. Synthetic prices in custom Renko or Heiken Ashi bars can differ from prices that actually traded, while standard Renko reversal behavior cannot always be reconstructed from completed bars.

Use the discrepancy to identify the question that remains: did the strategy generate the signal, did the historical engine model a fill, or did a live order execute? Changing fill resolution addresses only part of that comparison.