Channel
Dj Bankruptcy
@DJ_BANKRUPTCY
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,603subscribers
+2,341 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 | -1001550248188 |
|---|---|
| Type | Channel |
| Username | @DJ_BANKRUPTCY |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/DJ_BANKRUPTCY |
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 94% 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 |
|---|---|---|
| 19 Sept 2026, 03:41 | 4,603 | +43 |
| 14 Sept 2026, 13:20 | 4,560 | +48 |
| 11 Sept 2026, 07:37 | 4,512 | +501 |
| 6 Sept 2026, 06:01 | 4,011 | +107 |
| 5 Sept 2026, 23:39 | 3,904 | no change |
| 1 Sept 2026, 18:44 | 3,904 | +218 |
| 29 Aug 2026, 23:03 | 3,686 | +171 |
| 26 Aug 2026, 16:03 | 3,515 | +113 |
| 23 Aug 2026, 20:34 | 3,402 | +270 |
| 20 Aug 2026, 05:35 | 3,132 | +99 |
| 17 Aug 2026, 10:46 | 3,033 | +94 |
| 14 Aug 2026, 03:28 | 2,939 | +665 |
| 10 Aug 2026, 15:03 | 2,274 | +11 |
| 7 Aug 2026, 23:31 | 2,263 | +1 |
| 7 Aug 2026, 12:22 | 2,262 | 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.
@HEYDEJAY · 58,236
Telegram ranks this channel #12 of 76 here — alongside 75 others — read 23 August 2026
@ra_jv · 43,126
Telegram ranks this channel #58 of 68 here — alongside 67 others — read 28 August 2026
@DJPhellix · 30,676
Telegram ranks this channel #61 of 63 here — alongside 62 others — read 7 September 2026
This channel appears in 3 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Dj Bankruptcy” (@DJ_BANKRUPTCY), 4,603 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/DJ_BANKRUPTCY.
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.