Telegram RegisterThe public register of Telegram
Telegram profile photo for SmiteFX Algo Hub | MQL5 & Hedge Fund

Channel

SmiteFX Algo Hub | MQL5 & Hedge Fund

@SmiteFX_AlgoHub

On this record: Previous handles · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

169subscribers

+29 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004427397002
TypeChannel
Username@SmiteFX_AlgoHub
CreatedBetween 1 June 2026 and 22 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/SmiteFX_AlgoHub

Previous handles

@SmiteFX_AlgoHub was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@SmiteFXAlgoHub
held 8 August 20268 August 2026

Growth

140169154.57 August 2026 — 140 subscribers8 August 2026 — 140 subscribers15 August 2026 — 146 subscribers21 August 2026 — 155 subscribers29 August 2026 — 169 subscribers7 August 202629 August 2026
5 measurements spanning 22 days, net +29. 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 136–173 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 03:44169+14
21 Aug 2026, 05:30155+9
15 Aug 2026, 05:28146+6
8 Aug 2026, 22:16140no change
7 Aug 2026, 11:00140first reading

Engagement

29 posts held, back to 22 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
528.1%
avg views ÷ 169 subscribers
Avg views / post
893
16 posts measured
Reaction rate
1.16%
reactions ÷ views · ER floor
Posts in window
16
of 29 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
WindowRolling 30 days · latest post in window 21 August 2026
Posts held29 (22 July 202621 August 2026)
Views total14,280
Reactions total166
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Aug 2026, 05:30 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.

Reaction mix

320 reactions across 29 posts, in 6 distinct kinds. The most used accounts for 40.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
13140.9%
🥰8727.2%
🔥8225.6%
🎉134.06%
😍51.56%
🏆20.625%

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

Measured over the 29 most recent posts we hold, published 22 July 2026 to 21 August 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

21 Aug 2026, 01:32 UTC256 views11 reactionsread 21 August 2026
Photo

🏰 FORTRESS EA — +100% VERIFIED LIVE GROWTH There were winning periods, losing periods, drawdowns and recovery — exactly what real trading looks like. ✔️ No Grid/Martingale ✔️ Stop Loss Protection ✔️ Six-in-One Breakout Strategies ✔️ Risk-based & Dynamic Lot Sizing ✔️ Continuous Updates and Responsive Support ✔️ Climbing New Highs Everyday! 🏆 ✔️ Proprietary Breakout Algo 📊 ⭐️ Growing collection of positive user rev

4🥰4🔥2😍1

14 Aug 2026, 06:05 UTC980 views10 reactionsread 21 August 2026
Photo

🚀 LIMITED-TIME DEAL: GET FORTUNE EA + 2 BONUS EAs FREE! That means you get: ✔️ Get 3 professional trading systems for the price of 1! ✔️ Get more than $1,299 worth of products! ✔️ View verified live trading results! ✔️ Choose the EA combination that suits your trading style ⌛ This bundle is available for a limited time. Secure your preferred combination before the offer ends! ➡️ VIEW THE VERIFIED LIVE SIGNAL: http

5🥰3🔥2

14 Aug 2026, 04:51 UTC≈1,030 views12 reactionsread 21 August 2026
Photo

NEW BLOG POST 🖥 Why Your EA Needs a VPS (And What Happens If It Doesn't) Your EA is only "automated" for as long as it's actually connected. A closed laptop lid, a dropped home connection, a Windows update mid-trade — none of these are exotic scenarios, and any one of them can take your EA offline at exactly the wrong moment. In this week's post, we break down: 🔹 What a VPS actually does (and why it's infrastruct

5🥰5🎉2

14 Aug 2026, 01:48 UTC920 views14 reactionsread 21 August 2026
Photo

🚀 LIMITED-TIME OFFER: BUY FORTRESS EA & GET 2 BONUS EAs FREE! That means you receive: ✔️ 3 professional trading systems for the price of 1 ✔️ A bundle valued at over $1,299 ✔️ Access to verified live trading results ✔️ The freedom to build an EA combination that matches your trading style ⭐️ This offer is available for a limited time only. Secure Fortress EA and select your 2 bonus EAs before the promotion ends. ➡

8🔥3🥰2🎉1

11 Aug 2026, 09:03 UTC≈1,980 views9 reactionsread 21 August 2026
Photo

🚀 FORTUNE EA — 1,000%+ VERIFIED LIVE GROWTH ✔️ No Grid/Martingale ✔️ Verified Live Results ✔️ Fixed Take Profit & Stop Loss ✔️ Climbing New Highs Everyday! 🏆 ✔️ Proprietary Breakout Algo + AI Calibrations 📊 ⭐️ Growing collection of positive user reviews 🤝 Active support and an exclusive user community 🎁 Limited Bonus: Get 2 additional EAs with your Fortune EA purchase. ➡️ VIEW THE VERIFIED LIVE SIGNAL: https://ww

🥰43🎉2

11 Aug 2026, 05:57 UTC≈1,850 views5 reactionsread 21 August 2026
Photo

🏰 FORTRESS EA — BUILT FOR DISCIPLINED GOLD TRADING Fortress is designed for traders who prefer a structured XAUUSD breakout system without grid, martingale or recovery stacking. ✔️ Six-in-One Breakout Strategies ✔️ No Grid/Martingale & Fixed TP/SL ✔️ Risk-Conscious Strategy Design ✔️ Continuous Updates and Responsive Support ✔️ Climbing New Highs Everyday! 🏆 ✔️ Proprietary Breakout Algo + AI Calibrations 📊 ⭐️ Grow

3🥰2

10 Aug 2026, 11:40 UTC108 views11 reactionsread 21 August 2026
Photo

🚀 FORTUNE EA — 1,000%+ VERIFIED LIVE GROWTH ✔️ No Grid/Martingale ✔️ Verified Live Results ✔️ Fixed Take Profit & Stop Loss ✔️ Climbing New Highs Everyday! 🏆 ✔️ Proprietary Breakout Algo + AI Calibrations 📊 ⭐️ Growing collection of positive user reviews 🤝 Active support and an exclusive user community 🎁 Limited Bonus: Get 2 additional EAs with your Fortune EA purchase. ➡️ VIEW THE VERIFIED LIVE SIGNAL: https://ww

🥰63🔥2

9 Aug 2026, 18:02 UTC≈1,060 views9 reactionsread 21 August 2026
Photo

NEW BLOG POST 📊 Backtest vs. Live: Why the Numbers Never Match Exactly Ever wonder why your live account never quite matches the backtest? It's one of the most common questions in algo trading — and usually the gap isn't a broken strategy, it's a measurement problem. In this week's post, we break down: 🔹 Why tick simulation ≠ real market ticks 🔹 How spread and execution differ by broker 🔹 The slippage and latency

4🥰3🔥2

9 Aug 2026, 07:29 UTC≈1,000 views11 reactionsread 21 August 2026
Photo

🚀 LIMITED-TIME DEAL: GET FORTUNE EA + 2 BONUS EAs FREE! Purchase Fortune EA for only $249 and choose 2 additional EAs at no extra cost. 🎁 ✔️ Get 3 professional trading systems for the price of 1! ✔️ Get more than $1,299 worth of products! ✔️ View verified live trading results! ✔️ Choose the EA combination that suits your trading style ⌛ This bundle is available for a limited time. Secure your preferred combination

🔥4🥰43

8 Aug 2026, 03:53 UTC994 views11 reactionsread 21 August 2026
Photo

🚨 TARGET REACHED — FINAL DAY BEFORE PRICE INCREASE 🚨 We’ve officially hit our sales milestones: 🏆 Fortune EA — 100 copies sold 🏰 Fortress EA — 51 copies sold A huge thank you to everyone who has supported SmiteFX and trusted our trading systems. As promised, today is the final day to purchase both EAs at their current prices. FORTUNE EA Current Price: $199 New Price: $249 FORTRESS EA Current Price: $99 New Pric

4🔥4🥰3

7 Aug 2026, 02:52 UTC926 views12 reactionsread 21 August 2026
Photo

🏰 FORTRESS EA FEATURE SPOTLIGHT Three Risk Profiles. One Strategy Engine. Fortress EA isn't one-size-fits-all. Every account is different, so Fortress ships with three trading profiles — same underlying multi-strategy engine, different risk exposure — so you can match the EA to your own risk tolerance instead of the other way around. Backtest period: 1 Jan 2025 – 31 Dec 2025 | $10,000 initial deposit | 100% real t

4🔥4🥰3🏆1

6 Aug 2026, 18:03 UTC932 views10 reactionsread 21 August 2026

🚨 FORTRESS EA PRICE INCREASE — FINAL 5 COPIES AT $99 🚨 Fortress EA has now reached 45 copies sold. 📦 45 sold ⌛ 5 copies remaining at $99 📣 New price after that: $149 ✔️ No Grid ✔️ No Martingale ✔️ Stop Loss protection on every trade ✔️ Dynamic lot sizing ✔️ Lot size adjusted as account equity changes ✔️ Automatic trailing management ✔️ MT4 and MT5 versions ✔️ Verified live performance available ➡️ VIEW THE VERIFI

4🔥4🥰2

Showing the 12 most recent of 29 posts we hold for @SmiteFX_AlgoHub. 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.

Citation-graph rank

Citation-graph rank — 244,674 of 1,629,518 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“SmiteFX Algo Hub | MQL5 & Hedge Fund” (@SmiteFX_AlgoHub), 169 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/SmiteFX_AlgoHub.

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.