javellda has dealt 7416 Damage to Reddbeard's Stingray! They receive 5 Doubloons and nothing!!

Channel
Hopper Squire 2.0
@hoppersquire
On this record: Topic · Growth · Engagement · Posts · Cite this entry
61subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001123197850 |
|---|---|
| Type | Channel |
| Username | @hoppersquire |
| Created | Between 1 June 2017 and 29 February 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 3 October 2026 |
| On Telegram | t.me/hoppersquire |
Topic
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 28 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 00:16 | 61 | -1 |
| 10 Aug 2026, 03:46 | 62 | no change |
| 6 Aug 2026, 20:20 | 62 | first reading |
Engagement
20 posts held, back to 3 May 2022 — 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 20 posts for this entry, the most recent from 3 May 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
javellda has dealt 9551 Damage to Hopper Reddbeard! They receive 1 Doubloons and nothing!!
javellda has returned from the 7 Seas with 2 Doubloons
javellda has returned from Reddbeard Island with 4 Doubloons
StarReacher24 has dealt 1027 Damage to the Swarm Boss! It has 533993 Health remaining!
StarReacher24 has graciously helped the youth of the Hopper Farm. They have been left with 5 Fresh Diapers!
T_Cnor has just returned from the treacherous Swamp with 5 Nugs for the Swarm!
T_Cnor has dealt 353 Damage to the Swarm Boss! It has 535020 Health remaining!
T_Cnor has dealt 287 Damage to Reddbeard's Stingray! They receive 2 Doubloons and nothing!!
Scalf5 has dealt 648 Damage to the Swarm Boss! It has 4281608 Health remaining!
PtkKamillus has dealt 10706 Damage to the Swarm Boss! It has 4282256 Health remaining!
PtkKamillus has returned from Reddbeard Island with Rare Pirate Hopper
Showing the 12 most recent of 20 posts we hold for @hoppersquire. 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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Hopper Squire 2.0” (@hoppersquire), 61 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/hoppersquire.
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.