Channel
Mohammad Mansourpour |محمدمنصورپور
@mohammadmansourpour3
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,794subscribers
+45 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001298639298 |
|---|---|
| Type | Channel |
| Username | @mohammadmansourpour3 |
| 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 | 2 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/mohammadmansourpour3 |
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 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 |
|---|---|---|
| 2 Nov 2026, 22:06 | 4,794 | -11 |
| 30 Oct 2026, 12:36 | 4,805 | -11 |
| 27 Oct 2026, 03:58 | 4,816 | -5 |
| 24 Oct 2026, 03:16 | 4,821 | -2 |
| 20 Oct 2026, 20:06 | 4,823 | -14 |
| 18 Oct 2026, 00:40 | 4,837 | -4 |
| 15 Oct 2026, 05:58 | 4,841 | -7 |
| 11 Oct 2026, 22:20 | 4,848 | -13 |
| 5 Oct 2026, 09:00 | 4,861 | +42 |
| 27 Sept 2026, 07:56 | 4,819 | +130 |
| 18 Sept 2026, 11:42 | 4,689 | +12 |
| 13 Sept 2026, 18:17 | 4,677 | -12 |
| 9 Sept 2026, 22:39 | 4,689 | -7 |
| 4 Sept 2026, 20:58 | 4,696 | -10 |
| 2 Sept 2026, 20:13 | 4,706 | no change |
| 31 Aug 2026, 23:36 | 4,706 | -5 |
| 28 Aug 2026, 14:17 | 4,711 | -2 |
| 25 Aug 2026, 04:44 | 4,713 | -10 |
| 22 Aug 2026, 01:18 | 4,723 | -13 |
| 19 Aug 2026, 00:53 | 4,736 | 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.
@hannabidar · 215,373
Telegram ranks this channel #5 of 58 here — alongside 57 others — read 14 August 2026
@shimamuzic · 30,895
Telegram ranks this channel #39 of 85 here — alongside 84 others — read 6 September 2026
@alimoosic_tel · 54,009
Telegram ranks this channel #56 of 82 here — alongside 81 others — read 25 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Mohammad Mansourpour |محمدمنصورپور” (@mohammadmansourpour3), 4,794 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/mohammadmansourpour3.
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.