Channel
Deep House Music
@deephousemuzic
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,807subscribers
+111 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001093727725 |
|---|---|
| Type | Channel |
| Username | @deephousemuzic |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 19 September 2026 |
| On Telegram | t.me/deephousemuzic |
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 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 00:58 | 4,807 | +3 |
| 11 Sept 2026, 02:57 | 4,804 | +9 |
| 5 Sept 2026, 18:19 | 4,795 | +25 |
| 2 Sept 2026, 12:41 | 4,770 | no change |
| 1 Sept 2026, 17:48 | 4,770 | +12 |
| 29 Aug 2026, 22:24 | 4,758 | +8 |
| 27 Aug 2026, 07:37 | 4,750 | +11 |
| 24 Aug 2026, 07:27 | 4,739 | +12 |
| 20 Aug 2026, 14:05 | 4,727 | +21 |
| 17 Aug 2026, 18:33 | 4,706 | +6 |
| 14 Aug 2026, 08:28 | 4,700 | +4 |
| 13 Aug 2026, 02:45 | 4,696 | 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.
@Radiio_ava · 27,775
Telegram ranks this channel #16 of 61 here — alongside 60 others — read 10 September 2026
@musiconmindf · 39,250
Telegram ranks this channel #19 of 75 here — alongside 74 others — read 31 August 2026
@DJPhellix · 30,676
Telegram ranks this channel #24 of 63 here — alongside 62 others — read 7 September 2026
@DJRasheTMusiC · 42,186
Telegram ranks this channel #29 of 47 here — alongside 46 others — read 28 August 2026
@dj_pashaa · 48,530
Telegram ranks this channel #29 of 60 here — alongside 59 others — read 27 August 2026
@laminor_text_music · 153,361
Telegram ranks this channel #46 of 66 here — alongside 65 others — read 13 August 2026
@best_deeep · 153,044
Telegram ranks this channel #48 of 65 here — alongside 64 others — read 17 September 2026
This channel appears in 7 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Deep House Music” (@deephousemuzic), 4,807 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/deephousemuzic.
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.