Channel
@hoppersleague
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
95subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002315327986 |
|---|---|
| Type | Channel |
| Username | @hoppersleague |
| Created | 9 October 2024 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/hoppersleague |
Gaming — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 22:37 | 95 | -1 |
| 11 Sept 2026, 01:58 | 96 | -1 |
| 1 Sept 2026, 02:14 | 97 | -2 |
| 9 Aug 2026, 11:03 | 99 | no change |
| 7 Aug 2026, 14:14 | 99 | first reading |
11 posts held, back to 9 October 2024 — 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 3 January 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos 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.
45 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 48.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 22 | 48.9% | |
| 👍 | 6 | 13.3% | |
| ⚡ | 5 | 11.1% | |
| ❤ | 3 | 6.67% | |
| 🏆 | 3 | 6.67% | |
| 😁 | 3 | 6.67% | |
| 🎅 | 2 | 4.44% | |
| 👏 | 1 | 2.22% |
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 7 of the 11 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 45 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 9 October 2024 to 3 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
New year, new beginnings!💫So, we're turning a new page. That means we'll be working hard to keep you informed about all things game-related. There is a feeling in the air that this year is going to be packed with news, so get ready! 🎉🎮 Stay tuned! 🚀
❤3👍2🔥2⚡1
Rushing into 2025 with Ton Hopper 💵🐔💵
🔥4⚡3😁3🎅2
Wow, the soft launch starts – get ready for the most fun-filled game in the TON ecosystem! https://t.me/ton_go_gamebot/ton_go
🔜 The TON Hopper beta test is coming to an end, and very soon the project will enter a new stage! 🌐 💼 Thank you to all Hoppers! We now have over 10,000 players — we’re grateful to each of you for participating in the TON Hopper beta! ⚡️ A special shoutout to our active Hoppers — there are over 2,000 of you! Thanks to you, this phase has been truly exciting. 🧩 By the way, there’s a hint on the screenshot about wha…
👍3🏆2
Want some fun? Want rewards? Then hop hop into game! https://t.me/tonhopper_bot/tonhoppergame
🔥11
Video, posted without a caption
🎉 Starting Beta Test! 🚀 Hoppers, it’s time to jump into the action! We're officially starting the beta test, and your adventure begins now. 🏃♂️💨 Get ready to explore, play, and share your feedback — every hop brings us closer to the full release! ⚡️
🔥4
Channel photo updated
🚀 TON Hopper: Alpha Launch is Here! @tonhopper_bot Hoppers, it’s time to take the first hop into the future! 🎮 We’re opening access to the alpha version of TON Hopper, and you’re one of the first to experience the dynamic 3D runner with meme characters that will soon shake up the GameFi world! 🌍 Please note that features are currently limited, but from this launch, you’ll see new updates and content being added ov…
🏆1👏1
TON Hopper is our first step into the world of GameFi, and very soon we will move to the next level with Web3 integration! 🚀 In this launch, you’ll be able to enjoy a dynamic 3D runner with meme characters and unique gameplay right inside Telegram. Your support plays a key role in the development of the project! 💪 🔥 In the near future, we will add Web3 features, offering real rewards for active play and participati…
⚡1👍1🔥1
Channel created
Showing the 11 most recent of 11 posts we hold for @hoppersleague. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“TON Hopper Network” (@hoppersleague), 95 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/hoppersleague.
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.