NeoBank: Automated MT5 trading with verified performance and flexible risk controls

This NeoBank review delivers a focused 2026 performance analysis using both backtest snapshots and live account summaries. The NeoBank: 2026 Performance data shows how the algorithm deploys hedge and grid methods while tracking weighted average exit logic. In this review and analysis we examine win ratios, average trade duration, and drawdown behavior with attention to deterministic parameters and developer transparency. NeoBank is unique because it separates BUY and SELL cycles, allowing simultaneous hedging without interdependent stop orders. The EA does not use per-order take profit or stop loss; instead it calculates the weighted average open price of the active side and exits all positions on that side when conditions are met. Angel Torres designed NeoBank to start a new cycle only when no positions exist for that side, limiting overlapping multi-cycle exposure. The algorithm uses a stepped distance in points and increases lot size per stage, applying a progressive lot-sizing model that can accelerate recovery but raises capital and risk needs. The EA suits markets with defined mean reversion or oscillation and handles choppy sessions better than persistent single-direction trends. Performance characteristics typically show moderate win rates on individual trades but larger profits when basket exits succeed; expect variable drawdown depending on multiplier settings and stage count. NeoBank is priced at $30 and carries a 4.5/5 rating across 100 reviews on the marketplace, and the review evaluates that track record against realistic account sizing and risk tolerance for MT5 users.

NeoBank's performance profile centers on basket outcomes rather than single-order wins. Typical win rate expectations per order may appear modest since many orders serve as leg entries for later basket closure; reported account-level win rates from sample tests often range between 40 and 60 percent for individual orders, while closed-basket profitability can be higher. Drawdown management depends heavily on stage count and lot multiplier; conservative settings produced smaller peak drawdowns near 10 to 20 percent in tests, while aggressive multipliers increased risk substantially. Trade frequency varies with market volatility and chosen timeframes, with more frequent cycles on lower timeframes and fewer but larger baskets on H1 and above. Account requirements should match risk profile: testers recommended a minimum balance proportional to the chosen multiplier, typically several thousand dollars for aggressive setups. Timeframe considerations emphasize testing on M30 to H4 for balanced behavior, and live monitoring on MT5 VPS setups to ensure consistent execution.

NeoBank is best categorized as moderate to aggressive risk depending on configuration, because the grid/martingale elements increase exposure as a losing cycle progresses. There is no per-order stop loss; the EA relies on basket-level exit logic which acts as the stop or take-profit mechanism. Position sizing follows a progressive model where initial lot multiplies per stage, so traders must set conservative initial lots and tight stage limits if they want to limit capital drawdown. Vulnerabilities include prolonged strong trends where hedges and grids can accumulate large adverse exposure, and sudden market gaps where execution slippage amplifies losses. Recommended account size depends on multiplier and steps, but a conservative minimum for live trading is often several thousand dollars to absorb drawdowns and allow the EA room to work.

Install NeoBank on MT5 by copying the EA file into the Experts folder and restarting the platform. Attach NeoBank to the chosen chart and enable automated trading in MT5. Configure key parameters such as initial lot size, lot multiplier, stage distance in points, maximum stages, and enable hedge cycles for BUY and SELL. Recommended broker types include low-spread ECN or STP brokers with reliable execution and low slippage. Optimal chart timeframes to start testing are M30 and H1, then validate on H4 for lower-frequency behavior. Run a thorough backtest, then forward test on a demo account before deploying live.