Channel
YASAKOV PROD.
@yasakovdj
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,677subscribers
+137 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001704515965 |
|---|---|
| Type | Channel |
| Username | @yasakovdj |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/yasakovdj |
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 27 September 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 |
|---|---|---|
| 5 Nov 2026, 01:45 | 1,677 | -3 |
| 1 Nov 2026, 14:59 | 1,680 | -1 |
| 29 Oct 2026, 07:37 | 1,681 | +1 |
| 26 Oct 2026, 12:27 | 1,680 | +6 |
| 23 Oct 2026, 09:39 | 1,674 | +5 |
| 20 Oct 2026, 02:08 | 1,669 | +4 |
| 17 Oct 2026, 00:17 | 1,665 | +5 |
| 10 Oct 2026, 16:19 | 1,660 | +47 |
| 4 Oct 2026, 23:57 | 1,613 | +49 |
| 27 Sept 2026, 01:46 | 1,564 | no change |
| 25 Sept 2026, 18:01 | 1,564 | +28 |
| 17 Sept 2026, 03:36 | 1,536 | -1 |
| 13 Sept 2026, 13:38 | 1,537 | +1 |
| 9 Sept 2026, 11:41 | 1,536 | +1 |
| 3 Sept 2026, 21:37 | 1,535 | -3 |
| 31 Aug 2026, 06:34 | 1,538 | -2 |
| 27 Aug 2026, 12:15 | 1,540 | 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.
@alexshikdj · 54,750
Telegram ranks this channel #60 of 89 here — alongside 88 others — read 27 August 2026
@djmikisofficial · 21,398
Telegram ranks this channel #63 of 90 here — alongside 89 others — read 25 September 2026
@djtabremixofficial · 45,584
Telegram ranks this channel #78 of 81 here — alongside 80 others — read 27 August 2026
This channel appears in 3 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“YASAKOV PROD.” (@yasakovdj), 1,677 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/yasakovdj.
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.