Telegram RegisterThe public register of Telegram
Telegram profile photo for MQL5 Trading Algorithmique

Channel

MQL5 Trading Algorithmique

@mql5fr

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

55,609subscribers

+5,507 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002213404207
TypeChannel
Username@mql5fr
DescriptionLes meilleures publications de la plus grande communauté de traders algorithmiques. Abonnez-vous pour rester au courant des dernières technologies et du développement des programmes de trading.
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/mql5fr

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 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 the other topics.

Growth

50,10255,60952,855.57 August 202617 November 2026
65 measurements spanning 102 days, net +5,507. 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 49,276–56,435 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
17 Nov 2026, 20:2755,609+191
14 Nov 2026, 17:5155,418+119
11 Nov 2026, 19:3855,299+61
9 Nov 2026, 22:0055,238+50
8 Nov 2026, 14:3555,188+11
7 Nov 2026, 07:4855,177+15
6 Nov 2026, 08:1955,162+13
5 Nov 2026, 04:5755,149+23
4 Nov 2026, 07:2655,126+30
3 Nov 2026, 06:4755,096+47
2 Nov 2026, 07:1955,049+17
1 Nov 2026, 04:2755,032+9
31 Oct 2026, 03:1155,023+29
30 Oct 2026, 05:4954,994+63
29 Oct 2026, 09:1554,931+69
28 Oct 2026, 07:0654,862+34
27 Oct 2026, 08:3954,828+37
26 Oct 2026, 05:3954,791+23
25 Oct 2026, 02:3754,768+50
23 Oct 2026, 23:4954,718first reading

Engagement

253 posts held, back to 30 July 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 208 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.75%
avg views ÷ 55,609 subscribers
Avg views / post
2,090
75 posts measured
Reaction rate
0.214%
reactions ÷ views · ER floor
Posts in window
75
of 253 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. It is computed over the 63 of 75 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 November 2026
Posts held253 (30 July 2026 – 18 November 2026)
Views total156,478
Reactions total286
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 11:59 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
≈2,100
Videos
≈6
Links
≈2,100

Lifetime counters from Telegram’s own channel header, read 18 November 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.

Video runtime
2m 31s
Average length
2m 31s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

1,440 reactions across 238 posts, in 17 distinct kinds. The most used accounts for 82.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,19282.8%
👍755.21%
👌553.82%
🔥402.78%
⚡171.18%
✍171.18%
🤔100.694%
👀70.486%
🎉50.347%
🤯50.347%
🏆30.208%
👨‍💻30.208%
🤓30.208%
🤝30.208%
🤨20.139%
🤩20.139%
😱10.069%

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 239 of the 253 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 1,440 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 253 most recent posts we hold, published 30 July 2026 to 18 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 75 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

18 Nov 2026, 07:00 UTC520 views2 reactionsread 18 November 2026
Photo

La fonction « Equity Guard » pour Prop Firm vise à sécuriser un compte face aux règles fréquentes des sociétés de trading pour compte propre. Le module surveille le capital en continu et, dès qu’un seuil est atteint, clôture toutes les positions, annule les ordres en attente et bloque toute nouvelle exécution jusqu’à la fin du verrouillage. Compatible avec le trading manuel et avec d’autres Expert Advisors, sans jama…

❤2

18 Nov 2026, 05:00 UTC618 viewsread 18 November 2026
Photo

La fonction « Session High Low » projette sur le graphique les sessions Asie, Londres et New York. Chaque période est encadrée par un rectangle coloré entre l’heure de début et de fin, en intégrant le plus haut et le plus bas atteints. Après clôture, des pointillés prolongent ces niveaux pendant quelques heures pour visualiser rapidement cassures et retests. L’intérêt est opérationnel : la fourchette asiatique sert …

17 Nov 2026, 07:00 UTC≈1,540 views6 reactionsread 18 November 2026
Photo

QCL Heikin Flow pour MT5 met en œuvre un Heikin Ashi lissé en deux étapes afin de réduire le bruit et de rendre la lecture de tendance plus stable. Le module sépare un lissage primaire du prix et un lissage secondaire des valeurs HA, chacun paramétrable en période et en méthode de moyenne mobile (EMA, SMA, SMMA, LWMA). L’implémentation repose sur 24 buffers: séries de sortie en bougies (haussières, baissières, neutr…

❤6

17 Nov 2026, 05:00 UTC≈1,410 views2 reactionsread 18 November 2026
Photo

Un nouvel indicateur prolonge le détecteur de pullback en construisant une structure de marché SMC au-dessus des oscillations confirmées. Le code est autonome, sans dépendance, et alimente la structure barre clôturée par barre clôturée. Deux couches coexistent. La première produit un zigzag de retracement strictement alterné et confirmé avec retard. La seconde conserve seulement les points utilisés par la structure,…

❤2

16 Nov 2026, 07:00 UTC≈1,970 views7 reactionsread 18 November 2026
Photo

VelaMayor MTF est un indicateur de visualisation multi-périodes pour MetaTrader 5, orienté analyse multi-timeframe, SMC, price action et méthodologies ICT. Il projette les dernières bougies d’une unité supérieure (H1, H4, D1) directement sur l’unité d’exécution (M1, M5, M15), sans navigation entre graphiques. Le rendu est géré en double couche, avec contours et remplissages indépendants pour améliorer le contraste s…

❤7

16 Nov 2026, 05:00 UTC≈1,720 viewsread 18 November 2026
Photo

Un simulateur de risque de marge calcule, pour un symbole donné, les cours auxquels le compte atteindrait l’appel de marge et le stop out définis par le courtier. Il sert à estimer l’impact d’un ajout de X lots sur le niveau de marge et à déterminer le volume additionnel maximal conservant un niveau de sécurité. L’outil fonctionne sous forme d’Expert Advisor uniquement pour accéder aux fonctions de calcul de profit …

15 Nov 2026, 05:00 UTC≈2,150 views3 reactionsread 18 November 2026
Photo

Une variante optimisée de l’indicateur AMA (Adaptive Moving Average) de Kaufman est disponible, avec un rendu visuel identique à la version d’origine. La version initiale a été optimisée en décembre 2006 afin de faciliter son utilisation dans des Expert Advisors. La variante non optimisée pouvait consommer davantage de ressources, ce qui impactait la durée des backtests et des phases d’optimisation lorsque l’EA effe…

❤3

14 Nov 2026, 07:00 UTC≈2,380 views6 reactionsread 18 November 2026
Photo

Plusieurs sociétés de gestion de portefeuille ferment un compte dès que la limite de perte quotidienne est atteinte. Un indicateur permet d’afficher ces niveaux directement sur le graphique, sans calcul manuel. Sont affichés : solde de début de journée (déduit de l’historique), niveau de capital lié à la limite journalière, perte courante en valeur et en pourcentage de la limite, marge restante avant dépassement, et…

❤6

14 Nov 2026, 05:00 UTC≈2,110 views3 reactionsread 18 November 2026
Photo

Les filtres de session d’un Expert Advisor sont exprimés en heure serveur, définie par l’horloge du courtier. Selon les infrastructures, cette horloge reste en UTC, ou bascule entre UTC+2 et UTC+3, avec des week-ends de changement différents selon les calendriers US et EU. Résultat : un créneau « 10:00–13:00 » peut devenir faux plusieurs semaines par an. Un outil d’audit peut déduire le décalage serveur sans dépendr…

❤3

12 Nov 2026, 07:00 UTC≈3,110 views9 reactionsread 18 November 2026
Photo

Les outils de suivi des challenges prop se limitent souvent à une perte journalière. ATS Prop Rules Monitor regroupe les cinq contraintes sur un seul tableau avec l’espace restant : perte journalière (incluant le flottant, optionnel, et heure de rollover configurable), perte maximale (statique ou ajustée equity/balance), progression vers l’objectif, jours de trading validés, et règle de « meilleure journée » si appli…

❤9

12 Nov 2026, 05:00 UTC≈2,590 views4 reactionsread 18 November 2026
Photo

Un indicateur technique calcule la fourchette de la séance asiatique par jour (00:00–07:00 UTC par défaut) et l’affiche sous forme de rectangle. L’hypothèse opérationnelle est une consolidation nocturne suivie d’une sortie fréquente à l’ouverture de Londres. Dans la fenêtre de cassure (07:00–11:00 UTC), un signal BUY/SELL est posé sur la première bougie clôturée au-delà des bornes de la fourchette, avec une marge de…

❤3👍1

11 Nov 2026, 09:00 UTC≈2,730 views8 reactionsread 18 November 2026
Photo

Le filtrage de tendance L1 vise une estimation robuste des séries temporelles financières, en supprimant le bruit court terme tout en préservant la dynamique long terme. La sortie est une tendance linéaire par morceaux, avec détection automatique des ruptures de pente, là où les lissages classiques (moyennes mobiles, Hodrick–Prescott) introduisent du retard et masquent les changements de régime. La régularisation se…

❤7👍1

Showing the 12 most recent of 253 posts we hold for @mql5fr. 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 1 registered channel — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

Cite this entry

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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“MQL5 Trading Algorithmique” (@mql5fr), 55,609 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/mql5fr.

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.