Telegram RegisterThe public register of Telegram
Telegram profile photo for تاریخ اشکانیان | Aškānān gāhnāmag

Channel

تاریخ اشکانیان | Aškānān gāhnāmag

@Arsacid_Chronicle

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

6,104subscribers

+350 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001513895754
TypeChannel
Username@Arsacid_Chronicle
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/Arsacid_Chronicle

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Arsacid_Chronicle/9684 · this entry4 Aug 2026, 05:04 UTC@Parthian_Zoroastrianism/13744 Aug 2026, 08:36 UTC1.003.5 hours
@Arsacid_Chronicle/9685 · this entry4 Aug 2026, 09:52 UTC@Parthian_Zoroastrianism/13754 Aug 2026, 09:57 UTC1.005 minutes
@Parthian_Zoroastrianism/13765 Aug 2026, 06:49 UTC@Arsacid_Chronicle/9692 · this entry5 Aug 2026, 06:49 UTC1.00under a minute
@Arsacid_Chronicle/9705 · this entry7 Aug 2026, 08:40 UTC@Parthian_Zoroastrianism/13777 Aug 2026, 10:54 UTC1.002.2 hours
@Arsacid_Chronicle/9707 · this entry7 Aug 2026, 10:11 UTC@Parthian_Zoroastrianism/13797 Aug 2026, 10:54 UTC1.0043 minutes
@Arsacid_Chronicle/9708 · this entry7 Aug 2026, 15:27 UTC@Parthian_Zoroastrianism/13807 Aug 2026, 15:28 UTC1.002 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@Parthian_Zoroastrianism9 (8/8 hand-verifiable sample passed)1.0081 minutesthis entry (8–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 47 comparable posts for this entry, running 4 August 2026 to 5 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @Arsacid_Chronicle — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

5,7536,1045,928.56 August 2026 — 5,754 subscribers7 August 2026 — 5,753 subscribers10 August 2026 — 5,767 subscribers13 August 2026 — 5,763 subscribers16 August 2026 — 5,790 subscribers19 August 2026 — 5,788 subscribers23 August 2026 — 5,802 subscribers26 August 2026 — 5,806 subscribers29 August 2026 — 5,823 subscribers1 September 2026 — 5,842 subscribers5 September 2026 — 5,863 subscribers10 September 2026 — 5,878 subscribers13 September 2026 — 5,885 subscribers18 September 2026 — 5,899 subscribers27 September 2026 — 5,933 subscribers5 October 2026 — 5,945 subscribers12 October 2026 — 5,978 subscribers15 October 2026 — 5,990 subscribers18 October 2026 — 5,987 subscribers22 October 2026 — 6,004 subscribers25 October 2026 — 6,010 subscribers28 October 2026 — 6,026 subscribers31 October 2026 — 6,035 subscribers3 November 2026 — 6,043 subscribers5 November 2026 — 6,049 subscribers9 November 2026 — 6,066 subscribers14 November 2026 — 6,104 subscribers6 August 202614 November 2026
27 measurements spanning 100 days, net +350. 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 5,700–6,157 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
14 Nov 2026, 16:556,104+38
9 Nov 2026, 14:056,066+17
5 Nov 2026, 21:476,049+6
3 Nov 2026, 05:406,043+8
31 Oct 2026, 08:106,035+9
28 Oct 2026, 07:156,026+16
25 Oct 2026, 11:486,010+6
22 Oct 2026, 01:076,004+17
18 Oct 2026, 09:265,987-3
15 Oct 2026, 11:315,990+12
12 Oct 2026, 11:165,978+33
5 Oct 2026, 12:375,945+12
27 Sept 2026, 18:355,933+34
18 Sept 2026, 03:215,899+14
13 Sept 2026, 20:015,885+7
10 Sept 2026, 11:195,878+15
5 Sept 2026, 03:175,863+21
1 Sept 2026, 13:295,842+19
29 Aug 2026, 19:075,823+17
26 Aug 2026, 12:125,806first reading

Engagement

48 posts held, back to 4 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 12 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.5%
avg views ÷ 6,104 subscribers
Avg views / post
640
14 posts measured
Reaction rate
2.74%
reactions ÷ views · ER floor
Posts in window
14
of 48 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
WindowRolling 30 days · latest post in window 5 November 2026
Posts held48 (4 August 2026 – 5 November 2026)
Views total8,956
Reactions total245
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 17: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.

Reaction mix

680 reactions across 47 posts, in 5 distinct kinds. The most used accounts for 66.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤45466.8%
👍18427.1%
🔥202.94%
👌172.50%
👏50.735%

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 47 of the 48 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 680 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 48 most recent posts we hold, published 4 August 2026 to 5 November 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

Telegram’s own ‘edited’ marker: 2 of 14 posts held from the last 30 days (14.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 08:40 UTC320 views13 reactionsread 5 November 2026

بنابراین، احتمالاً این خانواده‌ها برای تامین هزینه‌ های زندگی خود به منابع درآمدی دیگری نیز وابسته بودند. این موضوع با یادداشتی در بایگانی اسناد نیز تایید می‌شود که طبق این یادداشت، نانوایی به نام مردو-شوما-ایدین علاوه بر فعالیت خود به‌عنوان نانوا، مسئولیت اداره و مدیریت درآمدهای معبد را نیز بر عهده داشته و در ازای انجام این وظیفه، پول دریافت می‌کرده است. بر اساس پوست نوشته هایی که در اورامان نیز کشف شده‌اند، در سا…

❤7👍6

5 Nov 2026, 08:35 UTC327 views11 reactionsread 5 November 2026
Photo

داده هایی از زندگی معمول در عصر اشکانی اسناد اداری، منبع مهمی برای آگاهی ما از زندگی روزانه مردم در بابل در عصر اشکانی است. این اسناد اطلاعاتی درباره امور معابد ،اجرای آیین ها ، بهای کالا و خدمات به دست میدهد و در عین حال اشاراتی در زمینه وضعیت سیاسی نیز دربر دارد. در اینجا به چند نمونه از قیمت اقلام، پرداخت حقوق و درآمد اشاره خواهد شد؛ با توجه به لوح های گلی که در پیوند با سال ۹۳-۹۴ پیش از میلاد هستند میدانیم مرد…

❤7👍4

2 Nov 2026, 09:35 UTC849 views21 reactionsread 5 November 2026

نماد بالدار هخامنشی: اهوره‌مزدا، خورنه یا هردو؟ قرص/حلقهٔ بالدار همراه با نیم‌تنهٔ انسان‌نما در کنارِ قرص/حلقهٔ بالدارِ فاقد نیم‌تنه و نیز نیم‌تنهٔ انسان‌نما درون هلال یا دایره (بدون بال) وجود دارد (و گاه حتی به‌معنای واقعی کلمه، در کنار آنها دیده می‌شود). هرگونه تفسیر از نخستینِ این سه گونه، در نهایت باید در پرتوِ دو گونهٔ دیگر و نیز بر پایهٔ درکی کامل از نحوِ شمایل‌نگارانهٔ کاربردهای گوناگون آنها ــ که هنوز حاصل ن…

❤16👍5

2 Nov 2026, 09:34 UTC555 views11 reactionsread 5 November 2026

پویایی دین زرتشتی در جهان باستان و تعامل آن با فرهنگ‌های دیگر برخی تلاش کردند این مکان‌ها را به عنوان تجلیات زرتشتی‌گری یا بازمانده‌ای از یک سنت معماری ناشناخته هخامنشی یا زرتشتی تفسیر کنند یا آنها را به این دلیل که انتظار نابهنگام آنها مبنی بر مطابقت با زرتشتی‌گری «ارتدوکس» را برآورده نمی‌کردند، رد کردند. فقدان شواهد معماری رسمی زرتشتی هخامنشی بسیاری از این رویکردها را ناامید کرد. در اینجا من به جای استدلال برای هر…

❤8👍3

1 Nov 2026, 13:11 UTC676 views22 reactionsread 5 November 2026
Photo

🪙ضرب چهره فرهاد چهارم بر روی سکه های مارک آنتونی در سال ۳۳ ق.م مارک آنتونی یورش نهایی خود را در برابر فرهاد چهارم آغاز کرد و تا رود ارس پیشروی کرد، اما فراتر از آن نرفت. سپس برای مقابله با خطر اوکتاوین (آگوستوس) رقیب رومی خود بازگشت تا تدارک جنگ ببیند، در غیاب او اشکانیان هر دو ساتراپی ماد و ارمنستان را بازپس گرفتند و پادگان رومی مستقر شده را معدوم ساختند؛ احتمالا در این نقطه از زمان بود که فرهاد به عنوان غنیمت جنگ…

❤20👍2

31 Oct 2026, 17:48 UTC682 views28 reactionsread 5 November 2026
Photo

مسئلهٔ واژگان پارس، پارسوا، پارسواش، پارسوماش و پارت قوم‌نام پارس (فارسی باستان: pārsa) در منابع آشوری به اشکال گوناگونی نظیر: parsûa, parsûaš, parsûmaš (parsuwash, parsumash) دیده می‌شود که همگی به فرم ایرانی باستانِ *parsava یا *pārsava (*pārćwa) بازمی‌گردند (نیز v/w به m تبدیل میشود)، و با واژهٔ parϑava (قوم‌نام پارت) نیز همریشه‌اند. ‌ Skjærvø, P. O. (2006). IRAN vi. IRANIAN LANGUAGES AND SCRIPTS (1) Earliest Evi…

❤24👍4

30 Oct 2026, 20:25 UTC623 views16 reactionsread 5 November 2026

محققانی مانند دیرون تاکید می‌کنند که این مجسمه‌ها پیوند قدرت سیاسی و مذهبی را نشان می‌دهند: پادشاه به‌عنوان واسطه بین مردم و خدایان، با تاثیر ایدئولوژی سلطنتی اشکانی (مانند «فر»). در حدود سال ۱۷۰، سیناتروک، نخستین پادشاه هترا، ساختمانی مربع شکل در پشت ایوان بزرگ جنوبی در تمنوس مرکزی ساخت (ساختمان مربعی شماره چهار در عکس بالا). از دیدگاه معماری، این بنا یک نمونه‌ی غیر عادی در معماری مذهبی هترا است. با توجه به شباهت‌ه…

👍10❤5🔥1

30 Oct 2026, 20:24 UTC635 views19 reactionsread 5 November 2026
Photo

سیناتروک اول پادشاه هترا: سیناتروک اول یکی از حاکمان مهم هترا در شمال میان‌رودان بود که حدود ۱۴۰ تا ۱۸۰ میلادی حکومت کرد. حاکمان پیش از او عنوان «مریا» marya) داشتند که به‌ معنای «سرور»، «حاکم» بوده است. پدرش نصرو نیز فقط همین عنوان را داشت. سیناتروک اول (و برادرش بلاش) از جمله نخستین کسانی بودند که عنوان رسمی «ملک» (پادشاه) را به کار بردند. عنوان پادشاهی احتمالا از سوی پادشاه اشکانی بلاش چهارم به او اعطا شد، چ…

❤10👍9

29 Oct 2026, 22:27 UTC525 views16 reactionsread 5 November 2026

در واقع ممکن است موزدواُنو نیای تقدیس‌شدهٔ دودمان کوشانی بوده باشد که پس از تسلط کوشانیان بر سرزمین‌هایی با جمعیت قابل‌توجه هندی و تحت تأثیر عمیق سنت‌های دینی هندو، با یکی از شخصیت‌های ایزد شیوه درآمیخته شده است. پرستش نیاکانِ ایزدی‌شده در میان سکاها، پارتیان و دیگر کوچ‌نشینان ایرانی‌تبار گواهی شده است. بنابراین، منطقی است فرض کنیم که برخی بازتاب‌های این سنت در دوران شکوه امپراتوری کوشانیان نیز حفظ شده بوده است. جزئی…

❤16

29 Oct 2026, 22:23 UTC569 views12 reactionsread 5 November 2026

💠موزدواُنو (Mozdooano) ایزدی با نام موزدواُنو (MOΖΔΟΟΑΝΟ) بر روی شماری از سکه‌های طلای کمیاب کانیشکا دیده می‌شود. او به شکل مردی ریش‌دار به تصویر کشیده شده که از نظر پوشش و ظاهر شباهت زیادی به پادشاه کوشانی دارد (لوح ۱۴). موزدواُنو کلاه سلطنتی کوشانی را بر سر دارد که با دیهیم بسته شده است. او مسلح به شمشیر است و نیزه‌ای سه‌شاخه در دست دارد و بر اسبی دو سر سوار است. نام او در هیچ‌یک از متون زرتشتی شناخته‌شده نیست و ا…

❤11👍1

29 Oct 2026, 18:10 UTC564 views13 reactionsread 5 November 2026
Photo

واژهٔ frataraka در اصل باید به معنای «پیشرو» یا «برتر» باشد و در نتیجه تقریباً معادل «حاکم» یا «فرماندار» است (نک. براندنشتاین و مایرهوفر، ۱۹۶۴، ص. ۱۱۹)؛ البته در مواردی که این عنوان بر روی این سکه‌ها دیده می‌شود. این تفسیر را شروو (۱۹۹۷، ص. ۱۰۲) بار دیگر مورد تردید قرار داده است. دربارهٔ املای این واژه نیز باید توجه داشت که خوانش pltlk’، چنان‌که بر روی سکه‌ها گواهی شده است، با الف پایانی، نمی‌تواند با واژهٔ fratara…

❤8👍5

27 Oct 2026, 17:59 UTC953 views27 reactionsread 5 November 2026
Photo

نگاهی به ميتراى رومی کتاب «نگاه غربی به میترای رومی» منتشر شد نقل‌قولی از تورج دریایی درمورد این کتاب: سال هاست كه لازم بود يک محقق تاريخ اديان درباره نقش مهر / ميترا كار جديدى انجام دهد. دكتر نينا ماژجو سعى كرده با مطالعه ايزد مهر / ميترا در دنياى هند و ايرانى و سپس قفقاز و آسياى صغير و پس از آن در روم نگاهى بهتر و درست تر به اين خداى بزرگ جهان باستان داشته باشد. براى اينكار نه تنها بايد تاريخ اديان دانست بلكه كم…

❤19👍8

Showing the 12 most recent of 48 posts we hold for @Arsacid_Chronicle. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

11 Aug 2026, 16:25 UTCAnonymous Poll94 voters

آیا از روند علمی کانال راضی هستید؟ (پیشنهاد خود را حتما در کامنت ها مطرح کنید)

  1. بله86%
  2. خیر10%
  3. در نظرات اعلام خواهم کرد4%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 48 most recent posts we hold, published 4 August 2026 to 5 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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 4 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

تاریخ ما
@Tarikhema · 22,687
Telegram ranks this channel #1 of 74 here — alongside 73 others — read 19 September 2026
تاریخ ۷۰۰۰ ساله ایران
@IranAncient · 72,789
Telegram ranks this channel #29 of 82 here — alongside 81 others — read 19 August 2026
Discourse
@Discourseees · 25,462
Telegram ranks this channel #30 of 90 here — alongside 89 others — read 18 September 2026
کتابخانه تاریخ ما
@pdf_tarikhema · 46,393
Telegram ranks this channel #31 of 79 here — alongside 78 others — read 27 August 2026
ناگفته های تاریخ
@NagoftehayeTarikh · 19,423
Telegram ranks this channel #36 of 72 here — alongside 71 others — read 29 September 2026
@litera999کتابخانه‌وموزه
@litera999 · 78,469
Telegram ranks this channel #37 of 80 here — alongside 79 others — read 19 August 2026
افسانه فولکلور و ادبیات حماسی
@legendfolkepic · 20,743
Telegram ranks this channel #42 of 86 here — alongside 85 others — read 29 September 2026
دروغ‌ها و خرافات اسلام
@islie · 21,985
Telegram ranks this channel #43 of 70 here — alongside 69 others — read 23 September 2026
کتاب های تاریخی
@ketabtarikhim · 46,613
Telegram ranks this channel #49 of 88 here — alongside 87 others — read 27 August 2026
نقدى بر اسلام
@naghde_eslamm · 36,737
Telegram ranks this channel #66 of 81 here — alongside 80 others — read 1 September 2026
★کـــــوروش بـــــزرگ★
@cyrus_kabir · 29,203
Telegram ranks this channel #71 of 74 here — alongside 73 others — read 8 September 2026
I am Zeus
@zeus110 · 22,965
Telegram ranks this channel #72 of 96 here — alongside 95 others — read 19 September 2026
🌐مطالب تاریخی
@matalebtarikhim · 30,263
Telegram ranks this channel #77 of 82 here — alongside 81 others — read 7 September 2026

This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“تاریخ اشکانیان | Aškānān gāhnāmag” (@Arsacid_Chronicle), 6,104 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/Arsacid_Chronicle.

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.