Channel
فرزاد فرجی
@farzadmusic8
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,438subscribers
+53 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 | -1001301634832 |
|---|---|
| Type | Channel |
| Username | @farzadmusic8 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/farzadmusic8 |
Topic
Other / unclassifiable — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 15 Sept 2026, 15:38 | 4,438 | +14 |
| 11 Sept 2026, 21:36 | 4,424 | +10 |
| 7 Sept 2026, 20:39 | 4,414 | +5 |
| 3 Sept 2026, 22:23 | 4,409 | no change |
| 3 Sept 2026, 02:37 | 4,409 | +2 |
| 30 Aug 2026, 15:12 | 4,407 | +7 |
| 27 Aug 2026, 14:32 | 4,400 | -1 |
| 24 Aug 2026, 05:05 | 4,401 | +8 |
| 20 Aug 2026, 04:28 | 4,393 | +2 |
| 17 Aug 2026, 11:13 | 4,391 | +4 |
| 10 Aug 2026, 16:03 | 4,387 | +2 |
| 7 Aug 2026, 08:24 | 4,385 | 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.
@taymornamazii · 26,223
Telegram ranks this channel #4 of 59 here — alongside 58 others — read 13 September 2026
@farshadaminii · 40,665
Telegram ranks this channel #14 of 55 here — alongside 54 others — read 30 August 2026
@delsouzkhaledii · 28,524
Telegram ranks this channel #25 of 65 here — alongside 64 others — read 9 September 2026
@Roholakarami · 36,975
Telegram ranks this channel #26 of 62 here — alongside 61 others — read 1 September 2026
@Rahmatazary · 31,029
Telegram ranks this channel #42 of 77 here — alongside 76 others — read 7 September 2026
@miladahmaditel · 22,179
Telegram ranks this channel #53 of 72 here — alongside 71 others — read 21 September 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“فرزاد فرجی” (@farzadmusic8), 4,438 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/farzadmusic8.
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.