Channel
| کانال رسمی سجاد محمدی | Sajjad Mohammadi
@saajjad_mohammadi
On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry
15,306subscribers
-159 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001080620194 |
|---|---|
| Type | Channel |
| Username | @saajjad_mohammadi |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/saajjad_mohammadi |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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 |
|---|---|---|
| 18 Sept 2026, 05:00 | 15,306 | -3 |
| 15 Sept 2026, 23:38 | 15,309 | -31 |
| 14 Sept 2026, 06:38 | 15,340 | -13 |
| 12 Sept 2026, 17:39 | 15,353 | -10 |
| 10 Sept 2026, 17:57 | 15,363 | -10 |
| 7 Sept 2026, 18:42 | 15,373 | -23 |
| 4 Sept 2026, 20:57 | 15,396 | -36 |
| 3 Sept 2026, 08:56 | 15,432 | -17 |
| 1 Sept 2026, 23:15 | 15,449 | -12 |
| 31 Aug 2026, 23:57 | 15,461 | -11 |
| 30 Aug 2026, 20:14 | 15,472 | -9 |
| 29 Aug 2026, 21:02 | 15,481 | -4 |
| 29 Aug 2026, 00:27 | 15,485 | +4 |
| 27 Aug 2026, 00:44 | 15,481 | +9 |
| 24 Aug 2026, 23:53 | 15,472 | +5 |
| 23 Aug 2026, 14:16 | 15,467 | -5 |
| 22 Aug 2026, 01:08 | 15,472 | +26 |
| 20 Aug 2026, 22:06 | 15,446 | +17 |
| 19 Aug 2026, 23:18 | 15,429 | -8 |
| 18 Aug 2026, 21:54 | 15,437 | first reading |
Engagement
No public post preview. We read this entry on 18 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.
@buyesib_com · 30,700
Telegram ranks this channel #34 of 93 here — alongside 92 others — read 6 September 2026
@hoseintaheri_telegram · 103,553
Telegram ranks this channel #35 of 98 here — alongside 97 others — read 17 August 2026
@Maheharaminfo · 41,691
Telegram ranks this channel #39 of 97 here — alongside 96 others — read 29 August 2026
@mhpooyanfar · 47,673
Telegram ranks this channel #41 of 96 here — alongside 95 others — read 26 August 2026
@abaratinfo · 63,250
Telegram ranks this channel #43 of 98 here — alongside 97 others — read 20 August 2026
@nooriehinfo · 42,956
Telegram ranks this channel #47 of 95 here — alongside 94 others — read 28 August 2026
@hassanataie1 · 49,729
Telegram ranks this channel #48 of 95 here — alongside 94 others — read 25 August 2026
@fadakinfo_channel · 30,960
Telegram ranks this channel #56 of 93 here — alongside 92 others — read 6 September 2026
@reyhanatolhossein_channel · 31,117
Telegram ranks this channel #56 of 95 here — alongside 94 others — read 6 September 2026
@fotros_ir · 68,416
Telegram ranks this channel #60 of 96 here — alongside 95 others — read 20 August 2026
This channel appears in 10 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“| کانال رسمی سجاد محمدی | Sajjad Mohammadi” (@saajjad_mohammadi), 15,306 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/saajjad_mohammadi.
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.