Channel
محمد مهدی اردبیلی
@ardebili1402
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,052subscribers
+81 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001953105585 |
|---|---|
| Type | Channel |
| Username | @ardebili1402 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/ardebili1402 |
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 21 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 17:59 | 2,052 | +3 |
| 2 Nov 2026, 15:46 | 2,049 | +5 |
| 30 Oct 2026, 20:28 | 2,044 | +6 |
| 28 Oct 2026, 01:59 | 2,038 | +6 |
| 24 Oct 2026, 20:44 | 2,032 | +11 |
| 21 Oct 2026, 23:59 | 2,021 | +2 |
| 18 Oct 2026, 14:21 | 2,019 | +4 |
| 15 Oct 2026, 16:06 | 2,015 | -2 |
| 12 Oct 2026, 06:37 | 2,017 | +6 |
| 5 Oct 2026, 16:41 | 2,011 | +11 |
| 28 Sept 2026, 07:37 | 2,000 | +15 |
| 21 Sept 2026, 01:42 | 1,985 | no change |
| 18 Sept 2026, 12:37 | 1,985 | +3 |
| 13 Sept 2026, 21:58 | 1,982 | +5 |
| 10 Sept 2026, 11:16 | 1,977 | +8 |
| 5 Sept 2026, 07:59 | 1,969 | +1 |
| 1 Sept 2026, 18:35 | 1,968 | -3 |
| 28 Aug 2026, 23:45 | 1,971 | 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.
@Sedanet · 21,517
Telegram ranks this channel #19 of 91 here — alongside 90 others — read 23 September 2026
@Royal_psychologist · 19,607
Telegram ranks this channel #65 of 90 here — alongside 89 others — read 2 October 2026
@Poonehmoghimi · 42,708
Telegram ranks this channel #66 of 78 here — alongside 77 others — read 28 August 2026
@tarhvaredarmani1 · 22,899
Telegram ranks this channel #72 of 89 here — alongside 88 others — read 21 September 2026
@CBTRAVAN1 · 23,171
Telegram ranks this channel #74 of 88 here — alongside 87 others — read 20 September 2026
This channel appears in 5 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.
“محمد مهدی اردبیلی” (@ardebili1402), 2,052 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ardebili1402.
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.