Sillers: Automated MT5 trading expert delivering trend breakout accuracy and reliable profit management

This Sillers review for 2026 presents a clear performance analysis based on live monitoring and technical breakdowns. Sillers is designed to combine trend breakout signals with trend-following confirmation on higher timeframes, and this review examines entry logic, exit mechanics, and live account results to provide objective context. The 2026 performance and strategy analysis focuses on measured risk controls, trade frequency, and expected return behavior rather than marketing claims. What makes Sillers unique is the pairing of multi-timeframe confirmation with strict, fixed stop losses and an automated trailing stop mechanism. The algorithm scans higher timeframes for a validated momentum shift, then waits for an intraday breakout opportunity to execute on MT5. Sillers also uses a total profit closing rule that scales targets relative to account size; that approach simplifies position management and gives a deterministic closing criterion. Salavat Yulamanov, the developer, publishes live performance metrics which helps validate the system under real market conditions. In practice Sillers handles trending environments best, particularly strong directional moves in FX and major metal pairs when volatility confirms breakouts. Risk management emphasizes small per-trade exposure, frequent but selective entries, and automatic profit protection. Expected performance characteristics include moderate win rates with positive risk-reward per trade, drawdowns contained by fixed stops, and compounding potential when combined with conservative position sizing. Sillers aims to offer reliable, long-term stability on MT5 rather than short-term high-frequency gains.

Typical results for Sillers show a mix of conservative win rate and favorable risk-reward characteristics. Based on live-account samples, win rates are often in the 45-65% range depending on instrument selection and timeframe, with average winners larger than average losers due to trend-following exits. Drawdown management relies on fixed stop losses and trailing stops, which historically have limited peak drawdowns to mid single-digit percentages on carefully sized accounts in monitored samples. Trade frequency is moderate: expect several to a few dozen trades per month depending on volatility and instrument choice. Account requirements start at micro accounts for testing, with recommended minimum live size of $1,000 to $5,000 when using default lot-sizing and conservative risk settings. Timeframe considerations favor H4 and daily higher timeframe confirmation with lower timeframe execution to capture breakouts; traders should align chart timeframes to those settings for cleaner signals.

Sillers is best described as a moderate-risk automated system when configured with recommended parameters. The fixed stop loss provides clear per-trade risk, and the trailing stop reduces exposure as trades move into profit. Position sizing is intended to be conservative by default; users are encouraged to risk no more than 0.5-2% of equity per trade depending on account size and tolerance. Vulnerabilities include range-bound or highly choppy markets where breakout signals can produce false entries and small losses. Sudden major news events can widen spreads and increase slippage, impacting results. For practical use, a recommended account size is at least $1,000 for testing and $5,000 or more for a live allocation with sensible lot sizing.

Install Sillers by copying the EA file into the MT5 Experts folder, then restart the terminal so the expert advisor appears in the navigator. Attach Sillers to a chart, enable automated trading, and confirm permissions for DLL and live trading if required. Key parameters to configure include fixed stop loss size, trailing stop activation, total profit closing percentage, and initial lot sizing or risk-per-trade. Recommended brokers are ECN or low-spread brokers with reliable execution and low slippage. Optimal chart timeframes use higher timeframe confirmation such as H4 or Daily with lower timeframe execution. Backtest and forward-test on a demo account for at least 2-3 months before deploying live.