Channel
WHY ABUZ
@why_abuz
On this record: Topic · Growth · Engagement · Cite this entry
4,067subscribers
-98 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001997802509 |
|---|---|
| Type | Channel |
| Username | @why_abuz |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/why_abuz |
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 13 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 |
|---|---|---|
| 11 Oct 2026, 16:56 | 4,067 | -10 |
| 5 Oct 2026, 03:39 | 4,077 | -16 |
| 15 Sept 2026, 13:20 | 4,093 | -5 |
| 11 Sept 2026, 15:39 | 4,098 | -3 |
| 6 Sept 2026, 15:56 | 4,101 | +5 |
| 4 Sept 2026, 23:44 | 4,096 | no change |
| 2 Sept 2026, 08:07 | 4,096 | -10 |
| 29 Aug 2026, 23:02 | 4,106 | -10 |
| 26 Aug 2026, 23:16 | 4,116 | -10 |
| 23 Aug 2026, 12:46 | 4,126 | -7 |
| 20 Aug 2026, 04:35 | 4,133 | -9 |
| 16 Aug 2026, 22:23 | 4,142 | -7 |
| 13 Aug 2026, 14:18 | 4,149 | -13 |
| 10 Aug 2026, 21:11 | 4,162 | -1 |
| 8 Aug 2026, 01:37 | 4,163 | -2 |
| 7 Aug 2026, 12:39 | 4,165 | 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“WHY ABUZ” (@why_abuz), 4,067 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/why_abuz.
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.