Channel
Краснодар Новости
@dlsmsjx
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,989subscribers
-207 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001774721064 |
|---|---|
| Type | Channel |
| Username | @dlsmsjx |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/dlsmsjx |
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 75% 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:17 | 2,989 | -60 |
| 2 Nov 2026, 00:11 | 3,049 | -94 |
| 29 Oct 2026, 14:09 | 3,143 | -106 |
| 26 Oct 2026, 11:30 | 3,249 | -20 |
| 23 Oct 2026, 21:40 | 3,269 | -12 |
| 21 Oct 2026, 05:31 | 3,281 | -14 |
| 18 Oct 2026, 01:17 | 3,295 | -11 |
| 15 Oct 2026, 09:41 | 3,306 | -22 |
| 12 Oct 2026, 11:07 | 3,328 | -35 |
| 5 Oct 2026, 16:16 | 3,363 | -54 |
| 28 Sept 2026, 00:02 | 3,417 | -89 |
| 18 Sept 2026, 19:57 | 3,506 | +365 |
| 14 Sept 2026, 05:57 | 3,141 | -50 |
| 10 Sept 2026, 20:26 | 3,191 | no change |
| 10 Sept 2026, 17:21 | 3,191 | +142 |
| 5 Sept 2026, 21:39 | 3,049 | -134 |
| 1 Sept 2026, 14:05 | 3,183 | +1 |
| 29 Aug 2026, 20:55 | 3,182 | -9 |
| 27 Aug 2026, 02:59 | 3,191 | -6 |
| 23 Aug 2026, 16:18 | 3,197 | 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.
@animeuwy · 70,652
Telegram ranks this channel #5 of 55 here — alongside 54 others — read 19 August 2026
@chvizi · 113,207
Telegram ranks this channel #6 of 39 here — alongside 38 others — read 19 September 2026
@animeeSong · 22,907
Telegram ranks this channel #8 of 34 here — alongside 33 others — read 19 September 2026
@wwww_ii · 20,191
Telegram ranks this channel #14 of 43 here — alongside 42 others — read 28 September 2026
@grustnaya_muzyka · 69,613
Telegram ranks this channel #32 of 57 here — alongside 56 others — read 20 August 2026
This channel appears in 5 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.
“Краснодар Новости” (@dlsmsjx), 2,989 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/dlsmsjx.
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.