Backtest a screener
A screener backtest re-screens the market month by month over history and measures what the matches went on to return over six holding horizons, against a benchmark; you run it from the screener's Backtest tab.
Steps
- Save the screener with at least one filter. A backtest runs on the last saved filters and universe, so save your edits first. With no filter the tab shows "Backtest your screening rules" over "Add at least one screening rule in the filter bar above, then run it to see how it would have performed against the market, 2000 to today."
- Select the Backtest tab. Before its first run it shows a faded preview of the finished layout behind "See how this screener beat the market".
- Select Run backtest — or Backtest, which is what the header's primary action reads once the screener has no unsaved changes.
- Wait for it. The action reads
Backtesting {percent}%and the panel "Computing performance across six horizons" with the same percentage. Cancel stops watching the run; it undoes nothing, and a result already on screen stays. - Read the verdict band. It states the result as an edge over the benchmark — a hero figure read as "annualized above the benchmark" or "annualized below the benchmark", the horizon it was best at, and the benchmark's own name under Benchmark universe. Every figure in it is an edge, quoted in percentage points rather than as a return.
- Read the panels below it. Edge by holding horizon charts that edge across all six horizons, What happens after selection plots the screener's picks against the benchmark from the moment of selection, and Which filters earn their place breaks the result down filter by filter.
- Re-run after changing filters, with Re-run backtest beside the out-of-date banner.
Done. The verdict band and its three panels describe the filters you saved, and the trust strip closing the view reads "Rebalanced monthly".
What exactly do the six horizons measure?
They measure what the matched instruments returned over the 1, 2, 3, 6, 12 and 24 months after each monthly screening date, averaged across every such date in the tested history. So a screener backtest has six per-horizon averages and no equity curve: it never builds positions, it repeats the screen and follows what came out. That is a different question from a strategy backtest, which replays allocation, rebalancing and exits to produce one path — screener backtest covers the distinction, and holding horizon covers the windows themselves.
Why is my result measured against a benchmark I did not choose?
Because a screener's return means nothing on its own — the same list of matches looks strong in a rising market and weak in a falling one, and only the gap against a benchmark separates the filters from the market they ran in. The band names the benchmark it used under Benchmark universe. The screener backtest benchmark covers what that choice does to the numbers you read.
Why did my result come back instantly the second time?
Because a screener backtest you have already run is served from the result already held rather than computed again. That lasts until the daily market-data refresh, after which the first run of the new day computes in full and its figures can shift slightly even though you changed nothing. Screener execution and caching covers both halves.
What do the banners on the Backtest tab mean?
The banner reads "Out of date — filters changed since the last backtest. Showing the previous run."
You edited a filter after the run. Fincanva keeps the earlier result and dims it rather than deleting it, so you can still read it while knowing it belongs to the earlier filter set. Select Re-run backtest beside the banner to measure the filters you have now.
The run failed: "This backtest couldn't complete"
The body reads "Something went wrong while running it. Your screener and filters are unchanged — try again." Nothing was lost. Select Retry backtest.
The band reads "Refreshing data…" instead of a percentage
Market data is being loaded, and the run waits for it rather than answering from a partial picture. It keeps retrying on its own — there is nothing for you to do.
UPDATED 2026-10-07REVIEWED 2026-10-07