Channel
Diroz
@diiroz
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,996subscribers
-35 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002181473438 |
|---|---|
| Type | Channel |
| Username | @diiroz |
| Description | 18,19 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 21 September 2026 |
| Measurements held | 14 |
| On Telegram | t.me/diiroz |
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 21 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 Sept 2026, 01:13 | 1,996 | no change |
| 19 Sept 2026, 06:36 | 1,996 | -9 |
| 14 Sept 2026, 18:39 | 2,005 | -15 |
| 11 Sept 2026, 01:37 | 2,020 | +15 |
| 6 Sept 2026, 09:14 | 2,005 | -10 |
| 1 Sept 2026, 17:56 | 2,015 | +11 |
| 30 Aug 2026, 04:04 | 2,004 | -12 |
| 27 Aug 2026, 10:35 | 2,016 | +13 |
| 24 Aug 2026, 20:34 | 2,003 | +2 |
| 21 Aug 2026, 03:55 | 2,001 | -16 |
| 17 Aug 2026, 19:33 | 2,017 | -9 |
| 14 Aug 2026, 20:46 | 2,026 | -2 |
| 11 Aug 2026, 17:26 | 2,028 | -3 |
| 7 Aug 2026, 18:18 | 2,031 | 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.
@extasymind · 170,711
Telegram ranks this channel #16 of 61 here — alongside 60 others — read 27 August 2026
@Xray_Cloud · 33,153
Telegram ranks this channel #28 of 37 here — alongside 36 others — read 22 September 2026
@peikee_akhar · 37,472
Telegram ranks this channel #36 of 71 here — alongside 70 others — read 1 September 2026
This channel appears in 3 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 September 2026 — this entry's latest reading, not the date you are reading this.
“Diroz” (@diiroz), 1,996 subscribers as measured 21 September 2026. Telegram Register, tgregister.com/channel/diiroz.
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.