3 measurements spanning 8 days, net +2. 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 19–21 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
18 Aug 2026, 12:52
21
+2
11 Aug 2026, 17:46
19
no change
10 Aug 2026, 23:17
19
first reading
Engagement
13 posts held, back to 21 April 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
88.4%
avg views ÷ 21 subscribers
Avg views / post
18.6
9 posts measured
Reaction rate
3.85%
reactions ÷ views · ER floor
Posts in window
10
of 13 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. It is computed over the 2 of 9 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 8 August 2026
Posts held
13 (21 April 2025 – 8 August 2026)
Views total
167
Reactions total
1
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Aug 2026, 17:46 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.
Reaction mix
1 reaction across 1 post, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1
100.0%
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 3 of the 13 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 21 April 2025 to 8 August 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.
⬜ امیدوارم درک کرده باشید که مپر کیرمون کرده و مپ شاخی نداریم بهرحال
خطوط آبی فاصله های کوتاه رو نشون میده که حداقل بازشون یک ساعت هست یعنی شما اگه اول استارت لشکرکشی کرده باشید یک ساعت بعدش ارتش شما به قلعه میرسه و محاصره شروع میشه که رسیدن به قلعه رو خود ادمین اعلام میکنه سپس باید از دستور محاصره استغاده کنید
خطوط زرد نشانگر مسیر طولانی هست که دو ساعت زمان میبره و از اول استارت که شما لشکرکشی کشید بعد استاپ لشکرت…
[ 🇮🇶 ] [ Abbasid ]
🔰 قلعه پایتخت – بغداد قلب جهان اسلام.
نقطه قوت : قدرت فراخوانی نیروهای داوطلب مذهبی و ثروت افسانهای بازارها.
نقطه ضعف : شلوغی، احتمال شورشهای داخلی و کانالهای آبی که راه نفوذ مخفیانهست. دفاع از بغداد یعنی مدیریت آشوب.
🔰 قلعه موصل سد شمال.
نقطه قوت : قلعه کوهستانی مشرف به دشت که جلوی هر حملهای از شمال را میگیره.
نقطه ضعف : جمعیت مسیحی و کرد که وفاداریشان به خلافت همیشه شکنندهست.
🔰 ق…
[ 🇬🇷 ] [ Byzantine ]
🔰 قلعه پایتخت – قسطنطنیه غیرقابلنفوذترین شهر جهان مسیحیت.
نقطه قوت : دیوارهای سهگانه تئودوسیوسی، آبهای خلیج شاخ طلایی و آتش یونانی که هر ناوگانی را خاکستر میکنه.
نقطه ضعف : سیاستهای کاخ امپراتوری. اگر مدافعین به جان هم بیفتند، دیوارها به تنهایی کاری نمیکنن.
🔰 قلعه آدریانوپل سنگر بالکان.
نقطه قوت : فرماندهی بر تمام جادههای اروپایی و سوارهنظام زبده.
نقطه ضعف : فاصله کم با قبایل اسلا…
[ 🇹🇯 ] [ Samanid ]
🔰 قلعه پایتخت - سمرقند نگین جاده ابریشم.
نقطه قوت: تجارت و ثروت بیحساب که بهترین مزدوران و آهنگران را میآورد.
نقطه ضعف: فاصله زیاد از مرکز ایران و تهدید دائمی قبایل ترک استپها از شمال.
🔰 قلعه بخارا مرکز علم.
نقطه قوت : کتابخانه و علما که قدرت نرم و مشروعیت دینی میدهند.
نقطه ضعف : دیوارهای نهچندان بلند در برابر ارتشهای بزرگ.
🔰 قلعه چاچ پاسگاه مرزی
نقطه قوت : معادن آهن برای تجهیز ار…
[ 🇮🇷 ] [ Saffarid ]
🔰 قلعه پایتخت – زرنج دژ کویری و تسخیرناپذیر
نقطه قوت : دیوارهای خشتی عظیم که در گرمای سوزان، روحیه محاصرهکنندگان را نابود میکند و دسترسی محدود به آب شیرین در اطرافش.
نقطه ضعف : دوری از مراکز اصلی جمعیتی و عدم دسترسی به چوب برای تعمیرات سریع. تصرفش بدون قطع کامل کاروانهای شتر ناممکنه.
🔰 قلعه هرات دژ تجاری-نظامی با دیوارهای مستحکم.
نقطه قوت : چهارراه تجارت خراسان که ثروت و مزدوران ترک را …
🏛️ مأموریتهای مخصوص پادشاهیها
🔰 پادشاهی صفاریان : مأموریت پنهان یعقوب لیث و جانشینانش فقط کشورگشایی نیست، گرفتن مشروعیت از خلیفهست در حالی که او را تحقیر میکنند. هدف نهایی شما فتح بغداد و وادار کردن خلیفه به رسمیت شناختن صفاریان به عنوان امیرالامرای جهان اسلام با براندازی کامل خلافت عباسی است. دستیابی به این هدف، یک پیروزی دیپلماتیک-نظامی عظیم و کسب بیشترین امتیاز پیروزی در پایان سیزن خواهد بود.
🔰 خلافت عباسی :…
🏛️ در خصوص تم و جهان مینیسیزن
🔰 این سیزن در اواخر قرن نهم میلادی روایت میشه؛ دوران افول خلافت عباسی، ظهور سلسلههای ایرانیتبار و تداوم اقتدار بیزانس. چهار قدرت اصلی برای بقا و گسترش قلمرو میجنگند. تمام رولهای شما – از تأمین آذوقه گرفته تا فناوری محاصرهای – باید دقیقاً با محدودیتهای علمی، نظامی و اقتصادی این عصر مطابقت داشته باشه. صحبت از توپ باروتی، کشتیهای بخار یا شبکههای جاسوسی مدرن، رول شما رو فوراً باطل…
🏛️ مینی سیزن میراث صفاریان – به پرزورا خوش اومدید
به سیزنی کاملاً متفاوت و استراتژیک خوش اومدید؛ جایی که تاریخ رو شما با شمشیر، سیاست و تدبیر خودتون بازنویسی میکنید. مینیسیزن میراث صفاریان شما رو به قلب قرن نهم میلادی میبره، درست زمانی که شعلههای یک امپراتوری نوظهور در شرق، لرزه بر تن خلافت کهن انداخته و از آن سو امپراتوری روم شرقی با چشمانی تیزبین نظارهگر قدرتنمایی تازهواردهاست. این سیزن فقط بر اساس قوانینی ک…
Showing the 12 most recent of 13 posts we hold for @Perzura. 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.
Citation-graph rank
Citation-graph rank — 1,167,239 of 1,549,376entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 1 registered channel — 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.
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 18 August 2026 — this
entry's latest reading, not the date you are reading this.
“PerzuraMain | پرزورا” (@Perzura), 21 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/Perzura.
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.