Channel
أرشيف
@alkasralainyarchive
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,350subscribers
-18 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001927854800 |
|---|---|
| Type | Channel |
| Username | @alkasralainyarchive |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/alkasralainyarchive |
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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 10:39 | 4,350 | -1 |
| 2 Nov 2026, 03:16 | 4,351 | -2 |
| 30 Oct 2026, 11:18 | 4,353 | +1 |
| 27 Oct 2026, 11:17 | 4,352 | -2 |
| 24 Oct 2026, 20:46 | 4,354 | -1 |
| 21 Oct 2026, 12:21 | 4,355 | +4 |
| 15 Oct 2026, 08:07 | 4,351 | -3 |
| 12 Oct 2026, 15:31 | 4,354 | +2 |
| 5 Oct 2026, 15:02 | 4,352 | +4 |
| 27 Sept 2026, 13:36 | 4,348 | -1 |
| 17 Sept 2026, 19:37 | 4,349 | -10 |
| 13 Sept 2026, 08:57 | 4,359 | -2 |
| 9 Sept 2026, 17:19 | 4,361 | -1 |
| 4 Sept 2026, 18:18 | 4,362 | -1 |
| 3 Sept 2026, 23:01 | 4,363 | no change |
| 1 Sept 2026, 03:07 | 4,363 | -4 |
| 28 Aug 2026, 17:18 | 4,367 | -1 |
| 28 Aug 2026, 06:45 | 4,368 | 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.
@FUTUREDOCTORS_Siraj · 30,766
Telegram ranks this channel #17 of 83 here — alongside 82 others — read 7 September 2026
@FUTUREDOCTORS_196 · 36,230
Telegram ranks this channel #22 of 77 here — alongside 76 others — read 2 September 2026
@FUTUREDOCTORS_194 · 43,969
Telegram ranks this channel #33 of 89 here — alongside 88 others — read 29 August 2026
@amgad_samir_sounds · 52,881
Telegram ranks this channel #63 of 88 here — alongside 87 others — read 28 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“أرشيف” (@alkasralainyarchive), 4,350 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/alkasralainyarchive.
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.