Telegram RegisterThe public register of Telegram
Telegram profile photo for DJ Phellix

Channel

DJ Phellix

@DJPhellix

Verified by Telegram

On this record: Growth · Engagement · Telegram's recommendations · Cite this entry

29,477subscribers

+1,147 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001267475290
TypeChannel
Username@DJPhellix
Created2 November 2017measured — cross-checked against a third-party dataset (TGDataset)
First recorded14 August 2026
Last confirmed live24 August 2026
Measurements held18
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/DJPhellix

Growth

28,33029,47728,903.56 August 2026 — 28,330 subscribers8 August 2026 — 28,339 subscribers9 August 2026 — 28,344 subscribers10 August 2026 — 28,347 subscribers11 August 2026 — 28,353 subscribers12 August 2026 — 28,352 subscribers12 August 2026 — 28,367 subscribers14 August 2026 — 28,396 subscribers14 August 2026 — 28,396 subscribers15 August 2026 — 28,420 subscribers16 August 2026 — 28,435 subscribers17 August 2026 — 28,442 subscribers18 August 2026 — 28,444 subscribers19 August 2026 — 28,443 subscribers20 August 2026 — 28,452 subscribers21 August 2026 — 28,772 subscribers23 August 2026 — 29,379 subscribers24 August 2026 — 29,477 subscribers6 August 202624 August 2026
18 measurements spanning 19 days, net +1,147. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 28,158–29,649 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 19:2829,477+98
23 Aug 2026, 05:0329,379+607
21 Aug 2026, 18:4828,772+320
20 Aug 2026, 14:2428,452+9
19 Aug 2026, 17:2228,443-1
18 Aug 2026, 19:4728,444+2
17 Aug 2026, 20:2328,442+7
16 Aug 2026, 22:0728,435+15
15 Aug 2026, 18:2528,420+24
14 Aug 2026, 18:4128,396no change
14 Aug 2026, 10:2828,396+29
12 Aug 2026, 22:5728,367+15
12 Aug 2026, 01:1228,352-1
11 Aug 2026, 01:3328,353+6
10 Aug 2026, 01:1128,347+3
9 Aug 2026, 03:5228,344+5
8 Aug 2026, 02:3828,339+9
6 Aug 2026, 05:0028,330first reading

Engagement

No public post preview. We read this entry on 14 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

NOYAN | نویان
@noyanbahadori · 206,603
Telegram ranks this channel #76 of 83 here — alongside 82 others — read 11 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“DJ Phellix” (@DJPhellix), 29,477 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/DJPhellix.

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.