Channel
Archive Sajad Shahi | آرشیو سجاد شاهی |
@sajadshahiarchive
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,066subscribers
+6 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001732757632 |
|---|---|
| Type | Channel |
| Username | @sajadshahiarchive |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/sajadshahiarchive |
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 20 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 21:07 | 2,066 | -3 |
| 5 Nov 2026, 04:08 | 2,069 | -2 |
| 2 Nov 2026, 07:51 | 2,071 | -1 |
| 30 Oct 2026, 06:30 | 2,072 | +6 |
| 27 Oct 2026, 01:29 | 2,066 | +6 |
| 24 Oct 2026, 02:09 | 2,060 | -2 |
| 20 Oct 2026, 21:10 | 2,062 | +7 |
| 18 Oct 2026, 06:25 | 2,055 | +1 |
| 14 Oct 2026, 22:10 | 2,054 | -3 |
| 11 Oct 2026, 21:17 | 2,057 | -13 |
| 5 Oct 2026, 09:37 | 2,070 | +7 |
| 27 Sept 2026, 09:54 | 2,063 | +9 |
| 20 Sept 2026, 02:42 | 2,054 | no change |
| 16 Sept 2026, 01:18 | 2,054 | -3 |
| 12 Sept 2026, 03:17 | 2,057 | +3 |
| 7 Sept 2026, 17:00 | 2,054 | -1 |
| 3 Sept 2026, 00:55 | 2,055 | +18 |
| 30 Aug 2026, 16:38 | 2,037 | +2 |
| 27 Aug 2026, 08:25 | 2,035 | -1 |
| 24 Aug 2026, 14:27 | 2,036 | 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.
@vinak · 344,675
Telegram ranks this channel #25 of 54 here — alongside 53 others — read 31 August 2026
@BigShaggyReal · 37,538
Telegram ranks this channel #46 of 59 here — alongside 58 others — read 8 September 2026
@FullArchive_AminTijay · 21,672
Telegram ranks this channel #55 of 69 here — alongside 68 others — read 29 September 2026
@tiemcrypto · 333,764
Telegram ranks this channel #64 of 64 here — alongside 63 others — read 13 August 2026
This channel appears in 4 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Archive Sajad Shahi | آرشیو سجاد شاهی |” (@sajadshahiarchive), 2,066 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/sajadshahiarchive.
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.