Politics & activism — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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
24 measurements spanning 92 days, net -88. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 5,809–6,015 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)
Subscribers
Change
6 Nov 2026, 12:06
5,833
-7
3 Nov 2026, 19:29
5,840
-9
1 Nov 2026, 02:56
5,849
-5
28 Oct 2026, 23:00
5,854
-3
25 Oct 2026, 12:40
5,857
+10
22 Oct 2026, 19:10
5,847
-8
19 Oct 2026, 20:25
5,855
-14
16 Oct 2026, 20:46
5,869
-7
13 Oct 2026, 10:58
5,876
-8
7 Oct 2026, 10:59
5,884
-10
30 Sept 2026, 05:39
5,894
-22
16 Sept 2026, 00:58
5,916
-24
11 Sept 2026, 23:35
5,940
-20
7 Sept 2026, 03:41
5,960
-15
2 Sept 2026, 02:54
5,975
-7
30 Aug 2026, 05:15
5,982
-9
27 Aug 2026, 07:25
5,991
+8
24 Aug 2026, 03:56
5,983
+39
20 Aug 2026, 03:38
5,944
+13
16 Aug 2026, 21:38
5,931
first reading
Engagement
55 posts held, back to 3 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 10 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
3.05%
avg views ÷ 5,833 subscribers
Avg views / post
178
11 posts measured
Reaction rate
2.76%
reactions ÷ views · ER floor
Posts in window
11
of 55 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 4 November 2026
Posts held
55 (3 August 2026 – 4 November 2026)
Views total
1,958
Reactions total
54
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
4 Nov 2026, 16:12 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Video runtime
1h 01m
Average length
12m 23s
Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
544 reactions across 54 posts, in 12 distinct kinds. The most used accounts for 59.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
324
59.6%
🤬
76
14.0%
🔥
55
10.1%
❤
37
6.80%
🤩
20
3.68%
👏
15
2.76%
👌
4
0.735%
👎
4
0.735%
💯
4
0.735%
💔
3
0.551%
🕊
1
0.184%
🤔
1
0.184%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 54 of the 55 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 544 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 55 most recent posts we hold, published 3 August 2026 to 4 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 11 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
ایران را نمیتوان با قومگرایی نجات داد
از تجربه تاریخی تجزیهطلبی تا خطر بازتولید گسلهای قومی در پوشش ایرانگرایی۴
در این الگو، زبان فارسی بهعنوان زبان مشترک و رسمی کشور میتواند نقش پیونددهنده و ارتباطی خود را حفظ کند، در حالی که زبانها و گویشهای دیگر نیز بخشی از میراث فرهنگی ایران باقی میمانند.
اگر جریانی پادشاهیخواه است، باید موضع خود را روشن کند. اگر جمهوریخواه است، باید همین کار را انجام دهد نه اینکه ا…
ایران را نمیتوان با قومگرایی نجات داد
از تجربه تاریخی تجزیهطلبی تا خطر بازتولید گسلهای قومی در پوشش ایرانگرایی۲
در۲۱آذر۱۳۲۴،حکومت خودمختار آذربایجان به رهبری جعفر پیشهوری در تبریز اعلام موجودیت کرد. در ژانویه۱۹۴۶نیز جمهوری مهاباد به رهبری قاضی محمد شکل گرفت.
این تحولات صرفاً محصول اختلافات فرهنگی یا زبانی نبودند
حضور نظامی شوروی،مداخله خارجی،رقابتهای ژئوپلیتیکی و اختلافات داخلی ایران در شکلگیری آنها نقش دا…
ایران را نمیتوان با قومگرایی نجات داد
از تجربه تاریخی تجزیهطلبی تا خطر بازتولید گسلهای قومی در پوشش ایرانگرایی۳
تحولات کردستان در سالهای نخست پس از شورش ۱۳۵۷ نیز از نظر جامعهشناسی سیاسی اهمیت دارد.
پس از شورش57، اختلاف میان دولت جدید و گروههای سیاسی کرد درباره خودمختاری، تمرکززدایی، ساختار قدرت و حقوق سیاسی و فرهنگی به منازعات گستردهای منجر شد. آن هم توسط جریان هایی که تا پیش از 57 حرفی از خودمختاری نمیزدن…
ایران را نمیتوان با قومگرایی نجات داد
از تجربه تاریخی تجزیهطلبی تا خطر بازتولید گسلهای قومی در پوشش ایرانگرایی۱
📌لطفا اگر حامی تمامیت ارضی ایران و رضاشاه دوم هستید، این یادداشت را کامل بخوانید.
مقدمه: خطر همیشه از جایی که انتظار داریم وارد نمیشود
در طول۴۷سال گذشته،یکی از ابزارهایی که جریانهای تجزیهطلب برای تضعیف انسجام ملی ایران به کار گرفتهاند،تحریک احساسات قومی و تبدیل تفاوتهای فرهنگی و زبانی به مرزبن…
#امیروفا_پیرویان تحلیلگر ژئوپلیتیک کنگره آزادی، به آغوش سپاه و آخوندا برگشت.
این همون مسیری هست که دیر یا زود، همهی اعضای کنگره آزادی طی خواهند کرد؛ دیر و زود داره، اما سوختوسوز نداره.
فقط کافیه یه مدت صبر کنید که یا ماموریتشون تموم بشه و یا مهره سوخته بشن.
پ.ن: خانم #مهدیه_گلرو گوزو ، شما کی برمیگردی؟ بابای آخوندت منتظرته بیشرف
#جاویدشاه
عبدالله عارف از اعضای گروه حقوق بشر بلوچستان که جزو تریبون های اصلی تبلیغاتی برای جبهه مبارزین مردمی یا همون جیش العدل هست رو مشاهده می کنید که در مورد پادشاهی خواهان و #رضاشاه_دوم چی میگه دقیقا با همان ادبیات مجاهدین خلق
هنوز نفهمیدید پشت جبهه مبارزین مردمی چه کسانی هستند؟
آقا جدا بنظرم اون فرد از تیم #رضاشاه_دوم که جلسات افراد با ایشون رو هماهنگ میکنه رو باید پاسخگو کرد!
چون با این کاراش که هرکسی رو با هر سابقه ای میاره در حضور رضاشاه دوم، جون ایشون رو به خطر میندازه!
#ایران_توحدی که همین چند وقت پیش تو جلسه اقوام، کنار شاه ایران حضور داشت، کسی هست که کتاب هاش تو رژیم چاپ میشه و همچنان تو سایت آستان قدس داره به فروش میره و حکومتیهایی مثل #عادل_فردوسیپور و #مجید_مجیدی کتابشو خریدن!…
در مورد سفیدشویان جبهه مبارزین مردمی/جیش العدل در ایکس بخش عجیبیش اینه اکانت هایی مشغول قهرمان سازی از جیش العدل اسلامیست هستند که تا دیروز ادعا می کردند دشمن اسلام و ادیان الهی هستند!!
چطوری یهویی دنده عوض کردید شدید مبلغ اسلامیست ها؟
مشکوک نیست
«مردم ایران دلاوری خود را پیشتر نشان دادهاند؛ اکنون نوبت اروپاست که شجاعت خود را نشان دهد.»
آلیس تئودورسکو ماوه، نماینده پارلمان اروپا، پس از دیدار با شاهزاده رضا پهلوی بار دیگر بر حمایت خود از مردم ایران و مبارزه آنان در راه آزادی تأکید کرد.
او خواهان حمایت سیاسی و اقدام عملی اروپا برای شکستن سد سانسور و خفقان اطلاعاتی رژیم، و ایجاد دسترسی امن مردم ایران به اینترنت آزاد شد تا ایرانیان بتوانند با یکدیگر برای سازم…
سرکوب در داخل/جنگطلبی در خارج/جمهوری اسلامی بدون تغییر
#𓉱𓄂IRAN_News𓆃𓉱
Showing the 12 most recent of 55 posts we hold for @guardShahanShahi. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.
اخبار نظامی ایران و جهان / جنگ @Axiuos · 54,905 Telegram ranks this channel #3 of 88 here — alongside 87 others — read 22 August 2026
اتحاد ملی ایران | اخبار جنگ @OmidIranAzad · 58,550 Telegram ranks this channel #20 of 94 here — alongside 93 others — read 23 August 2026
همگام با رضاشاه دوم @siasattalkh · 62,457 Telegram ranks this channel #22 of 93 here — alongside 92 others — read 21 August 2026
Reza Pahlavi | رضا پهلوی @OfficialRezaPahlavi · 365,142 Telegram ranks this channel #32 of 92 here — alongside 91 others — read 10 August 2026
🔴اخبار جنگ | آزادی | اِوین @Evin_khabar · 131,561 Telegram ranks this channel #43 of 80 here — alongside 79 others — read 13 August 2026
پراجکت لئون.اخبار جنگ،ترامپ،رژیم،در لحظه!هرشب آپدیت صوتی! @ProjectLeon7 · 52,246 Telegram ranks this channel #61 of 90 here — alongside 89 others — read 25 August 2026
ملی گرایان مردم گرا @Mellig · 153,504 Telegram ranks this channel #66 of 88 here — alongside 87 others — read 12 August 2026
This channel appears in 7 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 6 November 2026 — this
entry's latest reading, not the date you are reading this.
“گارد شاهنشاهی واحد افشاگری” (@guardShahanShahi), 5,833 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/guardShahanShahi.
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.