Channel
Navid Arbabian
@Navid_Arbabian
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,247subscribers
+12 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001426942394 |
|---|---|
| Type | Channel |
| Username | @Navid_Arbabian |
| Description | Musician from khorasan http://Instagram.com/navidarbabian https://www.youtube.com/c/navidarbabianmusician https://open.spotify.com/artist/7eqG9RWRnH6ycS2axPUSl4?si=_Quni_EqSn20Ml1gxmsTOg https://soundcloud.com/navid-arbabian https://navidarbabian.com |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| On Telegram | t.me/Navid_Arbabian |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 18 Sept 2026, 01:29 | 2,247 | no change |
| 16 Sept 2026, 16:56 | 2,247 | -3 |
| 13 Sept 2026, 05:18 | 2,250 | -1 |
| 9 Sept 2026, 09:01 | 2,251 | -1 |
| 28 Aug 2026, 23:32 | 2,252 | +1 |
| 25 Aug 2026, 13:57 | 2,251 | +2 |
| 22 Aug 2026, 09:57 | 2,249 | -8 |
| 19 Aug 2026, 05:33 | 2,257 | +5 |
| 16 Aug 2026, 13:53 | 2,252 | +7 |
| 13 Aug 2026, 03:05 | 2,245 | +6 |
| 10 Aug 2026, 02:28 | 2,239 | +3 |
| 7 Aug 2026, 10:18 | 2,236 | +1 |
| 6 Aug 2026, 18:52 | 2,235 | 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.
@Official_MohsenNamjoo · 44,898
Telegram ranks this channel #7 of 83 here — alongside 82 others — read 27 August 2026
@owrsi · 55,176
Telegram ranks this channel #7 of 84 here — alongside 83 others — read 23 August 2026
@shaaynnshid · 28,641
Telegram ranks this channel #18 of 90 here — alongside 89 others — read 9 September 2026
@radiolimoo · 36,336
Telegram ranks this channel #20 of 85 here — alongside 84 others — read 1 September 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Navid Arbabian” (@Navid_Arbabian), 2,247 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Navid_Arbabian.
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.