This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
4 measurements spanning 6 days, net +65. 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 7,160–7,245 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 17:37
7,235
+64
9 Aug 2026, 15:15
7,171
+1
6 Aug 2026, 22:53
7,170
no change
6 Aug 2026, 11:02
7,170
first reading
Engagement
34 posts held, back to 30 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 10 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
19.8%
avg views ÷ 7,235 subscribers
Avg views / post
1,430
34 posts measured
Reaction rate
1.54%
reactions ÷ views · ER floor
Posts in window
34
of 34 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 11 August 2026
Posts held
34 (30 July 2026 – 11 August 2026)
Views total
48,643
Reactions total
748
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 02:18 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 57m
Average length
6m 12s
Measured directly from 19 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
748 reactions across 34 posts, in 5 distinct kinds. The most used accounts for 61.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
460
61.5%
👍
183
24.5%
🤩
45
6.02%
🔥
36
4.81%
👎
24
3.21%
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 34 of the 34 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 748reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 34 most recent posts we hold, published 30 July 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.
#ویژه_برنامه
🎥پیمان مکه؛ اتحاد عربستان و پاکستان هستهای علیه تهدیدهای جمهوری اسلامی و منطقهای؟
☢️ بررسی جایگاه قدرت هستهای پاکستان در معادلات بازدارندگی منطقه
🇺🇸 موضع ایالات متحده و دلایل سکوت واشنگتن در قبال این پیمان مستقل
🔺ياسين اهوازى | تحليلگر مسايل سياسى و امنيتى خاورميانه و جهان عرب
#اتحاد #عربستان
#پیمان_مکه
#جنگ #سپاه
آدرس کانال یوتیوب👇
http://www.youtube.c…
#ویژه_برنامه
🎥چرا پیمان مکه در شهر مکه و روز جمعه اعلام شد ؟
🕌 اهمیت نمادین انتخاب شهر مکه و روز جمعه برای اعلام رسمی پیمان
🌍 احتمال پیوستن مصر، اردن و سایر کشورهای مقتدر سنی به ائتلاف
🏗 ساختار عملیاتی، بودجه میلیاردی و تشکیل کمیتههای تخصصی در ریاض
🔺ياسين اهوازى | تحليلگر مسايل سياسى و امنيتى خاورميانه و جهان عرب
#اتحاد #عربستان
#پیمان_مکه
#جنگ #سپاه
آدرس کانال یوتیوب👇
ht…
🔵 آنهایی که فکر میکنند زمان شاه همه چیز گل و بلبل بود....
اظهارات هما ناطق استاد دانشگاه تهران را در خصوص دستگیری و شکنجه هایی که بر وی اعمال کردهاند را بشنوند...
اینها فقط گوشهای کوچک از نکبت حکومت پهلوی است که بر بیگناهان روا داشته شده...
#شاه #پهلوی
#رضا_پهلوی
#سلطنت_طلب
آدرس کانال یوتیوب👇
http://www.youtube.com/@seyedaqilhashemi
«اینستاگرام» | «تلگرام» | یوتیوب | «…
حکمت خواندن نماز نافله در خانه [به جای مسجد] چه میباشد؟
🔘 آن به اخلاص نزدیکتر است
🔘 و از ریا دورتر میباشد
🔘 خانه را به مانند قبرستان قرار نمیدهد [که در آن نمازی خوانده نمیشود]
🔘 و در خانواده، محبت به نماز ایجاد میکند
علامه ابن عثیمین رحمه الله
فتاوی نور علی الدرب ٢/٨ 📚
آدرس کانال یوتیوب👇
http://www.youtube.com/@seyedaqilhashemi
«اینستاگرام» | «تلگرام» | یوتیوب | «فی
#ویژه_برنامه
🎥 پیمان مکه؛ زنگ خطر برای ایران یا آغاز نظم جدید خاورمیانه؟
🔺ياسين اهوازى | تحليلگر مسايل سياسى و امنيتى خاورميانه و جهان عرب
#اتحاد #عربستان
#پیمان_مکه
#جنگ #سپاه
آدرس کانال یوتیوب👇
http://www.youtube.com/@seyedaqilhashemi
«اینستاگرام» | «تلگرام» | یوتیوب | «فیس بوک»
#پاسخ_به_شبهات
🔥 آخوندی که در مناظره بی آبرو شد!
🔺مناظره عالم وهابی و عالم رافضی در مورد افسانه شهادت حضرت فاطمه
#مناظره #طنز
#رسوایی #افشاگری
#حضرت_فاطمه #تاریخ
«اینستاگرام» | «تلگرام» | یوتیوب | «فیس بوک»
عبدالله بن عمر رضى الله عنهما مىگويد:
رسول الله ﷺ فرمودند:
↶ روز قيامت، الله بندهی مؤمن را نزد خود فرا میخواند و دربر میگيرد و به دور از انظار ديگران، به او میفرمايد:
◯ فلان گناه و فلان گناه را به ياد داری؟
بنده میگويد: بلی، ای پروردگار من!
و اينگونه الله از او، به گناهانش اعتراف میگيرد و بنده مؤمن، خود را در معرض هلاکت میبيند.
آنگاه، الله متعال میفرمايد:
◉ در دنيا گناهانت را پوشانيدم. امروز نيز آنها را…
رسول الله ﷺ فرمودند:
چشم زخم، حقيقت دارد.
اگر چيزی از سرنوشت، سبقت میگرفت، چشم زخم بود.
و اگر از شما درخواست کردند که اعضای بدنتان را بشوييد، اين کار را انجام دهيد.
صحیح مسلم: ٢١٨٨ 📚
■ در این حدیث رسول الله ﷺ بیان میدارد که چشم زخم حقیقت دارد،
یعنی: ایراد مصیبت در نتیجه چشم زخم چیزی ثابت و موجود است و چشم زخم آفتی است که در نتیجه نگاه عائن، انسان و حیوان را آسیب میزند و عائن شخصی است که با چشم خود آسیب می…
Showing the 12 most recent of 34 posts we hold for @seyedaqilhashemi. 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 — 118,413 of 1,481,217entries 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.
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 3 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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“سید عقیل هاشمی” (@seyedaqilhashemi), 7,235 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/seyedaqilhashemi.
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.