Understand a Renko Stochastic divergence strategy: its signal, entry confirmations, swing-based stop-loss, exit choices and limitations, with an example MT5 robot implementation.
Explore EA #001 Renko Divergence — MT5 robot →
What is the strategy trying to capture?
The method looks for a disagreement between successive price pivots and Stochastic readings on a Renko sequence. It then waits for a separate confirmation before entering. Its hypothesis is that a new price extreme accompanied by a weaker oscillator extreme may precede a reversal. That is a hypothesis to test, not a prediction that every divergence will reverse.
There are three separate decisions: whether a valid divergence exists, whether an entry trigger confirms it, and how to manage the position. Keeping these decisions separate helps explain why two divergence robots can take different trades on the same market.
Renko is the representation used to organize price movement; it is not the complete trading strategy. Our Renko chart guide explains fixed bricks, two-box reversals and synthetic-price limitations. This article focuses on how those bricks are used in the documented method.
How does regular Stochastic divergence work?
A bullish candidate pairs a lower second price low with a higher second Stochastic low. A bearish candidate pairs a higher second price high with a lower second Stochastic high. The comparison must use the intended corresponding pivots and the strategy’s defined oscillator values. A visually appealing line drawn after the outcome is known is not a reproducible signal rule.
The documented EA uses confirmed Renko pivots and configurable conditions such as pivot separation, minimum movement between pivots, Stochastic difference, zones and signal freshness. These conditions determine which candidates survive. Exact parameter meanings belong to the versioned manual; changing them changes the experiment.
Pivot confirmation can require subsequent bricks. Consequently, the second pivot’s plotted location and the time the algorithm can recognize it are different. Testing must use the latter. An entry cannot legitimately assume that a pivot was known at its lowest or highest price before confirmation.
Five documented entry confirmations
EA #001’s product documentation lists five selectable entry modes. They are alternative ways to confirm the divergence candidate, not five independent guarantees of a reversal.
- Micro CHOCH: wait for a local structure break in the intended direction.
- Fractal Trendline Break: wait for a break of a Renko fractal trendline.
- First of Both: use the first valid CHOCH or trendline trigger.
- Liquidity Sweep: use a wick breach and reclaim around the second divergence pivot.
- Level Confirm: require a defended pivot area followed by two or three aligned bricks.
A confirmation generally changes signal timing and entry distance. A later entry can avoid some unconfirmed candidates while leaving less distance to a target or requiring a different stop distance. Compare complete net outcomes rather than assuming that additional confirmation automatically improves a strategy.
Optional Renko SMA and broker-server trading-hour filters can restrict new entries. Long/short permissions, signal lifetime and retry rules also affect behavior. Record them with the test. Trading hours must be interpreted in the broker server’s clock rather than guessed from your local time.
Stop-loss, sizing and two exit approaches
The documented implementation uses a physical swing-based stop-loss with a configurable box buffer. Percentage-of-balance risk and fixed-lot sizing are alternatives. A fixed lot does not imply fixed monetary risk when the stop distance or instrument changes. A percentage input describes intended sizing; gaps, slippage and execution can make a realized loss differ.
Pure Renko exits after the configured number of consecutive opposite bricks. This ties the decision to the generated sequence. The actual exit price still depends on the broker instrument’s quotes and execution when the decision becomes known.
Fixed RR sets a target relative to the initial hard-stop distance. A planned two-R target does not guarantee that realized average winners equal two R. Costs, fills and stop execution remain part of the outcome. The physical stop described in the manual remains a separate protection under both approaches.
A hypothetical bullish setup, step by step
Suppose two confirmed price pivots are at 100 and 98 while their corresponding Stochastic readings are 18 and 25. Price made a lower low; the oscillator made a higher low. These invented values illustrate the divergence comparison only. They do not establish that the EA’s additional filters would accept the setup.
- Confirm that the pivots were recognizable using only information available at that time.
- Check spacing, oscillator conditions, freshness and any enabled filters.
- Wait for the selected entry confirmation. If it does not arrive before the signal expires, skip the candidate.
- Use the executable quote at the entry decision, then calculate the documented swing stop and sizing.
- Manage the position using the selected exit mode and the physical stop.
For an arithmetic illustration, an entry at 101 and initial stop at 97 create a four-unit price distance. A two-R target would be 109 before costs and execution differences. These are arbitrary price units, not a preset or instrument-specific recommendation. Monetary exposure also depends on contract size, tick value and volume.
When can the method fail?
Price can continue trending despite repeated divergence. An oscillator disagreement does not force an immediate reversal. Sideways conditions can also produce alternating confirmations and repeated losses. A Renko chart may look orderly while the executable market prices remain costly or volatile.
Brick size changes pivots, oscillator observations, confirmation timing and stop placement. Small bricks can magnify the relative cost burden; larger bricks can delay recognition. Sparse data, gaps, history rebuilding and inconsistent construction rules can alter the sequence. The settings cannot be transferred blindly between broker symbols.
The product page includes a supplied historical test with substantial drawdown and an extended losing sequence. Treat that report as an example for one configuration, period and broker—not evidence that every version of this method has an edge. Software runtime, preset compatibility and licensing verification remain part of release preparation.
How to research the strategy in MT5
- Record the EA version, Renko generator rules, box units, broker symbol and all inputs.
- Inspect sample signals visually, checking when pivots and confirmations actually became known.
- Include realistic spread, commission, financing and execution assumptions.
- Compare neighboring brick sizes and a small, predefined set of confirmation choices.
- Keep independent validation data and inspect drawdown, trade concentration and holding times.
- Compare demo signal timing and actual fills with the historical assumptions.
Use the MT5 backtesting guide and optimization guide for the broader process. More combinations create more opportunities to select an accidental historical peak.
MT5 implementation: EA #001 — Renko Divergence
Our configurable robot implements the documented Renko/Stochastic method with the five entry modes, two exit approaches and optional filters described above. Its product page contains version information, settings, the supplied historical report, source materials, price and current release status.
Release in preparation: purchases are currently unavailable. Publishing the strategy explanation does not certify runtime behavior or activate sales. Refer to the product page for the current verification status.
Sources and scope
Implementation details are based on the supplied EA #001 user manual, v1.2 and the published product documentation. The worked example is original and hypothetical. This is a description of this documented method, not a universal specification for every Renko divergence strategy.
Written by MT5 Robot Lab · Updated 6 October 2026.