Channel
sami.rock
@sajadshaikhi_official
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,146subscribers
-56 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001841925579 |
|---|---|
| Type | Channel |
| Username | @sajadshaikhi_official |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/sajadshaikhi_official |
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 99% 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 |
|---|---|---|
| 17 Sept 2026, 16:19 | 4,146 | -8 |
| 13 Sept 2026, 19:39 | 4,154 | -6 |
| 9 Sept 2026, 22:17 | 4,160 | -13 |
| 4 Sept 2026, 22:28 | 4,173 | no change |
| 4 Sept 2026, 06:41 | 4,173 | -13 |
| 28 Aug 2026, 23:17 | 4,186 | -7 |
| 25 Aug 2026, 16:33 | 4,193 | -6 |
| 22 Aug 2026, 13:35 | 4,199 | -3 |
| 21 Aug 2026, 22:45 | 4,202 | 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.
@Ramin_karami_music · 30,740
Telegram ranks this channel #4 of 88 here — alongside 87 others — read 7 September 2026
@Roholahkaramii · 26,415
Telegram ranks this channel #7 of 59 here — alongside 58 others — read 12 September 2026
@Roholakarami · 36,975
Telegram ranks this channel #23 of 62 here — alongside 61 others — read 1 September 2026
@farshadmoradiofficial · 61,739
Telegram ranks this channel #53 of 71 here — alongside 70 others — read 18 September 2026
@rasol_javid_orginal · 62,132
Telegram ranks this channel #66 of 82 here — alongside 81 others — read 21 August 2026
@klip_gham_laki · 46,673
Telegram ranks this channel #73 of 85 here — alongside 84 others — read 28 August 2026
@kordmozik66 · 42,812
Telegram ranks this channel #74 of 78 here — alongside 77 others — read 28 August 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“sami.rock” (@sajadshaikhi_official), 4,146 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/sajadshaikhi_official.
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.