Channel
PERSiAN DJ
@PERSIAN_DJS
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,076subscribers
+35 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001053272414 |
|---|---|
| Type | Channel |
| Username | @PERSIAN_DJS |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 October 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/PERSIAN_DJS |
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 7 October 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 18:19 | 1,076 | +3 |
| 7 Oct 2026, 05:33 | 1,073 | no change |
| 4 Oct 2026, 22:39 | 1,073 | +3 |
| 25 Sept 2026, 22:01 | 1,070 | +9 |
| 17 Sept 2026, 07:15 | 1,061 | +6 |
| 13 Sept 2026, 10:57 | 1,055 | +1 |
| 9 Sept 2026, 09:57 | 1,054 | -6 |
| 4 Sept 2026, 11:02 | 1,060 | +5 |
| 31 Aug 2026, 19:45 | 1,055 | +2 |
| 25 Aug 2026, 21:33 | 1,053 | +2 |
| 22 Aug 2026, 21:27 | 1,051 | +4 |
| 19 Aug 2026, 11:38 | 1,047 | +1 |
| 16 Aug 2026, 05:45 | 1,046 | +1 |
| 13 Aug 2026, 01:34 | 1,045 | +1 |
| 9 Aug 2026, 18:12 | 1,044 | +3 |
| 6 Aug 2026, 17:41 | 1,041 | 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.
@DJPhellix · 31,688
Telegram ranks this channel #4 of 63 here — alongside 62 others — read 7 September 2026
@DJTabaOfficial · 36,000
Telegram ranks this channel #15 of 57 here — alongside 56 others — read 2 September 2026
@WhiteMtproto · 43,044
Telegram ranks this channel #37 of 52 here — alongside 51 others — read 26 August 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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“PERSiAN DJ” (@PERSIAN_DJS), 1,076 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/PERSIAN_DJS.
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.