Channel
Musasal dhawicii qalbiga
@musasalchanell
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,552subscribers
+520 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001519778678 |
|---|---|
| Type | Channel |
| Username | @musasalchanell |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/musasalchanell |
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 82% 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, 06:40 | 4,552 | +19 |
| 4 Nov 2026, 06:17 | 4,533 | +12 |
| 1 Nov 2026, 15:49 | 4,521 | +15 |
| 29 Oct 2026, 10:56 | 4,506 | +18 |
| 26 Oct 2026, 18:46 | 4,488 | +10 |
| 23 Oct 2026, 22:06 | 4,478 | +13 |
| 21 Oct 2026, 01:47 | 4,465 | +2 |
| 17 Oct 2026, 19:00 | 4,463 | +22 |
| 14 Oct 2026, 11:05 | 4,441 | +10 |
| 11 Oct 2026, 03:21 | 4,431 | +36 |
| 4 Oct 2026, 21:59 | 4,395 | +42 |
| 25 Sept 2026, 06:17 | 4,353 | +57 |
| 16 Sept 2026, 12:41 | 4,296 | +68 |
| 13 Sept 2026, 02:41 | 4,228 | +34 |
| 9 Sept 2026, 09:16 | 4,194 | +43 |
| 4 Sept 2026, 22:47 | 4,151 | no change |
| 3 Sept 2026, 18:58 | 4,151 | +43 |
| 31 Aug 2026, 11:16 | 4,108 | +14 |
| 28 Aug 2026, 19:28 | 4,094 | +23 |
| 25 Aug 2026, 21:35 | 4,071 | 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.
@AARGUDASHO11 · 37,305
Telegram ranks this channel #2 of 20 here — alongside 19 others — read 1 October 2026
@INDHAHA_BADDA_MADOW · 39,890
Telegram ranks this channel #16 of 27 here — alongside 26 others — read 29 August 2026
@queenzuhur · 49,335
Telegram ranks this channel #29 of 31 here — alongside 30 others — read 25 August 2026
@musalsalka_leeyla · 60,731
Telegram ranks this channel #30 of 31 here — alongside 30 others — read 22 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.
“Musasal dhawicii qalbiga” (@musasalchanell), 4,552 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/musasalchanell.
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.