Kiwi and Roo: Automated MT4 Trading on AUDCAD/NZDCAD with Verified Results

In this 2026 review of Kiwi and Roo we present a clear performance and strategy analysis that explains what separates this EA from traditional grid systems. Kiwi and Roo is a mean-reversion grid Expert Advisor built specifically for AUDCAD and NZDCAD on the M15 timeframe; the algorithm tracks a calculated fair-value level and opens offsetting grids when price deviates beyond user-set thresholds. The design focuses on opening in both directions to capture reversion opportunities while maintaining independent control over each grid. What makes Kiwi and Roo unique is the combination of dual independent grids and a tiered position sizing scheme that deliberately reduces lot-size multipliers as the grid deepens, then holds lots flat after a configured level. This reduces capital escalation risk that typical doubling grids face. The EA also exposes threshold, step, and maximum grid depth parameters so traders can tune aggressiveness to account equity and risk appetite. Nattapad Salasawadi developed the strategy to work within the liquidity profiles of AUDCAD and NZDCAD and to limit exposure during trending bursts. In practice Kiwi and Roo performs best in range-bound or mean-reverting market conditions on M15 where deviations from fair value are frequent but not extended. The expected performance characteristics include moderate trade frequency, episodic drawdowns during trends, and recovery potential as the grid reverts. Backtests and live samples indicate stable expectancy when configured conservatively, but outcomes depend on precise parameter selection and disciplined risk management in live MT4 accounts.

Typical performance for Kiwi and Roo centers on a win-rate that varies by configuration but often sits in the 55–70% range on individual trades when optimized for AUDCAD and NZDCAD. Overall system expectancy depends on the tiered sizing and grid spacing; when set conservatively the EA targets steady monthly returns rather than large single-trade profits. Drawdown management is primarily handled by reducing multipliers deeper in the grid and by configurable maximum grid depth and equity stop limits. Trade frequency is moderate on M15, averaging several trades per week per pair depending on volatility. Minimum account requirements vary with risk tolerance; a $5,000 to $10,000 account is a reasonable starting point for conservative settings, while more aggressive settings require proportionally larger capital. Timeframe considerations are straightforward: optimized for M15 and not recommended for much higher or lower timeframes without retesting.

Risk level for Kiwi and Roo is moderate when configured conservatively and can move toward aggressive if grid depth and multipliers are left high. The EA does not use a fixed single-stop-loss per trade in the traditional sense; instead it relies on grid spacing, multiplier reduction, and optional account-level equity stops to cap losses. Position sizing is tiered, intentionally reducing multiplier values as the grid deepens and holding lots flat beyond a set level to avoid runaway risk. Vulnerabilities include extended trending moves in one direction that exceed grid recovery expectations and low-liquidity conditions during news events. For most users a recommended account size of $5,000 or higher provides a practical margin buffer for conservative settings.

Install Kiwi and Roo by copying the EA file into the MT4 Experts folder, then restart MT4 and attach the EA to the AUDCAD and NZDCAD M15 charts. Configure key parameters such as deviation threshold, grid step, initial lot size, multiplier reduction schedule, maximum grid depth, and equity stop limits before enabling auto-trading. Use brokers with low spreads and reliable execution; ECN or low-spread STP brokers are preferred for grid strategies. Keep the charts on M15 and disable other EAs on the same account during testing. Run a forward test on a demo account for at least 3 months and validate results with a backtest covering multiple market conditions before deploying on live accounts.