Channel
کـاژِهـ
@kuzheh
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,168subscribers
-47 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001650956961 |
|---|---|
| Type | Channel |
| Username | @kuzheh |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/kuzheh |
Topic
Personal blog — 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 4 October 2026 and assigned it the closest of 31 fixed categories, at 80% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 08:47 | 1,168 | -4 |
| 1 Nov 2026, 21:59 | 1,172 | -1 |
| 29 Oct 2026, 22:38 | 1,173 | -5 |
| 26 Oct 2026, 15:51 | 1,178 | -1 |
| 23 Oct 2026, 12:47 | 1,179 | -1 |
| 20 Oct 2026, 20:45 | 1,180 | -3 |
| 15 Oct 2026, 01:19 | 1,183 | +2 |
| 11 Oct 2026, 18:20 | 1,181 | -1 |
| 5 Oct 2026, 10:14 | 1,182 | -7 |
| 4 Oct 2026, 17:57 | 1,189 | no change |
| 27 Sept 2026, 02:36 | 1,189 | -7 |
| 18 Sept 2026, 04:40 | 1,196 | +2 |
| 13 Sept 2026, 22:41 | 1,194 | -4 |
| 10 Sept 2026, 13:01 | 1,198 | -7 |
| 5 Sept 2026, 07:59 | 1,205 | -5 |
| 1 Sept 2026, 19:33 | 1,210 | -5 |
| 29 Aug 2026, 05:15 | 1,215 | 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.
@taranom_khiyal · 100,380
Telegram ranks this channel #16 of 65 here — alongside 64 others — read 29 August 2026
@iimoviee788 · 27,089
Telegram ranks this channel #32 of 59 here — alongside 58 others — read 5 September 2026
@masoomeh_mohammadiasl · 22,183
Telegram ranks this channel #34 of 47 here — alongside 46 others — read 19 September 2026
@dokhati_channel · 20,308
Telegram ranks this channel #36 of 67 here — alongside 66 others — read 26 September 2026
@tavalodtavalod99 · 29,243
Telegram ranks this channel #50 of 67 here — alongside 66 others — read 8 September 2026
@negarmrze · 18,300
Telegram ranks this channel #61 of 68 here — alongside 67 others — read 3 October 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“کـاژِهـ” (@kuzheh), 1,168 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/kuzheh.
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.