Channel
Pars Music original
@parsmusicoriginal
On this record: Topic · Previous handles · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry
35,952subscribers
-483 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001008277800 |
|---|---|
| Type | Channel |
| Username | @parsmusicoriginal |
| Created | 25 September 2015 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 5 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/parsmusicoriginal |
Topic
Music — a classification, not a measurement. 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.
Previous handles
Recorded in 2019 as “دانلود آهنگ جدید|Pars Music” — 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 |
|---|---|---|
| 19 Sept 2026, 09:40 | 35,952 | -30 |
| 16 Sept 2026, 20:19 | 35,982 | -21 |
| 15 Sept 2026, 02:01 | 36,003 | -18 |
| 13 Sept 2026, 07:57 | 36,021 | -15 |
| 11 Sept 2026, 12:16 | 36,036 | -21 |
| 8 Sept 2026, 18:40 | 36,057 | -45 |
| 5 Sept 2026, 09:37 | 36,102 | -20 |
| 3 Sept 2026, 09:47 | 36,122 | -5 |
| 2 Sept 2026, 01:42 | 36,127 | -12 |
| 1 Sept 2026, 03:07 | 36,139 | -19 |
| 30 Aug 2026, 23:38 | 36,158 | -14 |
| 30 Aug 2026, 00:54 | 36,172 | -7 |
| 29 Aug 2026, 03:48 | 36,179 | -9 |
| 28 Aug 2026, 04:58 | 36,188 | -7 |
| 27 Aug 2026, 05:04 | 36,195 | -6 |
| 26 Aug 2026, 04:54 | 36,201 | -12 |
| 25 Aug 2026, 01:48 | 36,213 | -16 |
| 23 Aug 2026, 18:19 | 36,229 | -19 |
| 22 Aug 2026, 03:28 | 36,248 | -21 |
| 20 Aug 2026, 21:13 | 36,269 | first reading |
Engagement
No public post preview. We read this entry on 5 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.
@RadioMusic · 50,834
Telegram ranks this channel #1 of 53 here — alongside 52 others — read 25 August 2026
@smusicoriginal · 77,320
Telegram ranks this channel #1 of 51 here — alongside 50 others — read 19 August 2026
@dtaraneh · 81,109
Telegram ranks this channel #10 of 70 here — alongside 69 others — read 26 August 2026
@Navahang · 88,658
Telegram ranks this channel #12 of 73 here — alongside 72 others — read 19 August 2026
@number1music · 58,625
Telegram ranks this channel #24 of 69 here — alongside 68 others — read 23 August 2026
@ganja2music · 102,795
Telegram ranks this channel #35 of 84 here — alongside 83 others — read 15 August 2026
This channel appears in 6 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Pars Music original” (@parsmusicoriginal), 35,952 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/parsmusicoriginal.
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.