Posted without readable text

Channel
PerzuraWar | پرزورا وار
@PerzuraWar
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
20subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003179387776 |
|---|---|
| Type | Channel |
| Username | @PerzuraWar |
| Created | Between 1 September 2025 and 31 December 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/PerzuraWar |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 09:28 | 20 | no change |
| 11 Aug 2026, 17:46 | 20 | first reading |
Engagement
20 posts held, back to 9 July 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- —
- no view readings in window
- Avg views / post
- —
- no view readings
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 20 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.
| Window | Rolling 30 days · latest post in window 20 July 2026 |
|---|---|
| Posts held | 20 (9 July 2026 – 20 July 2026) |
| Views total | — |
| Reactions total | — |
| 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
3 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 3 | 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 1 of the 20 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 9 July 2026 to 20 July 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
نتیجه مساوی به سود قوای چینی نمره سنا هند 🇮🇳 9.5 نمره سنا چین 🇨🇳 9.9
نتیجه : پیروزی قوای روسیه و فتح باقیمانده خاک های گرجستان نمره سنا روسیه 🇷🇺 : 13.2
نتیجه پیروزی ارتش ایران و نابودسازی اسکادران ایالات متحده آمریکا نمره سنا ایالات متحده آمریکا 🇺🇸 8.6 نمره سنا جمهوری اسلامی ایران 🇮🇷 12.3
نتیجه پیروزی قوای دریایی ایالات متحده آمریکا و بازکردن تنگه باب المندب نمره سنا ایالات متحده آمریکا 🇺🇸 10.1
📜 پارت دوم 📝 شرح نبرد – نقطه عطف : خورشید به میانه آسمان رسیده بود و نبرد الکترونیک به اوج خود رسیده بود. امارات که از اختلال ایران به تنگ آمده بود،جنگنده های خود را برای حمله مستقیم به ناو جنگی ایران فرستاد. اما در این لحظه، ضعف آرایش امارات آشکار شد: تمرکز کامل بر جنگ الکترونیک، آنان را از شناسایی آرایش ششضلعی ایران غافل کرده بود. ناوهای ایرانی که در ششضلعی چیده شده بودند، از هوا و عقب پوشش کامل داشتند و فضای با…
🗞️ نبرد تنگه هرمز 📜 پارت اول 📌 پیشزمینه : مهگرفتگی صبحگاهی خلیج فارس، پردهای خاکستری بر آبهای نیلگون کشیده بود. جمهوری اسلامی ایران با ناو جنگی خود در قلب تنگه هرمز لنگر انداخته بود؛ چهار ناوشکن دایرهای کامل به شعاع ۱۰ تا ۱۵ کیلومتر پیرامونش تشکیل داده بودند و ناوهای محافظ در لایه دوم به خط ساحل چسبیده بودند. قایقهای تندرو چون زنبورانی نگهبان در اطراف جزایر ابوموسی و لارک گشت میزدند و هر تحرک مشکوک را به ن…
نتیجه : پیروزی قوای جمهوری اسلامی ایران و فتح شهر باکو آذربایجان و پایان کار آذربایجان در دنیای هستی نمره سنا جمهوری اسلامی ایران 🇮🇷 : 10.6
نتیجه : پیروزی قوای ارمنستان و پیشروی در مرزهای باقیمانده آذربايجان نمره سنا ارمنستان 🇦🇲 9.6
📜 پارت دوم 📝 شرح نبرد – نقطه عطف : خورشید به میانه آسمان رسیده بود و دود ناشی از انفجار ماکتهای فیک امارات، دید را برای هر دو طرف کاهش داده بود. در این آشوب، ایران ضربه اصلی خود را فرود آورد: زیردریاییهای ایرانی که در دورترین نقاط کمین کرده بودند، با شلیک اژدر پوسایدن، سونامی مصنوعی در میان ناوگان امارات ایجاد کردند. امواج سهمگین، آرایش پلکانی امارات را در هم شکست و چندین ناوچه سبک را واژگون ساخت. همزمان، موشکها…
🗞️ نبرد خلیج فارس 📜 پارت اول 📌 پیشزمینه : مهگرفتگی صبحگاهی خلیج فارس، پردهای خاکستری بر آبهای نیلگون کشیده بود. ایران با ناوگانی انقلابی و دکترینی نامتقارن در برابر امارات متحده عربی صفآرایی کرده بود. زیردریاییهای ایرانی در دورترین نقاط ممکن گشت میزدند و پهپادهای شناسایی بیوقفه بر فراز آبها پرواز میکردند. در برابر، امارات با ناوگانی کوچکتر اما منظم، آرایش پلکانی خود را آراسته بود و با رنگ آمیزی استتاری…
به دلیل تنگنای وقتی تحلیل هاتون رو دادم هوش مصنوعی بزنه - اگه کسشری دیدین توش به کلفتی خودتون ببخشید باید یدونه اد تحلیل بگیرم
Showing the 12 most recent of 20 posts we hold for @PerzuraWar. 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,103,604 of 1,549,704entries 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“PerzuraWar | پرزورا وار” (@PerzuraWar), 20 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/PerzuraWar.
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.