
Channel
DJ ALEX
@djalexalidad
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,470subscribers
+38 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001106128510 |
|---|---|
| Type | Channel |
| Username | @djalexalidad |
| Created | Between 1 February 2017 and 31 December 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/djalexalidad |
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 16 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 |
|---|---|---|
| 7 Nov 2026, 06:30 | 2,470 | +3 |
| 4 Nov 2026, 12:08 | 2,467 | +4 |
| 1 Nov 2026, 14:54 | 2,463 | +2 |
| 30 Oct 2026, 00:07 | 2,461 | -2 |
| 26 Oct 2026, 14:20 | 2,463 | -2 |
| 23 Oct 2026, 17:46 | 2,465 | +3 |
| 20 Oct 2026, 20:28 | 2,462 | +7 |
| 17 Oct 2026, 13:15 | 2,455 | +3 |
| 14 Oct 2026, 15:11 | 2,452 | -3 |
| 5 Oct 2026, 12:01 | 2,455 | +8 |
| 27 Sept 2026, 14:00 | 2,447 | -9 |
| 16 Sept 2026, 00:56 | 2,456 | no change |
| 14 Sept 2026, 10:17 | 2,456 | -2 |
| 10 Sept 2026, 23:38 | 2,458 | +4 |
| 5 Sept 2026, 13:58 | 2,454 | +1 |
| 2 Sept 2026, 00:09 | 2,453 | +8 |
| 29 Aug 2026, 23:23 | 2,445 | +1 |
| 26 Aug 2026, 21:34 | 2,444 | +1 |
| 24 Aug 2026, 04:54 | 2,443 | +5 |
| 20 Aug 2026, 12:06 | 2,438 | 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.
@djjalexalidad · 28,893
Telegram ranks this channel #6 of 85 here — alongside 84 others — read 10 September 2026
@dj_soushi_music · 128,179
Telegram ranks this channel #35 of 87 here — alongside 86 others — read 13 August 2026
@djjam_org · 46,049
Telegram ranks this channel #42 of 66 here — alongside 65 others — read 28 September 2026
@barbodmusiccc · 24,698
Telegram ranks this channel #49 of 71 here — alongside 70 others — read 18 September 2026
@AvangRecords · 42,501
Telegram ranks this channel #78 of 81 here — alongside 80 others — read 30 August 2026
This channel appears in 5 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“DJ ALEX” (@djalexalidad), 2,470 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/djalexalidad.
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.