MQL5 Algo Trading
Open in Telegram
The best publications of the largest community of algotraders. Subscribe to stay up-to-date with modern technologies and trading programs development.
Show moreπ Analytical overview of Telegram channel MQL5 Algo Trading
Channel MQL5 Algo Trading (@mql5dev) in the English language segment is an active participant. Currently, the community unites 519 842 subscribers, ranking 150 in the Technologies & Applications category and 5 in the United Kingdom region.
π Audience metrics and dynamics
Since its creation on Π½Π΅Π²ΡΠ΄ΠΎΠΌΠΎ, the project has demonstrated rapid growth, gathering an audience of 519 842 subscribers.
According to the latest data from 10 July, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 10 295 over the last 30 days and by 470 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 3.24%. Within the first 24 hours after publication, content typically collects 1.90% reactions from the total number of subscribers.
- Post reach: On average, each post receives 16 837 views. Within the first day, a publication typically gains 9 858 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 38.
- Thematic interests: Content is focused on key topics such as indicator, chart, mql5, candle, range.
π Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
βThe best publications of the largest community of algotraders.
Subscribe to stay up-to-date with modern technologies and trading programs development.β
Thanks to the high frequency of updates (latest data received on 11 July, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
519 842
Subscribers
+47024 hours
+3 3907 days
+10 29530 days
Data loading in progress...
Similar Channels
Tags Cloud
Incoming and Outgoing Mentions
---
---
---
---
---
---
Attracting Subscribers
July '26
July '26
+4 798
in 5 channels
June '26
+9 701
in 6 channels
Get PRO
May '26
+10 784
in 10 channels
Get PRO
April '26
+10 664
in 10 channels
Get PRO
March '26
+22 886
in 10 channels
Get PRO
February '26
+25 031
in 6 channels
Get PRO
January '26
+26 330
in 10 channels
Get PRO
December '25
+22 353
in 4 channels
Get PRO
November '25
+21 953
in 11 channels
Get PRO
October '25
+24 933
in 4 channels
Get PRO
September '25
+19 967
in 5 channels
Get PRO
August '25
+17 145
in 4 channels
Get PRO
July '25
+18 909
in 10 channels
Get PRO
June '25
+18 135
in 9 channels
Get PRO
May '25
+17 357
in 2 channels
Get PRO
April '25
+19 677
in 0 channels
Get PRO
March '25
+19 081
in 0 channels
Get PRO
February '25
+18 865
in 1 channels
Get PRO
January '25
+19 658
in 0 channels
Get PRO
December '24
+17 881
in 0 channels
Get PRO
November '24
+23 274
in 0 channels
Get PRO
October '24
+25 611
in 3 channels
Get PRO
September '24
+23 810
in 0 channels
Get PRO
August '24
+32 845
in 0 channels
Get PRO
July '24
+39 916
in 0 channels
Get PRO
June '24
+14 429
in 0 channels
Get PRO
May '24
+1 105
in 0 channels
Get PRO
April '24
+1 407
in 0 channels
Get PRO
March '24
+2 180
in 0 channels
Get PRO
February '24
+1 456
in 0 channels
Get PRO
January '24
+1 276
in 0 channels
Get PRO
December '23
+4 228
in 0 channels
| Date | Subscriber Growth | Mentions | Channels | |
| 11 July | +397 | |||
| 10 July | +476 | |||
| 09 July | +475 | |||
| 08 July | +567 | |||
| 07 July | +735 | |||
| 06 July | +691 | |||
| 05 July | +311 | |||
| 04 July | +184 | |||
| 03 July | +207 | |||
| 02 July | +459 | |||
| 01 July | +296 |
Channel Posts
This article upgrades the classic SuperTrend by making its ATR multiplier responsive to momentum divergence, using MPO4 (or optionally RSI) as the trigger. When a validated bullish/bearish divergence appears, a βshrinkingβ rule reduces the multiplier by a sensitivity factor, pulling the band closer to price. The result is tighter trailing stops near exhaustion and earlier flips for capturing the next trend.
A key focus is non-repainting behavior in MT5 indicators. Instead of fragile global flags, the design persists divergence context per bar via state buffers (last pivot prices/osc values, last divergence type, bars-since counter). State is propagated forward each iteration and reset on trend flips, keeping historical signals stable across ticks, refreshes, and restarts.
Implementation details cover a chart-window MQL5 indicator with a colored SuperTrend...
π Read | Docs | @mql5dev
| 2 |  Price-window indicators in MQL5 often shift arrays with ArrayCopy() on every bar to keep index 0 as βlatestβ. That design is O(n) per update and scales poorly with large periods, multi-symbol sets, and dense OnCalculate() workloads.
A circular buffer removes the shift. Only a head index advances with modulo arithmetic, and one slot is overwritten. Push and Get become O(1) regardless of window size; allocation is fixed at construction.
An MQL5 template CCircularBuffer<T> fits this pattern but comes with constraints: no specialization, template code must stay in-header, and capacity must be runtime. Statistical routines should use two-pass variance to avoid cancellation common in price series.
Result: less memory movement per bar, improved backtest throughput, and reduced live tick latency under load.
π Read | Signals | @mql5dev | 5 635 |
| 3 |  False breaks of recent N-bar highs/lows often act as liquidity sweeps: price runs stops beyond an obvious extreme, then closes back inside the range. The article turns this into a fully testable Turtle Soup contract: minimum sweep depth (points and % of range), minimum age of the swept level, sweep-window rules, and close-based rejection confirmation (multiple closes, optional reversal body).
The MQL5 implementation focuses on robustness: bar-close execution, duplicate-signal guards, per-direction position caps, and broker stop-level compliance. Stops can be dynamic beyond the sweep extreme or fixed-point; targets support R-multiple projection or the opposite side of the lookback range, with optional trailing.
It also builds chart tooling (levels, sweep zones, risk/reward boxes) and a scan engine using iHighest/iLowest and close checks, ready for S...
π Read | CodeBase | @mql5dev | 6 298 |
| 4 |  Mean-reversion implementation in MetaTrader 5: weekly channel breaks using two moving averages on High and Low with a shared period. Break above the upper band triggers short bias; break below the lower band triggers long bias.
Signal confirmation uses an ONNX-backed statistical model plus daily open/close moving averages for directional filtering. Data pipeline exports EURUSD daily bars to CSV via MQL5, then trains in Python on 2011β2019 and tests on 2020β2026. Model selection highlights overfitting in flexible learners; a linear regressor is chosen and exported to ONNX.
The EA loads the ONNX model, manages trades via magic number filtering, updates indicator buffers, and applies ATR-based symmetric SL/TP with trailing stops. Backtests with real ticks and random delay show modest positive expectancy, profit factor near 1.1, and larger average win...
π Read | Calendar | @mql5dev | 6 899 |
| 5 |  Most MT5 risk tools implicitly cap worst-case planning to what the recent window already contains. ATR, bootstrapped trade resampling, and historical VaR all operate on observed volatility and outcomes, so tail losses beyond the sample are systematically understated.
Financial returns are fat-tailed, so rare moves occur more often than normal assumptions imply. Extreme Value Theory addresses this by modeling only the tail, allowing extrapolation beyond the historical maximum loss.
An MQL5-native implementation can use Peaks-Over-Threshold with a Generalized Pareto fit via ALGLIB MLE. Outputs include EVT VaR, Expected Shortfall, and a shape parameter that quantifies tail heaviness, with hard refusal to report metrics when exceedances are insufficient.
π Read | Signals | @mql5dev | 7 092 |
| 6 |  Protecting profit after a position is opened typically requires rules that react to price movement, not just the entry signal. Common approaches include moving the stop loss to breakeven after a defined profit threshold, then switching to a trailing stop to lock in gains as volatility expands or contracts.
A structured method uses staged stop management: initial fixed stop, breakeven activation, and trailing based on points, ATR, or recent swing levels. Partial closes can reduce risk while keeping exposure for continuation. Controls such as minimum distance, step size, and spread filters help avoid premature stop-outs in noisy conditions.
π Read | AlgoBook | @mql5dev | 7 862 |
| 7 |  Replay/simulation work in MQL5 is moving past sockets and SQL basics into chart-side tooling needed for realistic interaction.
Current components (mouse pointer, Chart Trade indicator, EA messaging) can submit market execution, but cross-orders and replay symbols lack reliable visual feedback for positions and orders.
Next step is a minimal position-visualization indicator. An indicator can read position state and print details, without attempting trade actions, which remain EA-only. This also highlights a platform constraint: indicators share a single chart thread, so the logic must avoid blocking and unnecessary updates.
Focus shifts to controlled chart objects for position lines, with attention to object lifecycle and cleanup to prevent long-term chart degradation.
π Read | Docs | @mql5dev | 7 599 |
| 8 |  MetaTrader 5 hides powerful βindicator-likeβ behavior inside chart objects. By programmatically repurposing OBJ_FIBO, the article builds a custom risk tool that visually marks entry, stop, and target using only a few configured levels.
The core technique sets a fixed number of Fibonacci levels, then assigns each level its value, color, and style via parallel arrays. Using values outside 0..1 turns Fibonacci into a projection engine, making it easy to express 1:1, 1:1.5, and partial-exit layouts that canβt be recreated manually from the UI.
Practical refinements include locking selection to prevent accidental moves, hiding unwanted guide lines, exposing a stop/target ratio as an input, and optionally disabling right-side extension so multiple analyses can coexist cleanly. The article also explores switching drawing flow toward left-click interaction, ...
π Read | Signals | @mql5dev | 7 135 |
| 9 |  This article extends the MCP approach from trading execution to the full development workflow by connecting AI agents to MQL5 Algo Forge, a Git-based host backed by Forgejo. Using its HTTPS REST API, an assistant can programmatically create repos, commit EA files, manage branches, open pull requests, file issues, and publish releases.
The server is a portable Python project (no MetaTrader/Windows dependencies) built in layers: JSON config + token, an httpx-based API client with consistent error normalization, domain handlers, and a FastMCP tool surface exposing 12 tools.
Key implementation details include safe token handling (config or environment variable) and Base64 encoding/decoding for file endpoints. A single βcommit fileβ tool abstracts POST vs PUT by detecting existing files and retrieving sha automatically, enabling reliable updates without t...
π Read | Docs | @mql5dev | 6 829 |
| 10 |  Reliable MT5 Expert Advisors require systematic validation before sending trade requests. Common constraints include max positions/orders, volume min/max/step, SL/TP distance, margin, session limits, symbol permissions, and news filters. Market publication tests already enforce many of these cases, so reusable checks reduce duplication and regressions.
A compact MQL5 validator set can cover: lot sizing with step-based normalization (avoids retcode 10014), SL/TP distance vs SYMBOL_TRADE_STOPS_LEVEL, price digit normalization (avoids retcode 10015), freeze-level checks for order modifications, margin/funds checks, and βno changesβ guards to prevent TRADE_RETCODE_NO_CHANGES.
Additional utilities include: pending-order limits, lightweight new-bar detection, tradability checks for SYMBOL_TRADE_MODE_DISABLED, calendar-based news windows (live only), and UTC sess...
π Read | Signals | @mql5dev | 6 969 |
| 11 |  This part adds a pinned-tools ribbon to complement the deep, tabbed sidebar: the sidebar stays optimized for discovery, while the ribbon provides one-click access to a small set of frequently used drawing tools. The ribbon auto-hides when empty and preserves pin order.
Pinned tools are stored in the engine as an ordered list with a minimal API (count, get, contains, pin/unpin, toggle). Pinning appends; unpinning compacts the array without reordering, keeping behavior predictable.
A shared anti-aliased pushpin glyph is rendered via polygon coverage and alpha blending, reused consistently across flyout rows, the Pinned sidebar tile, and the ribbon.
The ribbon is a floating surface with drag, resize, and horizontal scrolling. It clips overflowing icons using an offscreen canvas and shows a proportional scrollbar thumb, keeping interaction smooth eve...
π Read | NeuroBook | @mql5dev | 7 662 |
| 12 |  Walk-Forward Analysis is reframed as a measurable robustness test for MT5 EAs: optimize on in-sample windows, score degradation on forward windows, and summarize it as a reproducible metric instead of eyeballing equity curves.
The core score is Walk-Forward Efficiency (WFE): per-window ratio of out-of-sample to in-sample Sharpe. Windows pass only if they retain at least 50% efficiency, with guards that force failure when in-sample Sharpe is non-positive or too small to be meaningful.
A native MQL5 pipeline implements the full loop: an EA logs per-bar equity to CSV, a fast reader ingests it, WFE_Engine.mqh computes Sharpe/WFE with numerical stability and validity flags, and a CCanvas histogram renders pass/fail windows and reference lines directly on-chart for immediate diagnosis.
π Read | Calendar | @mql5dev | 8 488 |
| 13 |  KCI Embedded Sniper is an algorithmic reversal-entry EA built around a fully embedded Kinetic Compression Index engine. KCI math (Velocity Quotients, Kinetic Displacement, Energy Dispersion, Phase Velocity) runs inside the EA, avoiding iCustom() latency and thread desynchronization. Signals are computed on closed bars only, targeting non-repainting execution with Singularity exhaustion validation and a Williams %R momentum gate.
The design removes external indicator files, reducing memory overhead and eliminating indicator path, loading, and buffer read errors. Computation is event-driven via rates_total and internal matrices, optimized for multi-asset operation in a single process loop.
Risk and filtering are parameterized: fixed lot sizing, ED-based dynamic SL/TP scaling, WPR period and extreme levels, plus KCI sensitivity controls (ZScorePeriod, Compress...
π Read | Docs | @mql5dev | 9 321 |
| 14 |  The Kinetic Compression Index (KCI) is a custom oscillator for detecting market exhaustion and localized compression events. It computes kinematic-style metrics directly inside the indicator loop, reducing reliance on multiple external indicator handles and simplifying EA buffer management.
The design exposes reproducible components such as Velocity, Deviation, and Dispersion, with Z-Score normalization applied over a rolling window before forming a composite KCI value. Signal buffers are built to validate on closed bars to reduce intrabar repainting and async tick timing issues.
A unified buffer map is central to integration: KCI main line and color index, buy/sell signal buffers, plus internal calculation arrays including Velocity Quotient, Kinetic Displacement, Energy Dispersion (usable as a volatility proxy for SL/TP logic), Phase Velocity, and R...
π Read | Forum | @mql5dev | 9 709 |
| 15 |  A Smart Money Concepts (SMC/ICT) market-structure indicator for MetaTrader 5 that derives structure from swing-high/swing-low sequencing and renders the current state directly on the chart.
Swing points are detected via N-bar fractals and plotted as arrows. Breaks are classified as BOS when price closes beyond the prior swing in the trend direction, and as CHoCH when the close exceeds the prior swing against the trend. On each structure break, the last opposite candle is flagged as an Order Block. Fair Value Gaps are identified as 3-candle imbalance zones. After a CHoCH, QML draws a dotted retrace level at the left-shoulder swing.
Key inputs include swing sensitivity, close vs wick confirmation, lookback bars, and per-feature toggles with configurable colors. Runs on any symbol and timeframe, recalculating on every new bar with close-confirmed markings.
π Read | Docs | @mql5dev | 10 264 |
| 16 |  A trading-journal export script pulls raw account history from the terminal and writes it to a single CSV in one run.
The script loads deals for the last N days, then aggregates them into closed positions by position ID. It works on both netting and hedging accounts and supports partial fills. Entry and exit prices are volume-weighted across all entry and exit deals per position.
Each CSV row includes: position ID, symbol, direction, volume, open time and VWAP open price, close time and VWAP close price, points result (direction-aware), commission, swap, net profit, duration (minutes), and the first deal comment for strategy-level filtering.
Inputs cover: period (days), file name (or auto TradeJournal_YYYY-MM-DD.csv), CSV separator (default β;β for Excel), optional common-folder output, and an optional current-symbol filter. Output goes to MQL5\Files o...
π Read | Signals | @mql5dev | 10 443 |
| 17 |  A position sizing script calculates lot size directly on the active chart symbol using a user-defined risk budget (percent of equity or fixed account currency) and stop-loss distance (points or explicit price level).
The calculation pulls live contract specs: tick size and tick value for money-per-point conversion, then applies volume min/max/step rules. Output is normalized by rounding down to the volume step so risk does not exceed the limit, and the exact risk at the normalized size is reported.
Margin is estimated for the intended direction using OrderCalcMargin. Clear warnings are generated when free margin is insufficient, when the computed size is below the symbol minimum (minimum volume exceeds the risk budget), or when the result is capped at the symbol maximum.
A full report is printed to the chart Comment, Experts journal, and a single-line Alert....
π Read | NeuroBook | @mql5dev | 10 125 |
| 18 |  Spread Monitor Panel is a lightweight on-chart panel for tracking the live spread of the current chart symbol, refreshed every second. Spread is calculated from Ask-Bid in points, avoiding issues with integer symbol properties on float-spread accounts.
The panel reports current spread plus minimum, average, and maximum since attachment, including sample count and start time. Current value is color-coded against user thresholds: green below warning, orange between warning and danger, red at or above danger.
Optional alerting triggers when spread remains at or above the danger threshold for a configurable number of consecutive seconds, with a cooldown to prevent repeated notifications during spikes. Configuration includes thresholds, alert settings, panel corner, offsets, and font size.
Designed for monitoring only: no trades, buffers, or plots. Suitabl...
π Read | Quotes | @mql5dev | 10 983 |
| 19 |  o you have Expert Advisors written in MQL4 and think migrating them to MetaTrader 5 will take too much time? Let's check this out right now.
We'll take an existing Expert Advisor from the MQL5.com CodeBase, feed it into ChatGPT, generate an MQL5 version, compile it in MetaEditor, and run it in the Strategy Tester. The entire process will take just a few minutes.
If you don't want to work with the code or handle the migration manually, there's an even easier option. MQL5.com offers a Freelance service where you can hire professional developers to convert Expert Advisors, indicators, and other applications.
Discuss the video:
π MQL5.community for traders
π MetaQuotes official YouTube channel | 14 290 |
| 20 |  MetaTrader 5 EA portability often fails due to broker-specific symbol identifiers, not strategy logic. Variants like EURUSD, EURUSDm, EURUSD.fx, GOLD, XAUUSD.a, or US30.cash can break SymbolSelect, bid/ask reads, and OrderSend, sometimes without explicit errors.
A broker-agnostic symbol layer addresses this with deterministic translation, terminal validation, caching, and CSV persistence. Resolution is defined as testable behavior: Resolve("EURUSD") returns a selectable symbol with non-zero quotes, or an empty result with logging.
Architecture splits responsibilities into modules: mapping storage, resolver with hash-based lookup plus controlled discovery, a small resolution cache, a host verification EA for live checks, and a benchmark tool for latency measurement.
π Read | AlgoBook | @mql5dev | 13 301 |
