Channel
DJ4X.in
@dj4xin
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,090subscribers
+88 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 | -1001291696338 |
|---|---|
| Type | Channel |
| Username | @dj4xin |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/dj4xin |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 |
|---|---|---|
| 16 Sept 2026, 20:18 | 6,090 | +19 |
| 12 Sept 2026, 12:15 | 6,071 | +14 |
| 8 Sept 2026, 13:55 | 6,057 | +40 |
| 3 Sept 2026, 06:26 | 6,017 | +6 |
| 30 Aug 2026, 22:57 | 6,011 | +5 |
| 29 Aug 2026, 19:43 | 6,006 | no change |
| 27 Aug 2026, 12:44 | 6,006 | -7 |
| 24 Aug 2026, 05:36 | 6,013 | -2 |
| 20 Aug 2026, 13:52 | 6,015 | +6 |
| 17 Aug 2026, 11:53 | 6,009 | +2 |
| 14 Aug 2026, 06:36 | 6,007 | +4 |
| 11 Aug 2026, 02:26 | 6,003 | +2 |
| 8 Aug 2026, 11:01 | 6,001 | -1 |
| 7 Aug 2026, 20:54 | 6,002 | 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.
@Biology_By_Dark2 · 21,812
Telegram ranks this channel #26 of 31 here — alongside 30 others — read 22 September 2026
@currentaffairsbyravistudyiqgk · 34,340
Telegram ranks this channel #41 of 44 here — alongside 43 others — read 3 September 2026
This channel appears in 2 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“DJ4X.in” (@dj4xin), 6,090 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/dj4xin.
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.