4 measurements spanning 7 days, net +5. 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 50–58 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 02:34
57
+6
10 Aug 2026, 10:46
51
no change
7 Aug 2026, 01:21
51
-1
6 Aug 2026, 02:02
52
first reading
Engagement
8 posts held, back to 24 December 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
145.6%
avg views ÷ 57 subscribers
Avg views / post
83.0
1 post measured
Reaction rate
2.41%
reactions ÷ views · ER floor
Posts in window
1
of 8 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 3 August 2026
Posts held
8 (24 December 2021 – 3 August 2026)
Views total
83
Reactions total
2
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Aug 2026, 10:46 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
4 reactions across 3 posts, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
4
100.0%
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 3 of the 8 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 24 December 2021 to 3 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.
⚡️Did you know LagoFast does more than just fix your ping?
Getting zero lag is great, but combining it with our FPS Boost feature is a game-changer. It automatically optimizes your PC settings to squeeze out every last frame per second for games like Warzone and FC26.
🛠Go to the 'FPS Boost' tab in your app, turn it on, and feel the difference today!
🆔LagoFast
📦THE WAIT IS OVER! Our Monthly Promo Code is LIVE!⚡️
As promised, here is your highly limited code to unlock ultra-low ping, 0% packet loss, and max FPS on PC, Console, or Mobile.🚀
🔥YOUR PROMO CODE:
CASB6YJL
⚠️ First Come, First Served!
The fastest member to redeem this inside their LagoFast app takes the win for this month. Run and get it!💨
⬇️ Did you get it?
Drop a comment below and let us know! Let's see …
🚨ATTENTION LAGOFAST SQUAD!🚨
We are dropping our ONLY exclusive promo code of the month very soon! 📦🔥
Because this is a highly limited monthly drop, it will be strictly First Come, First Served. If you want to lock in the ultimate ping and FPS boost, you need to be fast.⚡️
🔔Turn on channel notifications right NOW so you don't miss the drop. The fastest member takes it!
Are you ready?⏳
🆔LagoFast
🪂Dropping into Verdansk? Don't let lag send you back to the lobby!
If you play Call of Duty: Warzone, you already know how sweaty the lobbies can get. The last thing you need is a lag spike when you're in a 1v1 for the win.🏆
LagoFast offers specialized routes just for the current Warzone servers. It stabilizes your connection, eliminates packet burst, and helps you find the most optimal servers for your match.🌐…
🛞Which path is your connection taking right now?
Take a look at the blueprint below:
❌The standard route (red path) is full of congestion, packet loss, and pure frustration.
✅But once you toggle LagoFast, it instantly reroutes your traffic through our dedicated Game Booster nodes (green path), ensuring a direct, lightning-fast line straight to the game servers.
🙂Ready to switch to the happy path?
If you haven't te…
🙂See that rising graph? It’s not just about Ping. Let’s talk about FPS!
Did you know LagoFast doesn't just fix your network, but also significantly boosts your hardware performance?🖥⚙️
With the built-in FPS Boost feature, you can optimize your PC with a single click. It automatically closes unnecessary background processes, unparks CPU cores, and tweaks system settings to push your frame rates to the absolute ma…
🎮Tired of lagging out right when you're about to clutch the round?
Say goodbye to high ping, packet loss, and frustrating disconnects!🚀
Meet LagoFast - the ultimate Game Booster designed specifically for competitive gamers.
👀Look at the impact in the image:
🌐We take you from a messy "HIGH PING" route to the direct, optimized "LOW PING" path.
📈See your connection stabilize-transforming from a choppy 150ms down…
Showing the 8 most recent of 8 posts we hold for @lagofast. 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 — 278,899 of 1,345,403entries 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.
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.
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 13 August 2026 — this
entry's latest reading, not the date you are reading this.
“LagoFast Community” (@lagofast), 57 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/lagofast.
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.