Channel
إذاعة مرسال mirsal.live
@mirsallive
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,062subscribers
+142 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001332586250 |
|---|---|
| Type | Channel |
| Username | @mirsallive |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 20 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 20 October 2026 |
| On Telegram | t.me/mirsallive |
Topic
Music — 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 87% 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 |
|---|---|---|
| 20 Oct 2026, 08:19 | 5,062 | +22 |
| 16 Oct 2026, 22:46 | 5,040 | +16 |
| 13 Oct 2026, 18:39 | 5,024 | +10 |
| 7 Oct 2026, 17:19 | 5,014 | +23 |
| 1 Oct 2026, 02:02 | 4,991 | +26 |
| 16 Sept 2026, 05:22 | 4,965 | +2 |
| 12 Sept 2026, 07:58 | 4,963 | -4 |
| 8 Sept 2026, 05:37 | 4,967 | -7 |
| 1 Sept 2026, 21:46 | 4,974 | no change |
| 30 Aug 2026, 08:35 | 4,974 | +8 |
| 27 Aug 2026, 04:12 | 4,966 | +11 |
| 24 Aug 2026, 09:13 | 4,955 | +10 |
| 20 Aug 2026, 09:35 | 4,945 | +8 |
| 17 Aug 2026, 18:08 | 4,937 | +9 |
| 14 Aug 2026, 17:54 | 4,928 | +4 |
| 11 Aug 2026, 04:17 | 4,924 | +3 |
| 8 Aug 2026, 06:03 | 4,921 | +1 |
| 7 Aug 2026, 22:08 | 4,920 | 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.
@libya_salafy · 33,352
Telegram ranks this channel #36 of 69 here — alongside 68 others — read 4 September 2026
@Arafatbinhassan · 29,545
Telegram ranks this channel #44 of 92 here — alongside 91 others — read 8 September 2026
@Miraathalanbeyaa · 23,789
Telegram ranks this channel #51 of 90 here — alongside 89 others — read 17 September 2026
@Elbashasci · 24,698
Telegram ranks this channel #54 of 82 here — alongside 81 others — read 15 September 2026
@kibaar_al_ulama · 22,405
Telegram ranks this channel #56 of 98 here — alongside 97 others — read 20 September 2026
This channel appears in 5 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 20 October 2026 — this entry's latest reading, not the date you are reading this.
“إذاعة مرسال mirsal.live” (@mirsallive), 5,062 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/mirsallive.
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.