Channel
𝘿𝙅 𝙑𝘼𝙇𝘾𝙊
@deej_valco
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,672subscribers
-97 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 | -1001791866884 |
|---|---|
| Type | Channel |
| Username | @deej_valco |
| Created | Between 1 January 2022 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/deej_valco |
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 14 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, 00:58 | 3,672 | -6 |
| 13 Sept 2026, 03:41 | 3,678 | -11 |
| 8 Sept 2026, 20:18 | 3,689 | -9 |
| 6 Sept 2026, 23:56 | 3,698 | no change |
| 3 Sept 2026, 13:22 | 3,698 | -11 |
| 31 Aug 2026, 05:47 | 3,709 | -11 |
| 28 Aug 2026, 03:08 | 3,720 | -10 |
| 25 Aug 2026, 00:36 | 3,730 | -8 |
| 21 Aug 2026, 03:15 | 3,738 | -9 |
| 18 Aug 2026, 05:52 | 3,747 | -4 |
| 14 Aug 2026, 20:28 | 3,751 | -10 |
| 11 Aug 2026, 16:52 | 3,761 | -5 |
| 8 Aug 2026, 11:03 | 3,766 | -3 |
| 7 Aug 2026, 13:11 | 3,769 | 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.
@dj_reebok · 35,022
Telegram ranks this channel #19 of 54 here — alongside 53 others — read 5 September 2026
@DJ_SADEGH99 · 34,106
Telegram ranks this channel #24 of 79 here — alongside 78 others — read 3 September 2026
@nasabet_org1 · 23,165
Telegram ranks this channel #28 of 49 here — alongside 48 others — read 19 September 2026
@DEEJ_DARK · 125,408
Telegram ranks this channel #35 of 81 here — alongside 80 others — read 13 August 2026
@deej_danial · 84,042
Telegram ranks this channel #39 of 81 here — alongside 80 others — read 18 August 2026
@DJALIPADASHI · 220,288
Telegram ranks this channel #53 of 87 here — alongside 86 others — read 11 August 2026
This channel appears in 6 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.
“𝘿𝙅 𝙑𝘼𝙇𝘾𝙊” (@deej_valco), 3,672 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/deej_valco.
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.