Channel
Sadegh Nojouki
@sadegh_nojouki
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,297subscribers
+105 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 | -1001092054490 |
|---|---|
| Type | Channel |
| Username | @sadegh_nojouki |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/sadegh_nojouki |
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 |
|---|---|---|
| 19 Sept 2026, 16:21 | 5,297 | +3 |
| 15 Sept 2026, 08:21 | 5,294 | +14 |
| 11 Sept 2026, 13:37 | 5,280 | +63 |
| 7 Sept 2026, 00:40 | 5,217 | +8 |
| 2 Sept 2026, 01:26 | 5,209 | -5 |
| 31 Aug 2026, 22:21 | 5,214 | no change |
| 30 Aug 2026, 06:39 | 5,214 | +2 |
| 26 Aug 2026, 23:11 | 5,212 | -2 |
| 24 Aug 2026, 05:29 | 5,214 | +11 |
| 20 Aug 2026, 19:05 | 5,203 | +4 |
| 17 Aug 2026, 14:29 | 5,199 | +1 |
| 14 Aug 2026, 08:29 | 5,198 | +4 |
| 11 Aug 2026, 07:54 | 5,194 | +2 |
| 7 Aug 2026, 12:17 | 5,192 | 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.
@mykhatereha · 30,165
Telegram ranks this channel #23 of 71 here — alongside 70 others — read 7 September 2026
@EbiofficialChannel · 40,235
Telegram ranks this channel #29 of 79 here — alongside 78 others — read 30 August 2026
@YadeAyyaam · 30,161
Telegram ranks this channel #32 of 81 here — alongside 80 others — read 7 September 2026
@navayegollha · 52,904
Telegram ranks this channel #37 of 84 here — alongside 83 others — read 24 August 2026
@avaaye_mandegar · 43,652
Telegram ranks this channel #47 of 77 here — alongside 76 others — read 28 August 2026
@Navahang · 88,658
Telegram ranks this channel #51 of 73 here — alongside 72 others — read 19 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Sadegh Nojouki” (@sadegh_nojouki), 5,297 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/sadegh_nojouki.
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.