Channel
حاج مهدی اکبری
@HAJ_MEHDIAKBARI
On this record: Topic · Previous handles · Growth · Engagement · Telegram's recommendations · Cite this entry
5,618subscribers
-73 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001493733757 |
|---|---|
| Type | Channel |
| Username | @HAJ_MEHDIAKBARI |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/HAJ_MEHDIAKBARI |
Topic
Religion — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Previous handles
@HAJ_MEHDIAKBARI was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 30 August 2026 – 30 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 23:58 | 5,618 | -4 |
| 13 Sept 2026, 00:59 | 5,622 | -4 |
| 8 Sept 2026, 21:10 | 5,626 | no change |
| 8 Sept 2026, 21:00 | 5,626 | +5,058 |
| 31 Aug 2026, 06:45 | 568 | -5,075 |
| 30 Aug 2026, 19:54 | 5,643 | no change |
| 30 Aug 2026, 15:16 | 5,643 | -4 |
| 27 Aug 2026, 05:06 | 5,647 | -4 |
| 23 Aug 2026, 23:01 | 5,651 | -8 |
| 20 Aug 2026, 11:08 | 5,659 | -7 |
| 17 Aug 2026, 15:06 | 5,666 | -6 |
| 14 Aug 2026, 10:57 | 5,672 | -4 |
| 11 Aug 2026, 08:12 | 5,676 | -11 |
| 7 Aug 2026, 21:52 | 5,687 | -4 |
| 6 Aug 2026, 23:38 | 5,691 | 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.
@vahidshokri128 · 41,363
Telegram ranks this channel #19 of 92 here — alongside 91 others — read 29 August 2026
@maddahionlin · 39,945
Telegram ranks this channel #45 of 90 here — alongside 89 others — read 2 September 2026
@Alamdarbabol · 28,216
Telegram ranks this channel #81 of 93 here — alongside 92 others — read 9 September 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“حاج مهدی اکبری” (@HAJ_MEHDIAKBARI), 5,618 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/HAJ_MEHDIAKBARI.
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.