Channel
MUSALSALKA UBAXII MELO
@MUSALSAL_KA_LABADA_ISKU_WAALAN
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,108subscribers
+126 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001616450587 |
|---|---|
| Type | Channel |
| Username | @MUSALSAL_KA_LABADA_ISKU_WAALAN |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/MUSALSAL_KA_LABADA_ISKU_WAALAN |
Topic
Film & TV — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 |
|---|---|---|
| 1 Nov 2026, 06:09 | 3,108 | +2 |
| 29 Oct 2026, 00:00 | 3,106 | +2 |
| 26 Oct 2026, 00:18 | 3,104 | +12 |
| 23 Oct 2026, 03:35 | 3,092 | +9 |
| 19 Oct 2026, 21:46 | 3,083 | -10 |
| 17 Oct 2026, 06:40 | 3,093 | +5 |
| 14 Oct 2026, 00:34 | 3,088 | +8 |
| 8 Oct 2026, 19:57 | 3,080 | +32 |
| 2 Oct 2026, 05:55 | 3,048 | +23 |
| 16 Sept 2026, 22:02 | 3,025 | +1 |
| 12 Sept 2026, 17:16 | 3,024 | +12 |
| 11 Sept 2026, 13:56 | 3,012 | no change |
| 8 Sept 2026, 14:57 | 3,012 | +7 |
| 3 Sept 2026, 16:38 | 3,005 | +6 |
| 31 Aug 2026, 14:37 | 2,999 | +3 |
| 28 Aug 2026, 23:24 | 2,996 | +10 |
| 25 Aug 2026, 13:46 | 2,986 | +4 |
| 24 Aug 2026, 21:01 | 2,982 | 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.
@nuurdramahd · 35,872
Telegram ranks this channel #10 of 20 here — alongside 19 others — read 19 September 2026
@What_is_wrog_with_secretary_kim · 25,805
Telegram ranks this channel #10 of 24 here — alongside 23 others — read 18 September 2026
@Saaru6 · 34,990
Telegram ranks this channel #17 of 22 here — alongside 21 others — read 2 September 2026
@Musalsalka_Delikanli1 · 59,956
Telegram ranks this channel #26 of 29 here — alongside 28 others — read 24 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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“MUSALSALKA UBAXII MELO” (@MUSALSAL_KA_LABADA_ISKU_WAALAN), 3,108 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/MUSALSAL_KA_LABADA_ISKU_WAALAN.
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.