Channel
@akhbare_shora
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,777subscribers
-17 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001132154292 |
|---|---|
| Type | Channel |
| Username | @akhbare_shora |
| Description | ادمین @far_sheikh |
| Created | 22 May 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/akhbare_shora |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 00:32 | 6,777 | -7 |
| 8 Aug 2026, 23:01 | 6,784 | -10 |
| 6 Aug 2026, 03:18 | 6,794 | no change |
| 6 Aug 2026, 02:44 | 6,794 | first reading |
42 posts held, back to 5 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 pagesof Telegram’s post history, 20 posts per page.
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 6 of 42 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 42 (5 August 2026 – 11 August 2026) |
| Views total | 10,532 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 02: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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 9 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.
5 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 80.0% | |
| 😁 | 1 | 20.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 6 of the 42 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 42 most recent posts we hold, published 5 August 2026 to 11 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.
واگذاری ۵ هزار خانهریز در ۴ ساعت؛ رکورد فروش یا ابهام جدید در بازار مسکن؟ 🔹امروز فروش واحدهای خانهریز پروژه «فجر» در منطقه ۵ تهران، در سامانه شهرزاد کلید خورد و تنها در بازه زمانی ۴ ساعته (۱۰:۳۰ تا ۱۴:۳۰) به پایان رسید. آمار رسمی سامانه نشان از واگذاری ۶۱۲۶ واحد دارد. با توجه به این که طبق اعلام شهرداری ۱۱۲۶ واحد در گذشته واگذار شده بود، مشخص میشود که امروز ۵۰۰۰ واحد واگذار شد. 🔹اما سوال اینجاست: این خانهریزها …
😁1
Video, posted without a caption
شلیک مرگبار به قفسه سینه، گواهی فوت جعلی و زندگی با هویت قلابی/ پایان فرار مخوف شرور مسلح در عملیات مشترک پلیس معاون مبارزه با شرارت پلیس امنیت عمومی فراجا از دستگیری شرور مسلحی خبر داد که پس از شلیک به یک شهروند، با تهیه گواهی فوت جعلی تا مدتی با هویت جعلی در ایران زندگی میکرد اما سرانجام در عملیات مشترک پلیس امنیت عمومی و پلیس فتا دستگیر شد. سرهنگ سعید راستی معاون مبارزه با شرارت پلیس امنیت عمومی فراجا، از دستگی…
🔖 *یادداشت؛* 🔖 *از انتقال تجربه تا انتقال فرصت؛ حلقه مفقوده روابطعمومی ایران* ✍🏻 *محمدرضا پارسیان | کارشناس روابط عمومی* 💭 نزدیک به دو دهه فعالیت حرفهای در حوزه روابط عمومی، برای من صرفاً یک سابقه کاری نبوده است؛ مسیری بوده که در طول آن، از نزدیک با ظرفیتها، فرصتها، چالشها و کاستیهای این حرفه مواجه شدهام. 💭 سالها کار عملی، حضور در میدان ارتباطات، مواجهه با مدیران و سازمانها و رصد تحولات حرفه روابط عمومی، …
Photo, posted without a caption
📸💢توسعه زیرساخت شارژ پایتخت؛ بازدید میدانی مدیرعامل سازمان تاکسیرانی از ایستگاه شارژ برقی پایانه قیطریه 🚕 علی رحیمی، مدیرعامل سازمان مدیریت و نظارت بر تاکسیرانی شهرداری تهران، از ایستگاه شارژ برقی پایانه قیطریه که بهزودی به بهرهبرداری میرسد، بازدید کرد. 🚕 در این بازدید، رحیمی با اشاره به راهبرد توسعه ایستگاههای اختصاصی شارژ در پایانههای تاکسیرانی، سرعت بخشیدن به روند تجهیز این پایانهها را خواستار شد؛ رویکردی …
❤1
کارگاه آموزشی موبایلگرافی در باغ موزه مینیاتور منطقه۸ مدرس: سعید عرب پنجشنبه ۲۹ مرداد ۱۴۰۵ از ساعت ۱۶ تا ۲۰ آموزش اصول و تکنیکهای عکاسی با موبایل و تمرین عملی حضور برای علاقهمندان #رایگان است ثبتنام و اطلاعات بیشتر با شماره ۰۹۱۹۴۰۶۰۳۹۹ در پیامرسان بله #هشت_آنلاین #اطلاع_رسانی_منطقه۸
❤1
Photo, posted without a caption
*دیدار مردمی شهردار منطقه ۷ با هدف رسیدگی به مطالبات شهروندان * در ادامه ارتباط مستقیم مدیریت شهری منطقه ۷ با شهروندان، نشست ملاقات مردمی دکتر محمدهادی علیاحمدی، شهردار منطقه ۷ برگزار شد. در این دیدار، شهروندان مسائل، درخواستها و دغدغههای خود را مطرح کردند و موضوعات مطرحشده با حضور مدیران حوزه های مرتبط مورد بررسی و پیگیری قرار گرفت. به گزارش روابط عمومی شهرداری منطقه ۷، تداوم برنامه ملاقاتهای مردمی، فرصتی برا…
🔹 روایت ۵ سال خدمت و تلاش؛ ۳۶۵ هزار تن آسفالت برای نوسازی معابر منطقه ۲۱ از سال ۱۴۰۰ تا مرداد ۱۴۰۵، نهضت بهسازی معابر در منطقه ۲۱ پایتخت با شتابی بیسابقه دنبال شده است تا مسیری هموارتر و ایمنتر برای تردد شهروندان فراهم شود.
⭕️ تصویب طرح فشارافزایی میدان مشترک گازی پارس جنوبی 🟠 طرح راهبردی فشارافزایی میدان مشترک گازی پارس جنوبی با هدف حفظ ظرفیت تولید و افزایش برداشت گاز و میعانات گازی به تصویب شورای اقتصاد رسید؛ طرحی که اجرای آن نیازمند احداث مجموعهای از سکوهای تقویت فشار، تولید برق و تأسیسات دریایی مرتبط است.
📌 *شمارش معکوس برای گسترش «منطقه طبیعتگردی روددره فرحزاد» تا ۱۰۰ هکتار* ✅ آخرین جلسه هماهنگی پیش از افتتاح قطعه دوم پروژه «رود دره فرحزاد»، با حضور معاونین شهردار تهران برگزار شد. ✅ شهرداران مناطق ۲ و ۵ تهران نیز ضمن حضور در جلسه، گزارشی از آخرین وضعیت توافق و تعامل با اندک معارضین ملکی باقیمانده پروژه ارائه دادند. ✅ معاون خدمات شهری و محیط زیست شهرداری، اقدامات در حال انجام برای اتمام پروژه و تعهدات پیمانکار را…
Showing the 12 most recent of 42 posts we hold for @akhbare_shora. 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 — 289,848 of 1,350,102entries 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.
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.
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.
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.
“اخبار شورا” (@akhbare_shora), 6,777 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/akhbare_shora.
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.