Channel
👹ᴘʜᴏɴᴋ ᴍᴜsɪᴄ👹
@PhonkMusicIR
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,128subscribers
+53 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001618956118 |
|---|---|
| Type | Channel |
| Username | @PhonkMusicIR |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/PhonkMusicIR |
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 100% 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 |
|---|---|---|
| 4 Nov 2026, 03:19 | 1,128 | +3 |
| 28 Oct 2026, 13:00 | 1,125 | +3 |
| 25 Oct 2026, 23:05 | 1,122 | +1 |
| 23 Oct 2026, 00:47 | 1,121 | +2 |
| 20 Oct 2026, 09:46 | 1,119 | +3 |
| 17 Oct 2026, 18:09 | 1,116 | -3 |
| 14 Oct 2026, 17:08 | 1,119 | +1 |
| 11 Oct 2026, 00:19 | 1,118 | +4 |
| 6 Oct 2026, 05:24 | 1,114 | no change |
| 4 Oct 2026, 23:56 | 1,114 | +10 |
| 25 Sept 2026, 17:39 | 1,104 | +8 |
| 16 Sept 2026, 22:40 | 1,096 | +3 |
| 12 Sept 2026, 19:22 | 1,093 | +5 |
| 9 Sept 2026, 02:17 | 1,088 | +1 |
| 3 Sept 2026, 09:52 | 1,087 | +5 |
| 30 Aug 2026, 17:55 | 1,082 | +1 |
| 28 Aug 2026, 01:15 | 1,081 | -2 |
| 25 Aug 2026, 07:42 | 1,083 | -2 |
| 22 Aug 2026, 07:37 | 1,085 | +8 |
| 18 Aug 2026, 18:36 | 1,077 | 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.
@Faravahr_phonk · 65,706
Telegram ranks this channel #9 of 73 here — alongside 72 others — read 21 August 2026
@Hell_Musi · 29,260
Telegram ranks this channel #17 of 72 here — alongside 71 others — read 9 September 2026
@satannmusic · 24
Telegram ranks this channel #21 of 81 here — alongside 80 others — read 18 August 2026
@lybotmusic · 35,252
Telegram ranks this channel #27 of 50 here — alongside 49 others — read 2 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“👹ᴘʜᴏɴᴋ ᴍᴜsɪᴄ👹” (@PhonkMusicIR), 1,128 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/PhonkMusicIR.
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.