Channel
ππππ©π§ππ¬π¬
@Deepness_Deep_House
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
4,831subscribers
+37 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 | -1001300966923 |
|---|---|
| Type | Channel |
| Username | @Deepness_Deep_House |
| Created | 21 September 2020 β measured β cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 1 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Deepness_Deep_House |
Topic
Other / unclassifiable β 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 100% 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 |
|---|---|---|
| 17 Sept 2026, 03:40 | 4,831 | +19 |
| 12 Sept 2026, 23:58 | 4,812 | +1 |
| 9 Sept 2026, 00:41 | 4,811 | -12 |
| 3 Sept 2026, 09:04 | 4,823 | +5 |
| 1 Sept 2026, 23:40 | 4,818 | no change |
| 30 Aug 2026, 19:27 | 4,818 | -2 |
| 28 Aug 2026, 03:28 | 4,820 | -7 |
| 24 Aug 2026, 19:36 | 4,827 | +12 |
| 21 Aug 2026, 05:18 | 4,815 | +4 |
| 17 Aug 2026, 21:14 | 4,811 | +6 |
| 14 Aug 2026, 17:27 | 4,805 | +10 |
| 11 Aug 2026, 03:26 | 4,795 | +3 |
| 7 Aug 2026, 19:40 | 4,792 | -2 |
| 6 Aug 2026, 20:43 | 4,794 | 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.
@best_deeep Β· 153,044
Telegram ranks this channel #7 of 65 here β alongside 64 others β read 17 September 2026
@Disco_Deep Β· 26,593
Telegram ranks this channel #26 of 72 here β alongside 71 others β read 12 September 2026
@muzukarussia Β· 23,909
Telegram ranks this channel #27 of 54 here β alongside 53 others β read 17 September 2026
@Golden_deep Β· 23,076
Telegram ranks this channel #44 of 74 here β alongside 73 others β read 19 September 2026
@MUSICplusze Β· 23,330
Telegram ranks this channel #47 of 75 here β alongside 74 others β read 18 September 2026
@SunMusicDaily Β· 28,676
Telegram ranks this channel #79 of 81 here β alongside 80 others β read 9 September 2026
This channel appears in 6 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 17 September 2026 β this entry's latest reading, not the date you are reading this.
βππππ©π§ππ¬π¬β (@Deepness_Deep_House), 4,831 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Deepness_Deep_House.
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.