Channel
🦋🐬کانال هایده و مهستی🎵🎙
@hayedeh_musci
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,562subscribers
+134 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 | -1001653081632 |
|---|---|
| Type | Channel |
| Username | @hayedeh_musci |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/hayedeh_musci |
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 98% 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 |
|---|---|---|
| 17 Sept 2026, 15:36 | 5,562 | +2 |
| 13 Sept 2026, 23:38 | 5,560 | -2 |
| 10 Sept 2026, 15:37 | 5,562 | +14 |
| 5 Sept 2026, 15:59 | 5,548 | +5 |
| 1 Sept 2026, 20:57 | 5,543 | +13 |
| 30 Aug 2026, 22:13 | 5,530 | no change |
| 30 Aug 2026, 07:08 | 5,530 | +3 |
| 27 Aug 2026, 04:28 | 5,527 | +19 |
| 24 Aug 2026, 13:16 | 5,508 | +34 |
| 20 Aug 2026, 15:48 | 5,474 | +23 |
| 17 Aug 2026, 10:22 | 5,451 | +7 |
| 14 Aug 2026, 02:35 | 5,444 | +10 |
| 10 Aug 2026, 13:04 | 5,434 | +9 |
| 7 Aug 2026, 21:30 | 5,425 | -3 |
| 7 Aug 2026, 12:17 | 5,428 | 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.
@tanehayeghadimi · 18
Telegram ranks this channel #3 of 78 here — alongside 77 others — read 12 August 2026
@tk_fo · 60,990
Telegram ranks this channel #6 of 69 here — alongside 68 others — read 22 August 2026
@moeinesfahan · 73,888
Telegram ranks this channel #33 of 85 here — alongside 84 others — read 19 August 2026
@majaleh_bedanim · 136,058
Telegram ranks this channel #60 of 73 here — alongside 72 others — read 13 August 2026
@estekhdami_com · 23,311
Telegram ranks this channel #66 of 67 here — alongside 66 others — read 18 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“🦋🐬کانال هایده و مهستی🎵🎙” (@hayedeh_musci), 5,562 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hayedeh_musci.
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.