Channel
NITREX
@djnitrex
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,036subscribers
+356 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001431925189 |
|---|---|
| Type | Channel |
| Username | @djnitrex |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/djnitrex |
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 15 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 22:46 | 3,036 | +2 |
| 2 Nov 2026, 03:39 | 3,034 | +5 |
| 30 Oct 2026, 09:40 | 3,029 | +16 |
| 27 Oct 2026, 14:17 | 3,013 | +8 |
| 24 Oct 2026, 09:58 | 3,005 | +6 |
| 21 Oct 2026, 00:46 | 2,999 | -5 |
| 17 Oct 2026, 20:18 | 3,004 | -4 |
| 14 Oct 2026, 11:39 | 3,008 | +14 |
| 11 Oct 2026, 09:19 | 2,994 | +36 |
| 5 Oct 2026, 12:00 | 2,958 | +38 |
| 27 Sept 2026, 15:16 | 2,920 | +89 |
| 15 Sept 2026, 19:54 | 2,831 | +52 |
| 13 Sept 2026, 01:07 | 2,779 | no change |
| 12 Sept 2026, 13:41 | 2,779 | +14 |
| 8 Sept 2026, 10:58 | 2,765 | +32 |
| 3 Sept 2026, 01:15 | 2,733 | +26 |
| 30 Aug 2026, 12:54 | 2,707 | +27 |
| 27 Aug 2026, 12:15 | 2,680 | 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.
@djmikisofficial · 21,398
Telegram ranks this channel #4 of 90 here — alongside 89 others — read 25 September 2026
@alexshikdj · 54,750
Telegram ranks this channel #8 of 89 here — alongside 88 others — read 27 August 2026
@Dj_Zuxa_Music · 32,031
Telegram ranks this channel #27 of 83 here — alongside 82 others — read 5 September 2026
@djtabremixofficial · 45,584
Telegram ranks this channel #38 of 81 here — alongside 80 others — read 27 August 2026
This channel appears in 4 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“NITREX” (@djnitrex), 3,036 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/djnitrex.
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.