Channel
@tarikhpersiann
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
202subscribers
+12 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003022862103 |
|---|---|
| Type | Channel |
| Username | @tarikhpersiann |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/tarikhpersiann |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 08:35 | 202 | +12 |
| 20 Aug 2026, 23:03 | 190 | -2 |
| 14 Aug 2026, 22:38 | 192 | +2 |
| 8 Aug 2026, 12:02 | 190 | no change |
| 8 Aug 2026, 03:17 | 190 | first reading |
13 posts held, back to 19 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 page of 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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 13 (19 July 2026 – 7 August 2026) |
| Views total | 71 |
| Reactions total | 13 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 12:02 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.
74 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 24.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 18 | 24.3% | |
| 💔 | 13 | 17.6% | |
| 😡 | 12 | 16.2% | |
| ❤ | 10 | 13.5% | |
| 😨 | 8 | 10.8% | |
| 😱 | 6 | 8.11% | |
| 🕊 | 3 | 4.05% | |
| 👏 | 2 | 2.70% | |
| 😐 | 1 | 1.35% | |
| 🤔 | 1 | 1.35% |
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 13 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 74 reactions 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 19 July 2026 to 7 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.
🗣 در دوره ضعف ایرانـی ها؛ روسـتاها و شـهرهای شمـالغـرب کشور جـولانگـاه عشیره های سُـنی کـرمانجزبان بود که از زیر قـوانین سـختگـیرانه عثمانی ها به آذربایـجان متـواری میشدند. گـوشهای از جنـایتها و مصـائبی که بر مردم محلی ایران وارد میکنند: سیمیتقوی کرمانج ساکنان شهر ساوجبولاق(مهاباد) را اعم از ترک و فارس و ارمنی؛ هم غارت میکرد و هم میکشت. تنها ارفاقی که به سوران زبان های ساوجبولاق(مهاباد) میکردن این بود که ایشان ر…
😡3😨3🤔1
🔴 عشـیرههای کُرمانج در اشغـال مهاباد چه بر سر اهالی ترکزبان و.. شهر آوردند؟! 💠 دوران قـتلعام گـسترده و وحـشتناک اهـالی سـاوجـبولاق آذربایجان(مهاباد امروزی) 📚 خاطرات یک مترجم ✍🏻 محمد قاضی 📖 صفحه ۴۵ 👨💻حمید #ساوجبولاق #مهاباد JOIN: @tarikhpersiann 📚💠
💔4😱2
💠خسرو و هراکلیوس؛ الگوی حکومت معاویه در خطابهٔ علی بن ابیطالب علی آشکارا تلاش داشت هرچه سریعتر لشکرکشی خود را آغاز کند، پیش از آنکه معاویه بتواند نیروهایش را گرد آورد. او به ابنعباس دستور داد که مردم بصره را بسیج کند. بنا بر گزارش ابومخنف، حدود ۱۵۰۰ نفر در ابتدا به آنان پیوستند و سپس احنف بن قیس نیز همراه آنان شد. پس از فراخوان دوم ابنعباس، ۱۷۰۰ نفر از مردم بصره در جربیه قَضّامه گرد آمدند. در کوفه گفته شده است که…
❤4👍2
Signed Navid Feshki
💠خسرو و هراکلیوس؛ الگوی حکومت معاویه در خطابهٔ علی بن ابیطالب 📌برای مشاهده ترجمه متن و مشخصات منبع کلیک کنید 👨💻Navid JOIN: @tarikhpersiann 📚💠
❤2👍1
Signed Navid Feshki
دوستان عـزیز، مقصود ما آگاهـی بخشی از واقـعیات و معلومات سـاده تاریخی است بدون کـم و کاسـتی. تـعریف و تمجـید فانـتزی یا برعکسش تخریـب مغرضانه از سرگـذشت و اعـمال قومیـت ها و حـکومت ها از افـکار «رادیـکالی» و «سـلیقهای» افـراد نشـات میگـیرد. #واقعیات #جعلیات 👨💻حمید JOIN: @tarikhpersiann 📚
👍6🕊3
کریمخان و علیمردانخان شهر را گرفتند و به غارت پرداختند. بقول مورخ رستمالاتواریخ سی چهلهزار بختیاری عور(پاپتی، لخت) خدانشناس مانند یاجوج و ماجوج داخل شهر اصفهان شدند و دست به تاراج گشودند. چنان غارتی از اصفهان کردند که درباره انان گفتند: تا به آب دیدهها بر خیک ها کردند پر تا به خشت خانهها کردند بر استران کردند بار زنان و دختران در مسجدها و امامزاده ها پناه بردند ، آن بیتمیزان بیدیانت در آن اماکن مشرفه از خدا …
😨5😡2
Signed hamid
🖋 اقدامات و ایرانمداری «کریمخان زند» ⚜️ قتل و تجاوز وحشیانه و مرگآور به دختران و زنان اصفهانی توسط بختیاری ها و زند ها 📚 کریمخان زند ✍🏻 دکتر عبدالحسین نوائی 📖 صفحه ۴۱ 👨💻حمید #کریمخان #بختیاری #زند #اصفهان JOIN: @tarikhpersiann 📚💠
😡7💔5
Signed hamid
سلام نوید هستم مالک کانال و مخلص شما مدتی هست که بنا به دلایلی فعالیت رو کنار گذاشتم بزودی پس از فارغ شدن، دوباره فعالیت رو ادامه میدم، شما فعلا میتونید از مطالب سابق کانال استفاده کنید که پر شمارند تاریخ بخوانید تا آگاه شوید چاکر شما نوید
👍5❤2
Signed Navid Feshki
فوجی از افغان و فوجی از گبرهای(زرتشتی) کرمان به سرداری نصرالله خان کرمانی و امارت زبردست خان قندهاری برای تسخیر فارس و تدمیر اهل شیراز انفاذ داشت تفنگچیان سمغان کازرون و بلوک خنج و پشور لارستان که با افاغنه دعوی اتحاد مذهب داشتند به مدد سپاه گبر و افغان آمده و شیراز را در مدت نهماه محاصره نمودند از شیرازیان جلادت و دلاوری فوقالعاده بروز نمود. شهر شیراز را به قهر و غلبه گرفتند و پیش از فتح و بعد از فتح نزدیک به صدهز…
😱4😐1
Signed hamid
📌 روزگار بسیار تلخ و هولناک ایرانیان ⚜️ قتلعام مردم شیراز بدست زرتشتی ها و لار ها مقاومت جسورانه اهالی شهر بمدت ۹ ماه 📚 فارسنامه ✍🏻 فسائی 📖 صفحه ۵۰۲ جلد ۱ 👨💻حمید #زرتشتی #گبر #لار JOIN: @tarikhpersiann 📚💠
💔4
Signed hamid
«آغا محمد یحییخان افشار» سه سال بعد در پی کنارهگیری ایوبخان، زمام امور پاکستان را در دست گرفت. دوران حکومت او با رویدادهایی سرنوشتساز همراه بود؛ از برگزاری نخستین انتخابات سراسری پاکستان تا بحران سیاسی پاکستان شرقی و جنگ ۱۹۷۱ که به جدایی بنگلادش انجامید. این تحولات سرانجام به پایان حکومت وی و کنارهگیریاش از قدرت منجر شد. یحییخان پس از آن از صحنه سیاسی کنار رفت و سالهای پایانی عمر را در انزوا گذراند. با وجود د…
👍2❤1
Signed hamid
💠 سومین «رئیسجمهور پاکستان» 📸 آغا محمد یحییخان افشار قزلباش (۱۹۱۷–۱۹۸۰) از برجستهترین نظامیان و سیاستمداران پاکستان و سومین رئیسجمهور این کشور بود. او پس از تحصیل در آکادمی نظامی راج بریتانیا، در جنگ جهانی دوم خدمت کرد و پس از استقلال پاکستان، به سرعت در سلسلهمراتب ارتش ارتقا یافت. یحییخان در سال ۱۹۶۶ به فرماندهی ارتش پاکستان رسید... 👨💻حمید #افشارها JOIN: @tarikhpersiann 📚💠
👏2
Signed hamid
Showing the 12 most recent of 13 posts we hold for @tarikhpersiann. 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 — 1,173,893 of 1,629,452 entries 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 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“🏛ناگفته هایی از تاریخ ایران🏛” (@tarikhpersiann), 202 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/tarikhpersiann.
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.