Channel
Ставрополь | Жесть | ЧП
@muzika_dlya_dushi99
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,045subscribers
-77 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001283047687 |
|---|---|
| Type | Channel |
| Username | @muzika_dlya_dushi99 |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/muzika_dlya_dushi99 |
Topic
Local community — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 |
|---|---|---|
| 16 Sept 2026, 05:38 | 4,045 | -10 |
| 12 Sept 2026, 16:57 | 4,055 | -12 |
| 8 Sept 2026, 14:19 | 4,067 | -11 |
| 5 Sept 2026, 00:00 | 4,078 | no change |
| 3 Sept 2026, 08:47 | 4,078 | -3 |
| 31 Aug 2026, 04:27 | 4,081 | -6 |
| 28 Aug 2026, 12:17 | 4,087 | -5 |
| 25 Aug 2026, 05:35 | 4,092 | -6 |
| 22 Aug 2026, 14:06 | 4,098 | -9 |
| 19 Aug 2026, 05:42 | 4,107 | -2 |
| 16 Aug 2026, 06:48 | 4,109 | -6 |
| 9 Aug 2026, 21:52 | 4,115 | -7 |
| 6 Aug 2026, 13:40 | 4,122 | 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.
@goodmp3 · 56,206
Telegram ranks this channel #2 of 65 here — alongside 64 others — read 23 August 2026
@muzykatg · 26,677
Telegram ranks this channel #14 of 50 here — alongside 49 others — read 12 September 2026
@amiux_new · 30,902
Telegram ranks this channel #30 of 59 here — alongside 58 others — read 7 September 2026
@melodiy · 36,033
Telegram ranks this channel #39 of 69 here — alongside 68 others — read 2 September 2026
@AphoTG · 36,321
Telegram ranks this channel #68 of 78 here — alongside 77 others — read 1 September 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Ставрополь | Жесть | ЧП” (@muzika_dlya_dushi99), 4,045 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/muzika_dlya_dushi99.
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.