Channel
موزیک رقص
@danceico
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,538subscribers
-61 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001452216819 |
|---|---|
| Type | Channel |
| Username | @danceico |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/danceico |
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 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 |
|---|---|---|
| 6 Nov 2026, 18:38 | 4,538 | -4 |
| 3 Nov 2026, 15:16 | 4,542 | +2 |
| 31 Oct 2026, 15:17 | 4,540 | -5 |
| 29 Oct 2026, 01:47 | 4,545 | -5 |
| 26 Oct 2026, 10:49 | 4,550 | -3 |
| 23 Oct 2026, 13:48 | 4,553 | +2 |
| 20 Oct 2026, 10:36 | 4,551 | +2 |
| 17 Oct 2026, 14:28 | 4,549 | -10 |
| 14 Oct 2026, 15:01 | 4,559 | -6 |
| 11 Oct 2026, 09:39 | 4,565 | -10 |
| 4 Oct 2026, 22:56 | 4,575 | -5 |
| 25 Sept 2026, 21:36 | 4,580 | -29 |
| 15 Sept 2026, 03:36 | 4,609 | +6 |
| 11 Sept 2026, 18:18 | 4,603 | -6 |
| 6 Sept 2026, 22:36 | 4,609 | +4 |
| 2 Sept 2026, 22:50 | 4,605 | no change |
| 2 Sept 2026, 11:56 | 4,605 | -2 |
| 30 Aug 2026, 02:34 | 4,607 | +7 |
| 27 Aug 2026, 12:18 | 4,600 | +1 |
| 27 Aug 2026, 06:45 | 4,599 | 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.
@soheilahmadifarsingers1 · 51,726
Telegram ranks this channel #51 of 66 here — alongside 65 others — read 27 August 2026
@ashpaziiy · 20,688
Telegram ranks this channel #65 of 65 here — alongside 64 others — read 26 September 2026
@Draghsahang · 36,645
Telegram ranks this channel #84 of 84 here — alongside 83 others — read 31 August 2026
@bio_angizeshi1 · 21,229
Telegram ranks this channel #87 of 87 here — alongside 86 others — read 26 September 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“موزیک رقص” (@danceico), 4,538 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/danceico.
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.