Channel
mohsen aghakhani
@imohsenaghakhani
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,940subscribers
+356 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001788761517 |
|---|---|
| Type | Channel |
| Username | @imohsenaghakhani |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/imohsenaghakhani |
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 15 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:55 | 2,940 | +7 |
| 15 Sept 2026, 15:39 | 2,933 | -1 |
| 12 Sept 2026, 02:18 | 2,934 | +22 |
| 12 Sept 2026, 01:00 | 2,912 | no change |
| 7 Sept 2026, 10:41 | 2,912 | +41 |
| 2 Sept 2026, 07:52 | 2,871 | +42 |
| 29 Aug 2026, 22:55 | 2,829 | +26 |
| 26 Aug 2026, 14:33 | 2,803 | +87 |
| 23 Aug 2026, 20:54 | 2,716 | +112 |
| 20 Aug 2026, 12:23 | 2,604 | +17 |
| 17 Aug 2026, 19:17 | 2,587 | +3 |
| 17 Aug 2026, 12:15 | 2,584 | 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.
@official_2yar · 23,100
Telegram ranks this channel #9 of 64 here — alongside 63 others — read 19 September 2026
@saeedkarimi_officialchannel · 49,336
Telegram ranks this channel #18 of 68 here — alongside 67 others — read 26 August 2026
@EvanBand · 45,171
Telegram ranks this channel #22 of 75 here — alongside 74 others — read 31 August 2026
@mojtababadri451 · 74,619
Telegram ranks this channel #27 of 56 here — alongside 55 others — read 22 August 2026
@ahangetorkye · 91,921
Telegram ranks this channel #42 of 85 here — alongside 84 others — read 17 August 2026
@djahmadrezaa · 43,290
Telegram ranks this channel #45 of 79 here — alongside 78 others — read 28 August 2026
@neday7676 · 67,535
Telegram ranks this channel #46 of 57 here — alongside 56 others — read 7 September 2026
This channel appears in 7 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.
“mohsen aghakhani” (@imohsenaghakhani), 2,940 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/imohsenaghakhani.
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.