India's Fastest Realtime Data — Try 5 Days Free Now
[email protected] +91 990 999 3349 Mon–Fri 8:30 AM – 6:00 PM  ·  Sat 10:00 AM – 5:00 PM IST Mon–Fri 8:30–6 · Sat 10–5 IST Mon–Fri 8:30–6

Blog · Foundations

OHLC, one-minute or tick: which data should you backtest on?

Resolution and history depth decide whether a backtest measures your strategy or just the noise in your data. Here is the arithmetic, not the folklore.

Foundations Intermediate 9 September 2026 9 min read

Every backtest makes two decisions before it runs a single trade: how finely it sees each bar, and how far back it looks. Get either wrong and the result is not a pessimistic or optimistic estimate of your strategy — it is an estimate of something else entirely.

Resolution: what each kind of bar can and cannot tell you

DataWhat it knowsGood forCannot test
Daily OHLCFour prices per dayPositional and swing systems, screenersAnything with an intraday stop or target
One-minute barsFour prices per minute plus volumeMost intraday systems, indicator strategiesOrder flow, queue position, sub-minute exits
Tick-by-tickEvery trade and quote changeScalping, order flow, execution researchVery little — this is the ground truth

The classic trap is the intrabar ambiguity. A daily bar tells you the high and the low but not which came first. If your stop and your target both sit inside one bar, the backtest has to guess — and most platforms guess optimistically. One-minute data shrinks that window; tick data removes it.

How much history: the arithmetic of proving an edge

The honest question is not “how many years” but “how many trades”. A strategy’s average result per trade has a statistical noise that shrinks with the square root of the number of trades. That gives a simple rule: if your average trade divided by the spread of trades (a per-trade Sharpe ratio) is s, you need roughly (2 / s)² trades before the edge clears a two-standard-error hurdle.

Trades needed before an edge is statistically distinguishable (t ≥ 2, log scale) 101001,00010,000 s = 0.051,600 trades s = 0.10400 s = 0.15178 s = 0.20100 s = 0.3045
Computed from n ≈ (2 / s)², where s is average trade divided by the standard deviation of trades. Most real intraday edges sit near the top of this chart, which is why short histories mislead.

Two consequences follow. First, a strategy trading twice a week needs years to produce 400 trades; a year of data proves almost nothing. Second, weak edges — which is what most genuine edges are — need thousands of trades, and therefore deep history at fine resolution.

(2/s)²trades to clear a two-standard-error test
√nhow fast noise shrinks as trades accumulate
3+distinct regimes your history should cover

Depth also buys regimes, not just trades

Markets change character. A history that contains only a calm uptrend will pass strategies that fail the first time volatility doubles. Your data should include at least one sharp sell-off, one high-volatility recovery and one long range-bound stretch. Ten years of daily data covers that easily; for intraday work it is the reason deep one-minute and tick archives matter.

Three data traps that inflate every backtest

  • Unadjusted corporate actions. A 1:1 bonus halves the price overnight and looks like a crash. Your intraday and daily series must be adjusted consistently — see splits, bonuses and dividends.
  • Survivorship bias. Testing only today’s index members excludes the stocks that were dropped or delisted, which flatters results. Use point-in-time membership.
  • Look-ahead. Using a bar’s close to decide a trade inside that same bar. It is the single most common bug in home-built backtesters.
Where to get the data: Accelpix plans include tick, one-minute and end-of-day history of different depths — compare them on the pricing page — and the same archive is available programmatically through Pix APIs for Python and Node.js backtesters.

Once a strategy survives the numbers, size it properly before it touches capital: the free position size and risk-reward calculators turn a backtest into a plan you can actually trade.

Choosing resolution and depth by strategy type

StrategyTypical holdingMinimum resolutionHistory to aim for
Positional / swingDays to weeksDaily OHLC10+ years
Intraday indicator systemsMinutes to hoursOne-minute bars3–5 years or more
Options intradayMinutes to hoursOne-minute bars with GreeksSeveral expiry cycles of each type
Order flow / footprintSeconds to minutesTick-by-tickAs deep as the archive allows
ScalpingSecondsTick-by-tickEnough for thousands of trades

The pattern is consistent: the shorter the holding period, the finer the resolution you need — and, because short-term edges are usually thin, the more trades you need to prove them. That is why scalping research is the most data-hungry work in trading, not the least.

How to check a vendor’s history before you buy

  1. Pick a stock that split or issued a bonus. The daily and the five-minute chart should both be smooth across the date.
  2. Count the one-minute bars in a full session. Missing minutes in a liquid stock mean gaps in the archive.
  3. Compare the daily close with the exchange’s official close for a few random days.
  4. Check an expired futures contract. Good archives keep expired contracts; poor ones only keep continuous series.
  5. Ask where the history came from. Recorded live, or reconstructed later? Reconstructed data rarely has true tick sequence.
Key takeaways
  • Match resolution to the strategy: daily bars cannot test intraday stops.
  • Count trades, not years: about (2 / s)² trades to confirm an edge.
  • Deep history buys regime diversity as well as sample size.
  • Adjusted, survivorship-free, look-ahead-free data is the minimum standard.

Questions traders ask

How many years of historical data do I need to backtest?

Enough to include several market regimes and enough trades to be statistically meaningful. For most intraday strategies that means several years of one-minute data at minimum; the number of trades matters more than the number of years.

Can I backtest an intraday strategy on daily data?

No. Daily bars cannot tell you the order in which the high and the low happened, so any strategy with an intraday stop or target is untestable on them.

What is survivorship bias in backtesting?

Testing only on stocks that exist today excludes the ones that were delisted or dropped from an index, which inflates results. Use point-in-time index membership to avoid it.

Test it on your own symbols

Five days of full realtime and historical access, on your platform or through the API. No card, no auto-charge.

Start your 5-day free trial