Channel
بوعبدالعزيز الكويتي 🇰🇼
@bu_aziz_q8
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,277subscribers
-94 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 | -1001836078782 |
|---|---|
| Type | Channel |
| Username | @bu_aziz_q8 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/bu_aziz_q8 |
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 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 |
|---|---|---|
| 15 Sept 2026, 07:39 | 4,277 | -13 |
| 11 Sept 2026, 14:18 | 4,290 | -24 |
| 7 Sept 2026, 04:58 | 4,314 | -10 |
| 3 Sept 2026, 23:33 | 4,324 | no change |
| 2 Sept 2026, 08:24 | 4,324 | -14 |
| 30 Aug 2026, 12:56 | 4,338 | +3 |
| 27 Aug 2026, 02:17 | 4,335 | +2 |
| 24 Aug 2026, 12:33 | 4,333 | -11 |
| 20 Aug 2026, 17:04 | 4,344 | -4 |
| 13 Aug 2026, 17:37 | 4,348 | -10 |
| 10 Aug 2026, 20:36 | 4,358 | -13 |
| 7 Aug 2026, 19:01 | 4,371 | 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.
@bu3oof_fx · 36,057
Telegram ranks this channel #26 of 88 here — alongside 87 others — read 31 August 2026
@QamarAlali16 · 48,458
Telegram ranks this channel #43 of 85 here — alongside 84 others — read 27 August 2026
@Captain_kw · 40,767
Telegram ranks this channel #46 of 84 here — alongside 83 others — read 30 August 2026
@join_events · 49,632
Telegram ranks this channel #56 of 65 here — alongside 64 others — read 13 September 2026
@MT_TRADING00 · 32,826
Telegram ranks this channel #59 of 73 here — alongside 72 others — read 4 September 2026
@cfijgroup · 38,798
Telegram ranks this channel #75 of 79 here — alongside 78 others — read 31 August 2026
This channel appears in 6 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“بوعبدالعزيز الكويتي 🇰🇼” (@bu_aziz_q8), 4,277 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/bu_aziz_q8.
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.