Channel
استاد دکتر مهدی خیرالهی و استاد عرشیانفر
@Mahdikheyrolahi
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,793subscribers
+148 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001319062370 |
|---|---|
| Type | Channel |
| Username | @Mahdikheyrolahi |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/Mahdikheyrolahi |
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 83% 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 |
|---|---|---|
| 4 Nov 2026, 14:37 | 4,793 | +9 |
| 1 Nov 2026, 19:27 | 4,784 | +9 |
| 29 Oct 2026, 23:41 | 4,775 | -1 |
| 26 Oct 2026, 20:30 | 4,776 | +5 |
| 24 Oct 2026, 02:46 | 4,771 | -9 |
| 21 Oct 2026, 03:46 | 4,780 | +2 |
| 17 Oct 2026, 19:20 | 4,778 | +3 |
| 14 Oct 2026, 18:27 | 4,775 | +6 |
| 11 Oct 2026, 00:41 | 4,769 | +5 |
| 5 Oct 2026, 04:21 | 4,764 | +8 |
| 26 Sept 2026, 04:19 | 4,756 | -3 |
| 17 Sept 2026, 14:21 | 4,759 | +11 |
| 13 Sept 2026, 16:38 | 4,748 | +4 |
| 9 Sept 2026, 20:36 | 4,744 | +10 |
| 4 Sept 2026, 05:57 | 4,734 | +11 |
| 2 Sept 2026, 19:12 | 4,723 | no change |
| 31 Aug 2026, 23:48 | 4,723 | +6 |
| 29 Aug 2026, 04:56 | 4,717 | +12 |
| 25 Aug 2026, 20:55 | 4,705 | +36 |
| 22 Aug 2026, 11:52 | 4,669 | 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.
@arshiyaniha · 63,477
Telegram ranks this channel #2 of 81 here — alongside 80 others — read 21 August 2026
@elhaamacademy · 22,061
Telegram ranks this channel #6 of 71 here — alongside 70 others — read 2 October 2026
@Arshian_International_Group · 84,401
Telegram ranks this channel #11 of 73 here — alongside 72 others — read 18 August 2026
This channel appears in 3 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“استاد دکتر مهدی خیرالهی و استاد عرشیانفر” (@Mahdikheyrolahi), 4,793 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/Mahdikheyrolahi.
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.