Channel
دی جی مرتضی چیذری +️ Dj MorTeza Chizari
@mortezachizari
On this record: Previous handles · Growth · Engagement · Telegram's recommendations · Cite this entry
8,052subscribers
+281 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 | -1001015135094 |
|---|---|
| Type | Channel |
| Username | @mortezachizari |
| Created | Between 1 December 2015 and 31 March 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/mortezachizari |
Previous handles
Recorded in 2019 as “Dj MorTeza Chizari” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 07:40 | 8,052 | +51 |
| 3 Sept 2026, 20:41 | 8,001 | +37 |
| 31 Aug 2026, 02:24 | 7,964 | +45 |
| 27 Aug 2026, 18:45 | 7,919 | +20 |
| 25 Aug 2026, 21:03 | 7,899 | no change |
| 25 Aug 2026, 04:46 | 7,899 | +31 |
| 21 Aug 2026, 19:16 | 7,868 | +37 |
| 18 Aug 2026, 05:32 | 7,831 | +17 |
| 15 Aug 2026, 01:08 | 7,814 | +32 |
| 8 Aug 2026, 03:38 | 7,782 | +11 |
| 7 Aug 2026, 04:09 | 7,771 | first reading |
Engagement
No public post preview. We read this entry on 25 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.
@hayedehremix · 43,319
Telegram ranks this channel #3 of 65 here — alongside 64 others — read 29 August 2026
@music_qp2 · 27,997
Telegram ranks this channel #27 of 43 here — alongside 42 others — read 10 September 2026
@tk_fo · 61,175
Telegram ranks this channel #38 of 69 here — alongside 68 others — read 22 August 2026
@djahmadrezaa · 43,507
Telegram ranks this channel #44 of 79 here — alongside 78 others — read 28 August 2026
@DjDarushmalmir · 80,529
Telegram ranks this channel #55 of 86 here — alongside 85 others — read 18 August 2026
@djmehras · 53,248
Telegram ranks this channel #58 of 90 here — alongside 89 others — read 24 August 2026
@djpuni · 30,213
Telegram ranks this channel #72 of 78 here — alongside 77 others — read 8 September 2026
This channel appears in 7 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“دی جی مرتضی چیذری +️ Dj MorTeza Chizari” (@mortezachizari), 8,052 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/mortezachizari.
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.