Renko BacktestingOctober 26, 202613 min read

Renko Backtesting: Why Most Tests Lie and How to Fix Them

Renko backtests often look better than live trading. Learn the look-ahead and tick-data traps, how to model costs, and a clean process to test Renko honestly.

A Renko backtest can be trusted only if the bricks are built from real tick data, the fills are simulated on actual prices, and fees and slippage are included. Most default backtests on Renko charts skip at least one of these, which is why the equity curve looks so smooth and the live account does not. Below is how the distortion happens, what a sound test looks like, and how to run one yourself.

TL;DR

Renko bricks ignore time, so a backtest needs tick-level data to know the order of price moves inside a bar. Minute-bar Renko guesses it.
"Enter on the next brick" logic quietly peeks into the future and inflates results.
Renko strategies trade often on small moves, so costs and slippage can erase the whole edge.
The safer pattern: use Renko for the signal, and test fills against real OHLC price data.
Judge the result on win rate, profit factor and max drawdown, then check it on data the strategy never saw.

What makes Renko different to test
The three traps that inflate Renko backtests
Does Renko actually work? What the evidence says
A cleaner method: signal on Renko, fills on real prices
A worked checklist before you trust the numbers
Our perspective
How to test a Renko idea with Backtestify
Markets change: test across regimes
Can AI do the backtest for you?
FAQ
Sources

What makes Renko different to test

A Renko chart draws a new brick only when price moves a fixed amount, say 10 points, beyond the last brick. Time does not matter. Quiet hours produce nothing, and fast moves produce a stack of bricks. That is the appeal: noise is filtered out, and trends look clean.

The same property is the problem. A normal candle has an open, high, low and close at a known time. A Renko brick has no such anchor. When you ask software to replay history on bricks, it has to decide what happened between one brick and the next, and that decision is where backtests go wrong.

One practitioner write-up on testing Renko charts explains that when bricks are built from time-based data, the charting engine cannot see the fluctuations inside each bar. It simply stacks bricks from the low to the high or from the open to the close. The order it picks may not be the order the market actually traveled.

The three traps that inflate Renko backtests

1. Time-based data standing in for ticks

If your platform builds Renko from 1-minute or daily bars, a single bar that touched both a high and a low gets converted into bricks in an assumed sequence. Your strategy then "sees" a clean trend that may have been a whipsaw. The fix is tick-resolution data, where each trade is replayed in order. The same write-up notes that some popular charting packages do not offer true tick data, so check what your tool really uses before you trust any number it prints.

2. Next-brick entry and look-ahead bias

Many strategies say: "when the brick closes green, buy at the next open." On a Renko chart, the next brick only exists after price has already moved a full brick size in your direction. The test therefore assumes you got in with a brick of profit already made. The same source describes this as a future-looking positive bias that produces inflated equity curves. A QuantifiedStrategies guide to Renko trading also warns that look-ahead bias is the reason a Renko backtest needs careful handling.

A realistic rule: you can only act at the price available when the signal appears, not at the idealized price of a brick that has not yet formed.

3. Ignoring costs

Small bricks mean frequent signals. Frequent signals mean many fees, many spreads crossed, and many slippage events. Research on Renko-based algorithmic strategies points to the omission of transaction costs as a major pitfall: the apparent profit can vanish once handling fees, slippage and bid-ask spreads are modeled.

Researchers at the University of Warsaw make a related point about brick size: smaller thresholds increase trading frequency and sensitivity to transaction costs. Shrinking the brick to get more trades is rarely free.

Does Renko actually work? What the evidence says

The honest answer is that it depends on the strategy type and the market regime.

Academic work exists on both sides. A study on pairs trading using non-parametric Renko and Kagi constructions reported excess returns and strong risk-adjusted performance in its framework, with the 2013 paper citing monthly excess returns between 1.4% and 3.6% in certain pairs-trading contexts. That is a statistical-arbitrage setting with managed costs, not a retail breakout strategy on a single chart, so do not read it as a promise for yours.

Brick construction itself matters too. The Warsaw researchers describe an "overshoot" effect: price often moves past the threshold before a brick prints. According to their analysis, that can improve entry points for contrarian strategies while tending to erode profitability for trend-following ones. If you trade reversals off Renko, the overshoot may work for you. If you follow trends, it works against you. A piece on detecting trend reversals is a good companion read when you are deciding how entries should treat that overshoot.

On the professional side, Renko is mostly a lens. Market analyst David Weis, who teaches Renko-based reading of order flow, is featured by a San Francisco traders' association for using it to spot patterns like absorption and exhaustion. That is discretionary reading of market state, not a claim that a mechanical backtest on bricks validates a system.

Does Renko actually work? What the evidence says — overview diagram

A cleaner method: signal on Renko, fills on real prices

A widely used workaround is to separate two jobs. Renko decides what the market is doing (trend direction, a reversal brick). The execution test uses the underlying real price data to decide where you would actually have been filled. One empirical paper on an adaptive True Renko strategy describes this kind of practice: use Renko for signal identification while referencing real OHLC data to simulate order fills at real-world prices.

In practice this means:

Build the signal from bricks (for example, two consecutive up bricks after a down brick).
Timestamp the moment the signal first becomes true, not the moment the brick is later displayed.
Fill at the next available real price after that timestamp, plus spread and slippage.
Exit on real prices too: stops and targets are checked against actual highs and lows, not brick edges.

It is more work than flipping a chart style to Renko and pressing "run," but it is the difference between a test and a picture.

A worked checklist before you trust the numbers

Use this list on any Renko test, whether it is yours, a forum post's or a video's.

Question	Red flag	What good looks like
What data builds the bricks?	Minute or daily bars	True tick data, or a clearly stated approximation
Where is the entry filled?	Next brick open	Price at signal time, with slippage
Are costs included?	"Commission: 0"	Fees, spread and slippage per trade
How many trades?	A handful	Enough to judge a distribution, across several market conditions
Was it tuned on the same data?	Brick size picked from the best result	A test on data not used to choose parameters
Is drawdown shown?	Only net profit	Max drawdown beside profit factor and win rate

On execution costs, it helps to measure rather than guess. A guide on measuring and cutting trading slippage is a practical place to start before you set a slippage assumption in your test.

Brick size is a parameter, so test it like one

Brick size is the most influential setting, and the most abused. Pick the size that gave the best equity curve and you have overfit. Instead, test a range of sizes, and prefer a region where results are stable rather than a single spike. If 8-point bricks make money and 7 and 9 lose, you found noise. If 6 through 12 all produce a similar profit factor, you may have something.

Hypothetical results compare a spike with a stable range

Also consider whether the brick is fixed or based on ATR. A fixed size adapts poorly when volatility changes. An ATR-based size adapts, but it introduces its own lookback and, if computed with later data, another source of look-ahead.

More signals do not mean a better model

Do not assume a more complex predictor fixes things. A 2026 study of high-frequency, Renko-based machine learning found a gap between prediction accuracy and net returns: simple, cost-aware signal filters often beat deep-learning architectures once frictions were counted. Being right about direction more often is not the same as making money after costs.

Our perspective

We see the same pattern again and again with Renko strategies shared online. The chart looks beautiful, the video shows a handful of wins, and the claim stops there. What is missing is the unflattering part: the losing stretches, the drawdown, and what happens when the same rules meet a different market.

At Backtestify we built the platform around one idea: a strategy should be verified on real historical data before it gets your money, and the report should show winners and losers alike. When you test a strategy, look first at max drawdown and profit factor, not just win rate. A 70% win rate with small wins and rare large losses can still lose money, and Renko strategies are prone to exactly that shape, because the brick filter produces many small wins and the occasional sharp reversal.

Our advice is to treat Renko as a hypothesis generator. If a Renko idea survives a test with realistic fills, costs and out-of-sample data, it earned your attention. If it only works with a particular brick size on a particular instrument and period, it is a story, not an edge.

— WAJDI

How to test a Renko idea with Backtestify

Backtestify lets you describe a strategy in plain English, runs it against real historical market data, and reports each trade plus the key metrics: win rate, profit factor and max drawdown. You can then improve the rules and compare the original and improved versions side by side on recent data. Results can be exported in TradingView Pine script format, so you can move a verified idea back to your charts.

A sensible workflow for a Renko-inspired idea:

Write the rules as price-based conditions you can express on real data, such as a trend defined by consecutive moves of a fixed size.
Run the test and read the trade list, not only the summary.
Check max drawdown against what you could stomach in a live account.
Change one rule at a time, and keep the version that improves results on data the first version did not see.

If you are new to the process, our step-by-step guide to backtesting a trading strategy covers the basics, and our article on backtesting like a regulator explains the discipline behind trusting a result. Strategies are also easier to judge when you can see how a published one holds up, such as our report on a 50 EMA pullback with engulfing entry, which shows what a full evidence-based breakdown looks like.

Pricing

You can start on the Free plan. The Pro plan, which unlocks unlimited backtesting, improvement and forecasting, costs $29 per month or $190 per year. You can see both on the Backtestify home page.

Markets change: test across regimes

Renko strategies are especially regime-dependent. Trending markets produce long runs of same-color bricks. Choppy markets produce alternating bricks and repeated small losses. A test that spans only a strong trend will flatter any trend-following brick rule.

Split your history into rising, falling and sideways stretches and read the metrics for each. Our piece on regime detection and backtesting before you risk capital goes deeper on this. If the strategy only earns in one regime, you now know when to switch it off.

Can AI do the backtest for you?

People ask whether a chatbot can run the test. It can help write code, but it should not be your validator. A 2026 review notes that when QuantPedia asked ChatGPT-4 to backtest a simple risk-parity strategy in October 2023, the model computed volatility once and reused it across the whole year, which produced wrong results delivered with confidence. Brick construction from raw ticks is harder still. Use a tool that runs your rules on real market data and shows every trade.

FAQ

Can I rely on a Renko backtest in TradingView?

Treat it with caution. If the platform builds bricks from time-based bars rather than tick data, it has to guess the order of price moves inside each bar, and next-bar entries can give you a free brick of profit. Verify the entry price assumptions and add realistic costs before trusting the curve.

Are Renko charts profitable?

They can be in specific setups. Academic work has reported strong results for Renko-based pairs trading in a controlled framework, but other research shows costs and brick overshoot can erase the edge in trend-following. Profitability depends on the strategy, the brick size and the costs you pay.

Do professional traders use Renko charts?

Some do, mainly as a discretionary tool for reading trends and order-flow patterns such as absorption or exhaustion. They generally separate that visual read from the real price data used to test execution, rather than validating a system on bricks alone.

What brick size should I backtest?

Test a range, not a single value. Look for a neighborhood of sizes with similar profit factor and drawdown. A lone best size is usually overfitting, and smaller bricks raise trade count and cost sensitivity.

How many trades do I need for a Renko backtest?

There is no magic number, but a few dozen trades from one market phase proves little. Aim for a sample large enough to include winning and losing stretches, and confirm the results on a period you did not use to choose the settings.