Channel
DeepHouseCityRecords
@DeepHouseCityRecords
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,206subscribers
+1,113 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 | -1001228105292 |
|---|---|
| Type | Channel |
| Username | @DeepHouseCityRecords |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/DeepHouseCityRecords |
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 88% 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 |
|---|---|---|
| 14 Sept 2026, 00:17 | 4,206 | +128 |
| 10 Sept 2026, 07:19 | 4,078 | +210 |
| 6 Sept 2026, 00:23 | 3,868 | no change |
| 5 Sept 2026, 11:39 | 3,868 | +208 |
| 1 Sept 2026, 05:54 | 3,660 | +160 |
| 29 Aug 2026, 11:08 | 3,500 | +145 |
| 26 Aug 2026, 05:34 | 3,355 | +28 |
| 23 Aug 2026, 03:17 | 3,327 | +57 |
| 19 Aug 2026, 16:32 | 3,270 | +38 |
| 16 Aug 2026, 20:46 | 3,232 | +29 |
| 13 Aug 2026, 01:55 | 3,203 | +73 |
| 10 Aug 2026, 11:42 | 3,130 | +17 |
| 7 Aug 2026, 17:41 | 3,113 | +20 |
| 6 Aug 2026, 18:44 | 3,093 | 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.
@musiconmindf · 39,259
Telegram ranks this channel #37 of 75 here — alongside 74 others — read 31 August 2026
@Disco_Deep · 26,565
Telegram ranks this channel #52 of 72 here — alongside 71 others — read 12 September 2026
@SunMusicDaily · 28,644
Telegram ranks this channel #56 of 81 here — alongside 80 others — read 9 September 2026
@Ritmg · 66,592
Telegram ranks this channel #67 of 69 here — alongside 68 others — read 20 August 2026
@AutumnAU · 28,661
Telegram ranks this channel #81 of 90 here — alongside 89 others — read 9 September 2026
@piano_paradise_official · 55,579
Telegram ranks this channel #81 of 90 here — alongside 89 others — read 23 August 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“DeepHouseCityRecords” (@DeepHouseCityRecords), 4,206 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/DeepHouseCityRecords.
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.