
Channel
Z97 Official
@Z97_Official
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,708subscribers
-362 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002205980396 |
|---|---|
| Type | Channel |
| Username | @Z97_Official |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 21 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 21 October 2026 |
| On Telegram | t.me/Z97_Official |
Topic
Other / unclassifiable — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 21 Oct 2026, 08:09 | 4,708 | -14 |
| 17 Oct 2026, 22:50 | 4,722 | -22 |
| 15 Oct 2026, 07:06 | 4,744 | -28 |
| 11 Oct 2026, 23:40 | 4,772 | -46 |
| 5 Oct 2026, 16:41 | 4,818 | -94 |
| 27 Sept 2026, 21:37 | 4,912 | -63 |
| 18 Sept 2026, 08:58 | 4,975 | -31 |
| 13 Sept 2026, 16:58 | 5,006 | -39 |
| 10 Sept 2026, 01:16 | 5,045 | -21 |
| 4 Sept 2026, 22:21 | 5,066 | -4 |
| 3 Sept 2026, 12:09 | 5,070 | no change |
| 3 Sept 2026, 11:47 | 5,070 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@AFUNMX · 66,572
Telegram ranks this channel #10 of 57 here — alongside 56 others — read 28 September 2026
@MexswinOficial · 34,404
Telegram ranks this channel #11 of 55 here — alongside 54 others — read 3 September 2026
@TomateBetOficial · 19,921
Telegram ranks this channel #13 of 51 here — alongside 50 others — read 28 September 2026
@slots_big_win_mxg · 55,961
Telegram ranks this channel #14 of 59 here — alongside 58 others — read 3 September 2026
@brazino777mx · 22,499
Telegram ranks this channel #16 of 60 here — alongside 59 others — read 20 September 2026
@MXLOBO1 · 41,313
Telegram ranks this channel #16 of 58 here — alongside 57 others — read 3 September 2026
@chillbet_mexico · 38,345
Telegram ranks this channel #22 of 54 here — alongside 53 others — read 3 September 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 21 October 2026 — this entry's latest reading, not the date you are reading this.
“Z97 Official” (@Z97_Official), 4,708 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/Z97_Official.
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.