Channel
Farshidsabamusic 🎶
@farshidsabamusic
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,868subscribers
+837 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 | -1001425538556 |
|---|---|
| Type | Channel |
| Username | @farshidsabamusic |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/farshidsabamusic |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 24 Oct 2026, 01:20 | 5,868 | +34 |
| 20 Oct 2026, 16:21 | 5,834 | +46 |
| 17 Oct 2026, 09:30 | 5,788 | +8 |
| 14 Oct 2026, 13:04 | 5,780 | +33 |
| 11 Oct 2026, 05:19 | 5,747 | +68 |
| 5 Oct 2026, 02:02 | 5,679 | +78 |
| 26 Sept 2026, 11:56 | 5,601 | +111 |
| 17 Sept 2026, 01:58 | 5,490 | +29 |
| 13 Sept 2026, 06:16 | 5,461 | +46 |
| 9 Sept 2026, 12:57 | 5,415 | +80 |
| 4 Sept 2026, 04:00 | 5,335 | +36 |
| 31 Aug 2026, 21:23 | 5,299 | no change |
| 31 Aug 2026, 16:03 | 5,299 | +34 |
| 28 Aug 2026, 17:16 | 5,265 | +49 |
| 26 Aug 2026, 02:12 | 5,216 | +24 |
| 22 Aug 2026, 15:52 | 5,192 | +37 |
| 18 Aug 2026, 23:25 | 5,155 | +41 |
| 15 Aug 2026, 15:42 | 5,114 | +56 |
| 11 Aug 2026, 19:42 | 5,058 | +17 |
| 8 Aug 2026, 13:33 | 5,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.
@taymornamazii · 26,503
Telegram ranks this channel #6 of 59 here — alongside 58 others — read 13 September 2026
@miladahmaditel · 21,893
Telegram ranks this channel #7 of 72 here — alongside 71 others — read 21 September 2026
@bartaonana · 19,145
Telegram ranks this channel #26 of 61 here — alongside 60 others — read 3 October 2026
@FARSHADAMI · 75,117
Telegram ranks this channel #32 of 71 here — alongside 70 others — read 19 August 2026
This channel appears in 4 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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“Farshidsabamusic 🎶” (@farshidsabamusic), 5,868 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/farshidsabamusic.
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.