
Channel
Pmc Music️ ️️
@PmcHD_ir
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,821subscribers
-19 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001089488791 |
|---|---|
| Type | Channel |
| Username | @PmcHD_ir |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/PmcHD_ir |
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 87% 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:25 | 4,821 | -2 |
| 30 Oct 2026, 22:58 | 4,823 | -3 |
| 28 Oct 2026, 02:09 | 4,826 | -1 |
| 25 Oct 2026, 00:17 | 4,827 | -1 |
| 21 Oct 2026, 21:49 | 4,828 | -3 |
| 18 Oct 2026, 07:06 | 4,831 | +2 |
| 15 Oct 2026, 03:40 | 4,829 | -1 |
| 11 Oct 2026, 15:38 | 4,830 | -9 |
| 5 Oct 2026, 10:01 | 4,839 | -5 |
| 27 Sept 2026, 00:56 | 4,844 | -3 |
| 17 Sept 2026, 10:15 | 4,847 | +1 |
| 13 Sept 2026, 20:17 | 4,846 | +1 |
| 9 Sept 2026, 17:16 | 4,845 | -5 |
| 4 Sept 2026, 14:41 | 4,850 | +4 |
| 1 Sept 2026, 23:18 | 4,846 | no change |
| 1 Sept 2026, 06:02 | 4,846 | +4 |
| 29 Aug 2026, 06:54 | 4,842 | +4 |
| 26 Aug 2026, 05:33 | 4,838 | +1 |
| 22 Aug 2026, 22:04 | 4,837 | +7 |
| 19 Aug 2026, 03:05 | 4,830 | 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.
@musicall_pmc · 20,951
Telegram ranks this channel #3 of 48 here — alongside 47 others — read 22 September 2026
@mzixs · 35,273
Telegram ranks this channel #23 of 63 here — alongside 62 others — read 1 September 2026
@Draghsahang · 36,699
Telegram ranks this channel #28 of 84 here — alongside 83 others — read 31 August 2026
@jomlea · 29,580
Telegram ranks this channel #59 of 89 here — alongside 88 others — read 8 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Pmc Music️ ️️” (@PmcHD_ir), 4,821 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/PmcHD_ir.
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.