Channel
πππ_ππππ
@VID_KORD_18
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
1,100subscribers
-47 since we began measuring on 22 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
Register entry
| Telegram ID | -1002032571255 |
|---|---|
| Type | Channel |
| Username | @VID_KORD_18 |
| Created | Between 1 November 2023 and 31 May 2024 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 2 times, most recently 5 November 2026 |
| On Telegram | t.me/VID_KORD_18 |
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 |
|---|---|---|
| 2 Nov 2026, 01:27 | 1,100 | -1 |
| 29 Oct 2026, 18:20 | 1,101 | -1 |
| 27 Oct 2026, 03:16 | 1,102 | -2 |
| 23 Oct 2026, 21:58 | 1,104 | -2 |
| 21 Oct 2026, 06:49 | 1,106 | -2 |
| 18 Oct 2026, 10:58 | 1,108 | -1 |
| 15 Oct 2026, 06:47 | 1,109 | -2 |
| 12 Oct 2026, 11:06 | 1,111 | -4 |
| 6 Oct 2026, 05:16 | 1,115 | no change |
| 5 Oct 2026, 14:41 | 1,115 | -8 |
| 28 Sept 2026, 03:22 | 1,123 | -11 |
| 18 Sept 2026, 08:57 | 1,134 | -1 |
| 14 Sept 2026, 06:18 | 1,135 | -1 |
| 5 Sept 2026, 08:57 | 1,136 | -4 |
| 1 Sept 2026, 19:44 | 1,140 | -2 |
| 29 Aug 2026, 17:57 | 1,142 | -1 |
| 26 Aug 2026, 16:38 | 1,143 | -5 |
| 23 Aug 2026, 23:45 | 1,148 | +1 |
| 22 Aug 2026, 16:30 | 1,147 | 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.
@kordDip Β· 44,680
Telegram ranks this channel #11 of 72 here β alongside 71 others β read 27 August 2026
@magaleh_kordi Β· 60,476
Telegram ranks this channel #36 of 79 here β alongside 78 others β read 23 August 2026
@Kermanshahklipp Β· 21,184
Telegram ranks this channel #44 of 74 here β alongside 73 others β read 26 September 2026
@qzalmix Β· 78,568
Telegram ranks this channel #45 of 51 here β alongside 50 others β read 22 August 2026
@shahan_tunes Β· 31,424
Telegram ranks this channel #50 of 71 here β alongside 70 others β read 21 September 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total, of which the 5 where it ranks highest are shown above. 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.
βπππ_ππππβ (@VID_KORD_18), 1,100 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/VID_KORD_18.
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.