Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 95% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
34 measurements spanning 49 days, net +27,854. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 529,085–565,295 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)
Subscribers
Change
25 Sept 2026, 15:02
561,117
+3,970
19 Sept 2026, 04:21
557,147
+1,134
16 Sept 2026, 16:00
556,013
+1,040
14 Sept 2026, 16:58
554,973
+877
13 Sept 2026, 05:19
554,096
+606
11 Sept 2026, 04:40
553,490
+1,293
8 Sept 2026, 08:56
552,197
+1,547
5 Sept 2026, 05:37
550,650
+693
3 Sept 2026, 09:56
549,957
+883
2 Sept 2026, 00:33
549,074
+539
31 Aug 2026, 23:36
548,535
+754
31 Aug 2026, 00:28
547,781
+630
30 Aug 2026, 02:13
547,151
+165
29 Aug 2026, 05:42
546,986
+795
28 Aug 2026, 08:54
546,191
+1,020
27 Aug 2026, 11:08
545,171
+748
26 Aug 2026, 07:47
544,423
+818
25 Aug 2026, 05:36
543,605
+1,027
24 Aug 2026, 05:28
542,578
+759
22 Aug 2026, 13:43
541,819
first reading
Engagement
472 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 105 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
1.92%
avg views ÷ 561,117 subscribers
Avg views / post
10,800
256 posts measured
Reaction rate
0.308%
reactions ÷ views · ER floor
Posts in window
256
of 472 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 26 September 2026
Posts held
472 (5 August 2026 – 26 September 2026)
Views total
2,762,580
Reactions total
8,503
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
26 Sept 2026, 19:26 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈4,180
Videos
≈6
Links
≈4,180
Lifetime counters from Telegram’s own channel header, read 26 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
14,508 reactions across 471 posts, in 25 distinct kinds. The most used accounts for 56.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
8,165
56.3%
👍
3,748
25.8%
🔥
699
4.82%
🤩
576
3.97%
👌
555
3.83%
👨💻
206
1.42%
⚡
105
0.724%
👀
76
0.524%
✍
69
0.476%
🏆
69
0.476%
🤣
55
0.379%
🎉
47
0.324%
🤡
26
0.179%
👏
24
0.165%
🤔
20
0.138%
😁
17
0.117%
🤯
16
0.11%
👾
11
0.076%
🤝
6
0.041%
😎
5
0.034%
5 further kinds
13
0.09%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 471 of the 472 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 14,508 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 472 most recent posts we hold, published 5 August 2026 to 26 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Serial autocorrelation can remain hidden behind a clean equity curve. Lag-1 checks are insufficient; dependence often shows up at higher lags or across a block of lags.
The Ljung-Box portmanteau test addresses this by aggregating sample autocorrelations through horizon h into a single Q statistic and chi-square p-value. Residual diagnostics matter: if ARIMA/GARCH residuals remain autocorrelated, the model is leaving…
SAGDFN targets spatio-temporal forecasting bottlenecks by reducing redundant edges early. Significant Neighbors Sampling builds a sparse neighborhood per node using similarity-ranked candidates plus random picks to preserve diversity and limit overfitting.
Sparse Spatial Multi-Head Attention operates on the sparse graph and prunes weak links more aggressively via Entmax-style normalization. In practice, Sparse-SoftM…
Native MT5 chart objects make table UIs hard to maintain: RectLabel/Edit grids require manual coordinates, per-object styling, and tight synchronization. A reusable CTable class resolves this by separating cell state from rendering and centralizing layout and lifecycle.
Each cell stores width/height, colors, alignment, read-only, and description, plus “custom color” flags to protect overrides when defaults change. C…
Canvas-based MQL5 dashboards can remain visually correct while losing responsiveness when every hover, scroll, or popup triggers a full repaint and repeated OS text measurements. Under rapid interaction, event volume outpaces rendering and causes stutter.
A performance pass keeps output unchanged by combining frame throttling and partial rendering. Rendering is capped at ~16 ms per frame, collapsing event bursts int…
MQL5 can be extended with a small OS-style helper layer to standardize filesystem work, using native terminal APIs as building blocks. Coverage is narrower than Python, but enough for common file and folder tasks.
Core methods map cleanly: getcwd (via script path and parent), listdir, scandir with a lightweight DirEntry equivalent, remove (FileDelete), rmdir, rename/move (FileMove), mkdir (FolderCreate), and stat vi…
FX options desks work in delta space, not strike space. Standard quotes per expiry are ATM volatility, 25-delta risk reversal, and 25-delta butterfly, with optional 10-delta wings. Strikes are derived from these pillars plus an interpolation choice.
Equity-style tooling in MetaTrader 5 commonly starts from listed strike chains and single-rate Black-Scholes. For FX this misses both market quoting practice and the two…
Probability theory remains a practical dependency for trading systems, from strategy PnL estimates to risk models. Modern ML also inherits classical statistics: neural nets are probabilistic models optimized via maximum likelihood, with predictable strengths and limits.
A random variable is a deterministic function X(ω) on an assumed probability space Ω, used because Ω is rarely tractable directly. The working repre…
ATR-smoothed Heiken Ashi candles are drawn directly on the chart: blue for bullish and red for bearish. Smoothing is ATR-driven: if the new HA close deviates from the prior smoothed close by at least ATR x sensitivity, the candle uses raw HA values; otherwise open/close are blended via a configurable factor to suppress minor colour flips.
Trend bias is provided by Fast EMA (default 20) and Slow EMA (default 50). Ear…
MetaTrader 5 ships with MarketProfile, but it does not segment volume by individual swing legs. A swing-based profile can be built from OHLC and platform tick volume to study volume concentration inside each completed high-to-low and low-to-high move.
Core logic: confirm swing highs/lows using a configurable window and next-bar validation, then connect confirmed points with a ZigZag leg. For each finished leg, compu…
Double tops/bottoms look obvious in hindsight but are hard to automate because pivots, necklines, and tolerances are often subjective. This article turns the pattern into a deterministic contract suitable for MT5 Strategy Tester.
The MQL5 design confirms swing pivots using a fixed left/right bar window, then pairs two same-type pivots only if their prices match within a tolerance scaled by pattern height. The neckli…
MetaTrader 5 reports blend partial exits into a single result, hiding whether scaling out improved or weakened performance. This article builds a native MQL5 Scale-Out Value Analyzer that reconstructs positions from deal history, detects multi-exit closures, and evaluates scaling against counterfactual full exits using only the trader’s realized exit prices.
For each scaled position, it reprices the full volume at t…
Tree-based feature_importances_ (MDI) answers what the forest split on, not what a feature is worth. As features multiply, correlated indicators become interchangeable, and their “credit” gets diluted across copies, letting weak or even useless columns outrank a real signal with no warning.
Permutation importance (MDA) is out-of-sample but can fail harder: if a signal has duplicates, permuting one column leaves subs…
❤13👍7🤩4🔥2
Showing the 12 most recent of 472 posts we hold for @mql5dev. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 15 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
MetaTrader Hints @metatrader_hints · 36,118 Telegram ranks this channel #1 of 47 here — alongside 46 others — read 3 September 2026
Trading Algorítmico MQL5 @mql5es · 45,474 Telegram ranks this channel #1 of 61 here — alongside 60 others — read 28 August 2026
FBS Analytics @fbsanalytics · 86,876 Telegram ranks this channel #8 of 84 here — alongside 83 others — read 17 August 2026
FundedNext Official Channel @FundedNextOfficialCommunity · 61,312 Telegram ranks this channel #29 of 77 here — alongside 76 others — read 22 August 2026
ETI - English @eti_algos · 38,775 Telegram ranks this channel #31 of 59 here — alongside 58 others — read 30 August 2026
Register KFX VIP / VVIP 🇮🇩 @registerkfxvip · 44,861 Telegram ranks this channel #45 of 74 here — alongside 73 others — read 27 August 2026
Octa Analytics @octa_analytics · 75,529 Telegram ranks this channel #59 of 84 here — alongside 83 others — read 19 August 2026
TMA OFFICIAL® @TMAbyArty · 24,938 Telegram ranks this channel #69 of 86 here — alongside 85 others — read 14 September 2026
FXStreet Forex News @fxstreetforex · 103,471 Telegram ranks this channel #71 of 88 here — alongside 87 others — read 15 August 2026
This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Domains linked from posts
4 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 25 September 2026 — this
entry's latest reading, not the date you are reading this.
“MQL5 Algo Trading” (@mql5dev), 561,117 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/mql5dev.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.
