Channel
محفل شاه نجف فردیس
@mahfele_shahe_najaf
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,965subscribers
+12 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 | -1001256704443 |
|---|---|
| Type | Channel |
| Username | @mahfele_shahe_najaf |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/mahfele_shahe_najaf |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 02:16 | 3,965 | +3 |
| 14 Sept 2026, 07:40 | 3,962 | +2 |
| 10 Sept 2026, 13:19 | 3,960 | +6 |
| 5 Sept 2026, 22:44 | 3,954 | no change |
| 5 Sept 2026, 13:01 | 3,954 | -5 |
| 1 Sept 2026, 04:26 | 3,959 | +3 |
| 28 Aug 2026, 23:13 | 3,956 | -2 |
| 26 Aug 2026, 08:53 | 3,958 | -2 |
| 23 Aug 2026, 16:04 | 3,960 | -1 |
| 20 Aug 2026, 06:56 | 3,961 | +3 |
| 17 Aug 2026, 10:14 | 3,958 | +5 |
| 14 Aug 2026, 03:14 | 3,953 | -2 |
| 10 Aug 2026, 11:14 | 3,955 | +3 |
| 7 Aug 2026, 12:25 | 3,952 | -1 |
| 6 Aug 2026, 15:10 | 3,953 | 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.
@Alamdarbabol · 28,216
Telegram ranks this channel #1 of 93 here — alongside 92 others — read 9 September 2026
@K_ataieniya315 · 36,102
Telegram ranks this channel #33 of 94 here — alongside 93 others — read 2 September 2026
@vahidshokri128 · 41,363
Telegram ranks this channel #36 of 92 here — alongside 91 others — read 29 August 2026
@amirhoseinhazrati128 · 38,402
Telegram ranks this channel #39 of 94 here — alongside 93 others — read 31 August 2026
@hoseinizadkhah · 29,012
Telegram ranks this channel #47 of 97 here — alongside 96 others — read 9 September 2026
@morteza_yebor313 · 70,315
Telegram ranks this channel #72 of 92 here — alongside 91 others — read 20 August 2026
This channel appears in 6 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“محفل شاه نجف فردیس” (@mahfele_shahe_najaf), 3,965 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/mahfele_shahe_najaf.
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.