Channel
محفل بیت الاحزان حضرت زینب(سلام الله علیها)
@beytol_ahzan_zeynab
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,530subscribers
+53 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001082056980 |
|---|---|
| Type | Channel |
| Username | @beytol_ahzan_zeynab |
| Description | محفل بیت الاحزان حضرت زینب(س) متوسلینبهشاهزادهعلیاصغر(ع) مشهدمقدس اطلاعرسانی جلسات نشرکلیپهاوصوتهایجلسه پیچاینستاگرامbeytolahzan.official |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 September 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 15 |
| On Telegram | t.me/beytol_ahzan_zeynab |
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 27 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 16:16 | 1,530 | no change |
| 24 Sept 2026, 21:58 | 1,530 | -2 |
| 16 Sept 2026, 13:55 | 1,532 | +2 |
| 13 Sept 2026, 01:41 | 1,530 | -6 |
| 9 Sept 2026, 06:40 | 1,536 | +8 |
| 4 Sept 2026, 08:17 | 1,528 | +3 |
| 1 Sept 2026, 00:54 | 1,525 | -1 |
| 25 Aug 2026, 18:45 | 1,526 | +3 |
| 22 Aug 2026, 22:22 | 1,523 | +3 |
| 19 Aug 2026, 22:02 | 1,520 | +9 |
| 16 Aug 2026, 14:53 | 1,511 | +16 |
| 13 Aug 2026, 04:05 | 1,495 | +6 |
| 10 Aug 2026, 03:32 | 1,489 | +5 |
| 7 Aug 2026, 12:01 | 1,484 | +7 |
| 6 Aug 2026, 16:12 | 1,477 | 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.
@amirhoseinhazrati128 · 38,669
Telegram ranks this channel #49 of 94 here — alongside 93 others — read 31 August 2026
@naseri205 · 20,855
Telegram ranks this channel #50 of 94 here — alongside 93 others — read 25 September 2026
@morteza_yebor313 · 70,488
Telegram ranks this channel #56 of 92 here — alongside 91 others — read 20 August 2026
@eeydanian315 · 22,123
Telegram ranks this channel #60 of 92 here — alongside 91 others — read 21 September 2026
This channel appears in 4 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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“محفل بیت الاحزان حضرت زینب(سلام الله علیها)” (@beytol_ahzan_zeynab), 1,530 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/beytol_ahzan_zeynab.
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.