Channel
Drown In Music
@Drown_in_Music
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,574subscribers
+2,244 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 | -1001726051634 |
|---|---|
| Type | Channel |
| Username | @Drown_in_Music |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/Drown_in_Music |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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, 23:36 | 6,574 | +34 |
| 30 Oct 2026, 23:46 | 6,540 | +392 |
| 28 Oct 2026, 07:27 | 6,148 | -35 |
| 25 Oct 2026, 09:18 | 6,183 | -2 |
| 22 Oct 2026, 10:37 | 6,185 | +112 |
| 19 Oct 2026, 02:55 | 6,073 | +474 |
| 16 Oct 2026, 11:40 | 5,599 | -22 |
| 13 Oct 2026, 02:34 | 5,621 | -2 |
| 6 Oct 2026, 14:15 | 5,623 | +669 |
| 29 Sept 2026, 08:38 | 4,954 | -39 |
| 18 Sept 2026, 21:01 | 4,993 | -23 |
| 14 Sept 2026, 14:36 | 5,016 | -8 |
| 10 Sept 2026, 20:37 | 5,024 | -22 |
| 5 Sept 2026, 13:16 | 5,046 | -31 |
| 2 Sept 2026, 00:54 | 5,077 | -5 |
| 1 Sept 2026, 12:18 | 5,082 | no change |
| 30 Aug 2026, 03:46 | 5,082 | -22 |
| 27 Aug 2026, 11:07 | 5,104 | -23 |
| 24 Aug 2026, 12:15 | 5,127 | -42 |
| 20 Aug 2026, 14:07 | 5,169 | 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.
@zakharbarbie · 44,496
Telegram ranks this channel #27 of 82 here — alongside 81 others — read 26 August 2026
@samkade_rapi · 26,892
Telegram ranks this channel #29 of 75 here — alongside 74 others — read 8 September 2026
@Dopingmazei · 75,467
Telegram ranks this channel #40 of 80 here — alongside 79 others — read 12 September 2026
@hiphoptwitter · 44,754
Telegram ranks this channel #52 of 79 here — alongside 78 others — read 28 August 2026
@CommentsGap · 61,158
Telegram ranks this channel #56 of 71 here — alongside 70 others — read 30 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Drown In Music” (@Drown_in_Music), 6,574 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/Drown_in_Music.
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.