What is survivorship bias in backtesting?

Testing a strategy only on securities that still exist today, which excludes every company that delisted or failed. Because those exclusions are not random – they correlate with poor performance – the backtest is measured on a universe selected for success.

How do I detect look-ahead bias?

Shift every input forward by a conservative publication lag and re-run. A sharp drop in performance indicates the original test was using information not available at the decision time. Also check that signals generated on a bar's close are executed on a later bar.

How much out-of-sample data do I need?

Enough to contain market conditions absent from the training period, which usually means more than a single year. What matters more than length is that it is genuinely untouched – a hold-out period you have already tuned against has become training data.

Learn · 29 July 2026

Why your backtest looks better than reality

Survivorship bias, look-ahead bias and overfitting each inflate backtested returns in ways that vanish in live trading. What each one is, how it creeps in, and how to test for it.

4 min read

A backtest is a claim about a history that did not happen: the history in which you traded this strategy. The gap between backtested and live performance is rarely bad luck. It is usually one of three biases, each of which inflates results systematically rather than randomly.

Survivorship bias

If your data covers companies currently listed, every company that delisted, was acquired or went to zero is missing. You are testing on a universe pre-filtered for survival, which is information nobody had at the time.

The fix is a point-in-time universe: for each historical date, the set of securities actually listed and eligible on that date, delisted names included, with their delisting outcome. If your data source cannot provide this, the honest response is to widen your uncertainty rather than proceed as though it did not matter.

Look-ahead bias

Look-ahead bias is using information the strategy could not have had at the decision moment. It is the easiest bias to introduce accidentally and the hardest to spot, because the code looks correct.

Source	What goes wrong
Financial results dated to period end	Q1 results are stamped 31 March but were published in May. Using them from 1 April sees the future by six weeks.
Restated financials	The database holds the corrected figure; the market traded on the original.
Same-bar execution	Signalling on the close and filling at that same close assumes an order placed after the price was known.
Index membership	Applying today's constituent list to a historical date includes companies added later, precisely because they performed well.
Normalising over the full sample	Scaling a feature by the whole period's mean and standard deviation leaks the future into every early observation.

Common sources of look-ahead

Overfitting

Test enough variations on the same data and one will look excellent by chance. This is not a subtle statistical concern – it is close to guaranteed once the number of configurations tried becomes large.

E[max of N random strategies] grows roughly with √(2 ln N)

The best of many random strategies looks good in proportion to how many were tried – even when none has any edge at all.

The practical consequence is that the number of configurations you tested is part of your result. A Sharpe of 1.5 found on the first attempt and the same figure found on the four-hundredth are different pieces of evidence, and only one of them is worth much.

01Decide the hypothesis before looking at the data, and write it down.
02Hold out a period and do not touch it until the strategy is final. Once you have tuned against it, it is training data.
03Count and report every configuration tested, including the ones abandoned.
04Prefer fewer parameters. Each additional one is another degree of freedom to fit noise with.
05Check whether the edge survives on adjacent markets or periods. A real effect usually leaves traces elsewhere.

Illustrative, not measured: the exact reduction depends entirely on the strategy. The shape is the point — every correction moves the number down, never up.

What a credible backtest looks like

A point-in-time universe including delisted securities.
Every input lagged by its realistic publication delay.
Costs and slippage applied per trade, at execution, not netted off at the end.
Execution assumptions no better than crossing the spread on the next available bar.
An untouched out-of-sample period, and an honest count of what was tried.

A backtest built this way will show lower returns than the naive version. That is the point – the lower number is the one that has some chance of being repeated.

Common questions

What is survivorship bias in backtesting?: Testing a strategy only on securities that still exist today, which excludes every company that delisted or failed. Because those exclusions are not random – they correlate with poor performance – the backtest is measured on a universe selected for success.
How do I detect look-ahead bias?: Shift every input forward by a conservative publication lag and re-run. A sharp drop in performance indicates the original test was using information not available at the decision time. Also check that signals generated on a bar's close are executed on a later bar.
How much out-of-sample data do I need?: Enough to contain market conditions absent from the training period, which usually means more than a single year. What matters more than length is that it is genuinely untouched – a hold-out period you have already tuned against has become training data.

What a trade actually costs in India: brokerage, STT, GST and slippage

Zero-brokerage is not zero-cost. A full breakdown of every charge on an Indian equity trade, why slippage usually exceeds the visible fees, and what it does to a high-frequency strategy.

3 min read

Screening criteria that survive contact with the market

Most screens return either four companies or four hundred. How to choose criteria that narrow a universe without accidentally encoding a single sector, and how to sanity-check a screen before trusting it.