Channel
بیرق معظم یاحسین(ع)کرج
@beyragh_yahosein
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,009subscribers
+74 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001109577430 |
|---|---|
| Type | Channel |
| Username | @beyragh_yahosein |
| Created | Between 1 February 2017 and 31 December 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/beyragh_yahosein |
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 97% 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 |
|---|---|---|
| 4 Nov 2026, 10:28 | 4,009 | +16 |
| 1 Nov 2026, 07:59 | 3,993 | +45 |
| 29 Oct 2026, 16:26 | 3,948 | +69 |
| 26 Oct 2026, 11:06 | 3,879 | +1 |
| 23 Oct 2026, 03:30 | 3,878 | +5 |
| 20 Oct 2026, 11:59 | 3,873 | -3 |
| 17 Oct 2026, 06:29 | 3,876 | -9 |
| 14 Oct 2026, 06:27 | 3,885 | -3 |
| 10 Oct 2026, 17:40 | 3,888 | -4 |
| 4 Oct 2026, 20:01 | 3,892 | -19 |
| 24 Sept 2026, 21:40 | 3,911 | -3 |
| 16 Sept 2026, 11:00 | 3,914 | -4 |
| 13 Sept 2026, 00:22 | 3,918 | -1 |
| 9 Sept 2026, 02:57 | 3,919 | -4 |
| 5 Sept 2026, 23:21 | 3,923 | no change |
| 3 Sept 2026, 18:15 | 3,923 | -2 |
| 28 Aug 2026, 10:53 | 3,925 | -6 |
| 25 Aug 2026, 04:57 | 3,931 | -2 |
| 22 Aug 2026, 11:32 | 3,933 | -2 |
| 21 Aug 2026, 20:30 | 3,935 | 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.
@buyesib_com · 30,578
Telegram ranks this channel #11 of 93 here — alongside 92 others — read 6 September 2026
@ArdabilMusik · 122,193
Telegram ranks this channel #41 of 65 here — alongside 64 others — read 21 August 2026
@K_ataieniya315 · 37,936
Telegram ranks this channel #57 of 94 here — alongside 93 others — read 2 September 2026
@HADISDEll_313 · 20,073
Telegram ranks this channel #75 of 86 here — alongside 85 others — read 28 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“بیرق معظم یاحسین(ع)کرج” (@beyragh_yahosein), 4,009 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/beyragh_yahosein.
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.