Channel
موسیقی تحمیلی
@Mousighi_TAHMILI
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,116subscribers
+15 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001520396553 |
|---|---|
| Type | Channel |
| Username | @Mousighi_TAHMILI |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/Mousighi_TAHMILI |
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 6 October 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 |
|---|---|---|
| 2 Nov 2026, 15:45 | 1,116 | +1 |
| 30 Oct 2026, 15:00 | 1,115 | -1 |
| 27 Oct 2026, 16:07 | 1,116 | +2 |
| 22 Oct 2026, 07:57 | 1,114 | -2 |
| 18 Oct 2026, 15:28 | 1,116 | +3 |
| 15 Oct 2026, 08:36 | 1,113 | -1 |
| 11 Oct 2026, 23:01 | 1,114 | -1 |
| 6 Oct 2026, 05:21 | 1,115 | no change |
| 5 Oct 2026, 10:20 | 1,115 | -3 |
| 27 Sept 2026, 01:36 | 1,118 | +6 |
| 18 Sept 2026, 00:00 | 1,112 | +4 |
| 13 Sept 2026, 14:38 | 1,108 | +8 |
| 4 Sept 2026, 02:18 | 1,100 | +1 |
| 31 Aug 2026, 07:28 | 1,099 | -1 |
| 28 Aug 2026, 18:08 | 1,100 | -1 |
| 28 Aug 2026, 07:30 | 1,101 | 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.
@textmusic5 · 20,617
Telegram ranks this channel #3 of 82 here — alongside 81 others — read 26 September 2026
@AutumnAU · 28,205
Telegram ranks this channel #4 of 90 here — alongside 89 others — read 9 September 2026
@mehdidarabichannel · 24,126
Telegram ranks this channel #9 of 41 here — alongside 40 others — read 16 September 2026
@NOSTALGYSONGS · 44,912
Telegram ranks this channel #26 of 84 here — alongside 83 others — read 28 August 2026
@Nostalzhikmusic · 21,834
Telegram ranks this channel #30 of 63 here — alongside 62 others — read 22 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“موسیقی تحمیلی” (@Mousighi_TAHMILI), 1,116 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/Mousighi_TAHMILI.
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.