International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 54% 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
34 measurements spanning 55 days, net -4,075. 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 131,596–136,934 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)
Subscribers
Change
30 Sept 2026, 20:00
132,243
+31
18 Sept 2026, 04:57
132,212
-226
16 Sept 2026, 01:00
132,438
-250
14 Sept 2026, 04:38
132,688
-173
12 Sept 2026, 13:38
132,861
-144
10 Sept 2026, 14:59
133,005
-286
7 Sept 2026, 10:39
133,291
-131
4 Sept 2026, 12:38
133,422
+96
2 Sept 2026, 23:08
133,326
+478
1 Sept 2026, 20:35
132,848
-39
1 Sept 2026, 00:06
132,887
-94
31 Aug 2026, 02:45
132,981
-130
29 Aug 2026, 23:34
133,111
-154
28 Aug 2026, 21:32
133,265
-111
27 Aug 2026, 20:54
133,376
-115
26 Aug 2026, 22:23
133,491
-132
26 Aug 2026, 01:34
133,623
-115
25 Aug 2026, 00:46
133,738
-175
23 Aug 2026, 14:34
133,913
-169
21 Aug 2026, 22:08
134,082
first reading
Engagement
163 posts held, back to 29 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 113 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
58.6%
avg views ÷ 132,243 subscribers
Avg views / post
77,600
102 posts measured
Reaction rate
3.30%
reactions ÷ views · ER floor
Posts in window
102
of 163 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 30 September 2026
Posts held
163 (29 July 2026 – 30 September 2026)
Views total
7,910,460
Reactions total
261,073
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
30 Sept 2026, 10:00 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
19m 07s
Average length
38s
Measured directly from 30 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
422,422 reactions across 163 posts, in 72 distinct kinds. The most used accounts for 34.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
143,787
34.0%
🤣
79,915
18.9%
👍
76,500
18.1%
🔥
32,258
7.64%
👏
19,729
4.67%
😁
19,221
4.55%
💩
15,928
3.77%
🤮
4,039
0.956%
💔
2,780
0.658%
🥱
2,631
0.623%
🎉
2,609
0.618%
😐
2,574
0.609%
😱
2,551
0.604%
🤬
2,359
0.558%
👌
2,029
0.48%
🖕
1,357
0.321%
🍾
1,227
0.29%
🤯
1,184
0.28%
😢
917
0.217%
👎
694
0.164%
52 further kinds
8,133
1.93%
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 163 of the 163 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 422,422 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 163 most recent posts we hold, published 29 July 2026 to 30 September 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.
مهم/
تقریبا محرز شده حادثه تروریستی بوده:
مقامات اسرائیلی بعد از تحقیقات اولیه و شهادت مسافرها، الان حادثه پرواز «فلایدوبای» رو بهعنوان یک 'حمله تروریستی' بررسی میکنن.
گفته میشه کمکخلبان چند بار با چاقو به کاپیتان حمله کرده، تا اینکه اعضای خدمه و مسافرها به زور وارد کابین شدن و مهارش کردن.
کانال ۱۲ اسرائیل به نقل از شاهدها گزارش داده که هنگام حادثه صدای «اللهاکبر» شنیده شده.
@pouriazeraati
مهم/
منابع اسرائیلی گزارش دادن سرویسهای امنیتی اسرائیل احتمال تروریستی بودن حادثهی پرواز «فلایدوبای» رو نادیده نگرفتن.
کمکخلبان در حال حاضر داره بازجویی میشه و تا اینجا مشخص شده قصد داشته 'به زور کنترل هواپیما رو از خلبان بگیره و ساقطش کنه.'
@pouriazeraati
نشونههای افزایش تنش در آینده نزدیک [احتمالا بعد انتخابات آمریکا]:
بیبی نتانیاهو در دیدار با محمد بنزاید در امارات، اطلاعات تازهای از سرویسهای اطلاعاتی اسرائیل رو با بنزاید در میون گذاشته که نشون میده جمهوری اسلامی دوباره داره برنامه هستهایش رو گسترش میده؛ از جمله ساختوسازهای جدید در سایت کوه کلنگ.
نتانیاهو در این جلسه گفته ارزیابی اسرائیل اینه که جمهوری اسلامی ممکنه «طی هفتههای آینده» دست به حمله بزنه.
…
اسرائیل تأیید کرد به احتمال بالا یکی از خلبانهای سعی کرده هواپیما رو ساقط کنه و همه مسافرها رو بکشه.
بیبی نتانیاهو تصمیم گرفته هواپیماهای نظامی به عربستان بفرسته تا اسرائیلیها رو برگردونن خونه.
@pouriazeraati
فاک!
ظاهرا داستان فراتر از دعوای معمولی بین دو خلبان بوده:
الان جمعبندی کلی اینه که یکی از خلبانها قصد خودکشی داشته و سعی کرده با شیرجه دادن هواپیما، اون رو ساقط کنه. بعد خلبان دوم برای جلوگیری از این کار، خلبان اول رو با چاقو زده.
چند مسافر اسرائیلی هم وارد ماجرا شدن و کمک کردن جلوی سقوط هواپیما گرفته بشه.
تو این عکس یکی از مسافرهای پرواز «فلایدوبای» از مبدأ دوبی به تلآویو دیده میشه که دخالت کرده؛ روی پیراهن…
خاک بر سر خلبان و کمک خلبان:
اولش که خبر اومد بیرون فاز اینو میداد که یه طرح هواپیمارباییه.
پرواز شماره ۱۰۷۳ فلایدوبای از مبدأ دوبی به تلآویو حدود یه ساعت پیش زمانی که در آسمان شمال عربستان بود، کد رهگیری اورژانسی مربوط به هواپیماربایی ارسال کرد.
حدود صد شهروند اسرائیلی در این پرواز بودن.
یه مدتی از هواپیما خبری نبود اما خوشبختانه دقایق پیش اعلام شد که داره در یکی از فرودگاههای عربستان میشینه.
دلیلش فکر می…
گزارشهایی که میگن چند کشور غربی پیامهای فوری صادر کردن و از شهروندهاشون خواستن فوراً ایران رو ترک کنن، درست نیست.
هیچکدوم از سفارتخونههای فرانسه، بریتانیا، ایتالیا، آلمان یا دیگر کشورهای اروپایی هشدار جدیدی صادر نکردن.
هشدارها درباره سفر نکردن به ایران یا توصیه به شهروندها برای ترک کشور، همونهاییه که از ماهها قبل وجود داشته و امروز هیچ هشدار تازهای منتشر نشده.
@pouriazeraati
مهم/
یک مقام اطلاعاتی آمریکا گفته واشنگتن با ارزیابی بیبی نتانیاهو موافقه که نشونههایی از احتمال حمله به اسرائیل در آستانه انتخابات پیش رو وجود داره.
@pouriazeraati
بیبی نتانیاهو:
'نشونههایی وجود داره که دشمنان ما ممکنه در آستانه انتخابات سعی کنن به ما حمله کنن.
با ما درنیفتید. دست بلند ما هر جا و هر زمانی که باشید بهتون میرسه.' :)
بهبه، داره جالب میشه …
@pouriazeraati
خودش هم گند زد به هیکل عراقچی :))
ترامپ:
'آکسیوس همین الان گزارشی منتشر کرده و گفته ترامپ به جمهوری اسلامی پیشنهاد کاهش تحریمها و آزاد کردن پولهای بلوکهشده رو داده. این اصلاً حقیقت نداره. من هیچ چیزی بهشون پیشنهاد ندادم!
گزارش آکسیوس، مثل بیشتر گزارشهاشون، یک داستان ساختگیه که فقط برای ارضای «سندروم ترامپزدگی»شون منتشر شده. باید فوراً این گزارش جعلی رو پس بگیرن!'
@pouriazeraati
رسانههای نزدیک به دموکراتها و برخی مطبوعات عرب طبق معمول نوشتن رژیم با توقف غنیسازی موافقت کرده.
جمهوری اسلامی بلافاصله تکذیب کرد.
مجتبی کوتاه نخواهد اومد :)
@pouriazeraati
یک دلار آمریکا:
دو میلیون و چهارصدوپنجاه هزار ریال.
خاک بر سرت عرزشی!
@pouriazeraati
👍2,560🤬408💔153💩98😁86😢64❤54😱37
Showing the 12 most recent of 163 posts we hold for @pouriazeraati. 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.
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.
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 30 September 2026 — this
entry's latest reading, not the date you are reading this.
“پوریا زراعتی Pouria Zeraati” (@pouriazeraati), 132,243 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/pouriazeraati.
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.