Channel
️Yousef Jamali
@Yousefjamalirad
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,288subscribers
+210 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001143392323 |
|---|---|
| Type | Channel |
| Username | @Yousefjamalirad |
| Created | Between 1 February 2016 and 31 October 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/Yousefjamalirad |
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 19 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 08:46 | 2,288 | -1 |
| 2 Nov 2026, 13:15 | 2,289 | -1 |
| 30 Oct 2026, 14:46 | 2,290 | -3 |
| 27 Oct 2026, 18:21 | 2,293 | -3 |
| 24 Oct 2026, 22:35 | 2,296 | -3 |
| 18 Oct 2026, 14:59 | 2,299 | -2 |
| 15 Oct 2026, 23:40 | 2,301 | +5 |
| 12 Oct 2026, 13:38 | 2,296 | -5 |
| 5 Oct 2026, 16:37 | 2,301 | +8 |
| 28 Sept 2026, 08:57 | 2,293 | +89 |
| 19 Sept 2026, 02:28 | 2,204 | no change |
| 19 Sept 2026, 02:21 | 2,204 | +94 |
| 14 Sept 2026, 08:38 | 2,110 | +23 |
| 10 Sept 2026, 10:36 | 2,087 | -7 |
| 4 Sept 2026, 19:57 | 2,094 | +2 |
| 1 Sept 2026, 13:08 | 2,092 | -3 |
| 29 Aug 2026, 21:27 | 2,095 | +2 |
| 26 Aug 2026, 20:55 | 2,093 | -2 |
| 24 Aug 2026, 01:49 | 2,095 | -5 |
| 20 Aug 2026, 20:05 | 2,100 | 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.
@Ramin_karami_music · 33,744
Telegram ranks this channel #20 of 88 here — alongside 87 others — read 7 September 2026
@aliahmadiyani_a · 46,753
Telegram ranks this channel #40 of 64 here — alongside 63 others — read 26 August 2026
@music_qp2 · 26,716
Telegram ranks this channel #43 of 43 here — alongside 42 others — read 10 September 2026
@farhadjahangiriorg · 64,441
Telegram ranks this channel #82 of 95 here — alongside 94 others — read 23 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“️Yousef Jamali” (@Yousefjamalirad), 2,288 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Yousefjamalirad.
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.