زندگی و جهانداری کوروش بخش پنجم 🏛️ کورش بزرگ و گشایش بابل-قسمت یکم 🌙 ۱. برآمدن نبونئید و دگرگونی آیین بابل نبونئید واپسین پادشاه بابل نو پیش از چیرگی ایرانیان بر بابل بود. او از خاندان شاهی نبود و پس از کشتهشدن لاباشیمردوک، شاه خردسال بابل، در پی یک گریسهبازی(توطئه) به تخت نشست. از تبار و خاندان او آگاهی چندانی نداریم؛ تنها روشن است که مادرش پریستار(کاهنهٔ) بزرگ پرستشگاه سین، ایزد ماه، در حَرّان بود. نبونئید ن…

Channel
کانال تاریخ ایران
@Persian_History_Archive
On this record: Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
215subscribers
+3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003922980134 |
|---|---|
| Type | Channel |
| Username | @Persian_History_Archive |
| Created | Between 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/Persian_History_Archive |
Also posting the same content
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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 14:53 | 215 | +3 |
| 7 Aug 2026, 03:32 | 212 | no change |
| 6 Aug 2026, 19:46 | 212 | first reading |
Engagement
19 posts held, back to 2 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 84.8%
- avg views ÷ 215 subscribers
- Avg views / post
- 182
- 17 posts measured
- Reaction rate
- 1.25%
- reactions ÷ views · ER floor
- Posts in window
- 19
- of 19 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. It is computed over the 9 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 19 (2 August 2026 – 6 August 2026) |
| Views total | 3,100 |
| Reactions total | 28 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 03:32 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
28 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 35.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 10 | 35.7% | |
| ❤ | 9 | 32.1% | |
| 👏 | 5 | 17.9% | |
| 👍 | 2 | 7.14% | |
| ❤🔥 | 1 | 3.57% | |
| 👎 | 1 | 3.57% |
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 9 of the 19 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 28reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 2 August 2026 to 6 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.
Recent posts
کوروش و گشایش بابل- قسمت دوم ⚔️ ۴. چرا کورش به بابل لشکر کشید؟ پس از چیرگی کورش بر سرزمینهای ماد، لیدی و سپس بخشهای خاوری ایرانشهر، راه او به سوی میانرودان باز شد. دربارهٔ انگیزهٔ درست لشکرکشی به بابل نمیتوان با دلاستواری یک بهانهی یگانه برگزید. شاید پیوند بابل با دشمنان کورش و پشتیبانی آن از کرزوس، پادشاه لیدی، یکی از زمینههای دشمنی بوده باشد؛ ولی گواه روشنی برای یک یاریرسانی جنگی بزرگ از سوی بابل به لیدی …
🔹️کوروش و گشایش بابل-قسمت سوم 🌿 ۸. آمدن کورش به بابل کورش هفده روز پس از گشایش شهر، در ۲۹ اکتبر ۵۳۹ پیش از میلاد، خود درون بابل شد. گزارش سالنامهٔ نبونئید از این آمداری چهرهای آرام پیش می آورد: راه پیش روی کورش با شاخههای نی آراسته شد و شهر در آرامش بود. کورش نیز برای سراسر سرزمین بابل آشتی آورد. این نکته بسیار پرارج است؛ زیرا بابل یکی از بزرگترین کانونهای شهرآیینی جهان باستان بود و اگر کورش آن را با ویرانی گست…
🔹️کوروش و گشایش بابل-قسمت چهارم 🌍 ۱۲. پیدایش شاهنشاهی چند نفانه(ملته) با گشایش بابل، گسترهٔ فرمانروایی کورش به اندازهای رسید که از بسیاری از فرمانرواییهای پیشین جهان باستان بزرگتر بود. در این شاهنشاهی، تنها یک زانیچ(قوم) فرمان نمیراند؛ پارسیان، مادها، بابلیان، آشوریان، مردمان سامی، تورانیان، یونانیان و دیگر مردمان در کنار یکدیگر در چارچوب فرمانروایی هخامنشی گنجیدند. این ویژگی یکی از دگرگونیهای بزرگ روزگار کورش…
جدیدا چقدر تاریخدان زیاد شده 😂 میگم یه سوال ایلامی ها و کاسی ها آریایی نبودن ولی هخامنشیان بودن مگه میشه هردوتاشون لر باشن البته بنده در جایگاهی نیستم که نظر بدم 😂
🤣5
ایران؛ نامی به درازای تاریخ آیا ایران فقط ۸۷ سال قدمت دارد؟! 🔻 قسمت ششم و پایانی در قسمت پنجم دیدیم که حتی فاتحان مغول و ترکمان آققویونلو مجبور شدند نام «ایران» را بپذیرند. حالا میرسیم به اوج ماجرا: احیای کامل و یکپارچه پادشاهی ایران توسط صفویان، و در نهایت، حقیقت اقدام رضاشاه در سال ۱۳۱۳. ━━━━━━━━━━━━━━━ 📍 ۱. صفویه؛ تجدید پادشاهی مستقل و یکپارچه «ایران» شاه اسماعیل صفوی در سال ۹۰۷ هجری (۱۵۰۱ میلادی) در تبریز تاجگ…
👏1
━━━━━━━━━━━━━━━ 📍 ۵. اقدام تاریخی رضاشاه در سال ۱۳۱۳ (۱۹۳۵ میلادی)؛ اصلاح، نه اختراع حالا میرسیم به اصل ماجرا! اگر نام ایران از ۳۰۰۰ سال پیش وجود داشت، پس رضاشاه در سال ۱۳۱۳ دقیقاً چه کاری انجام داد؟ همانطور که در پنج قسمت قبل با دهها سند دیدیم، ما ایرانیها از عصر ساسانی تا قاجار همیشه به کشورمان «ایران» میگفتیم. اما غربیها به دلیل سنت بهجامانده از یونان باستان، در مکاتبات دیپلماتیک از واژه «Persia» استفاده می…
👏1
دهنم سرویس شده ریشه نام ایرانو از اغاز تا پایان توضیح بدم جناب پانترک آمده میگه ایران ترکیه🤣 ای خدا مارو عذاب نده
🤣5
🔹️اهمیت تاریخ و فرهنگ و زبان از دهان استاد فرزانه و بیداردل اقای جلال الدین کزازی @IranGrad تاریخ چراغ راه آیندهاست @Persian_History_Archive
🏹 گشودن ایران خاوری به دست کوروش بزرگ-به قلم شروین وکیلی پس از گشودن سارد، کوروش بیدرنگ روی به سوی ایران خاوری نهاد. این شتاب در لشکرکشی شگفت مینماید؛ زیرا او پس از دو نبرد سنگین با ماد و لودیه میتوانست به آسودن و بازسازی سپاه بپردازد. ازاینرو، انگیزهٔ این لشکرکشی را میتوان سرکشی سرزمینهایی دانست که پیشتر فرمانبردار ماد بودند و پس از برافتادن ماد، خود را از بند فرمان تازه رهاشده میدیدند. 📜یوستینوس، آریان، ه…
🔹️ایران و ایرانشهر به قلم ژاله آموزگار بخش دوم 💥دگرگونی زمین در افسانه آفرینش به باور متن های پهلوی که آزند(تفسیر) اوستایند، آفرینش دوازده هزار ساله است. در سههزارسالهی سوم، اهریمن بر زمین یورش آورد. زمین لرزید، کوهها پدید آمدند، رودها و دریاها روان شدند و هفت کشور ساخته شد. بهترین آنها «خونیرس» است و ایرانویج در دل آن جای دارد، با آبهای فراوان و رستنیهای آرمانی کوچ مادها و پارسها در هزاره نخست پیش از میل…
❤3
ایران؛ نامی به درازای تاریخ آیا ایران فقط ۸۷ سال قدمت دارد؟! 🔻 قسمت پنجم در قسمت چهارم دیدیم که غزنویان، سلجوقیان و خوارزمشاهیان، با اینکه تبار ترکی داشتند، خودشان را وارث «ایرانزمین» میدانستند. حالا میرسیم به یکی از تلخترین و در عین حال شگفتانگیزترین فصلهای این ماجرا: حمله مغول. ━━━━━━━━━━━━━━━ 📍 ۱. حمله مغول و دوره ایلخانان؛ تولد دوباره «کشور ایران» در سیاست چنگیزخان ابتدا تمام شرق و مرکز ایران را ویران کرد، …
Showing the 12 most recent of 19 posts we hold for @Persian_History_Archive. 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 — 28,286 of 1,478,351entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“کانال تاریخ ایران” (@Persian_History_Archive), 215 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Persian_History_Archive.
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.