Channel
@tarava_ir
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
840subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003098017998 |
|---|---|
| Type | Channel |
| Username | @tarava_ir |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/tarava_ir |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 17:51 | 840 | no change |
| 11 Aug 2026, 13:16 | 840 | first reading |
20 posts held, back to 5 June 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 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 5 August 2026 |
|---|---|
| Posts held | 20 (5 June 2026 – 5 August 2026) |
| Views total | 289 |
| Reactions total | 19 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 13:16 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.
144 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 80.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 116 | 80.6% | |
| 💔 | 13 | 9.03% | |
| 🕊 | 7 | 4.86% | |
| 👍 | 6 | 4.17% | |
| 👌 | 2 | 1.39% |
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 20 of the 20 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 144reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 5 June 2026 to 5 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.
«اگه شعارها، پشتِ خودشون یه حقیقتِ دیگه قایم کرده باشن چی؟» آن سوی هیاهو... شروع روایت از یک سوال، تماس کوتاه و رسیدن به جواب از سوی دیگرِ ماجرا تارآوا | پژواک آگاهی 「 @tarava_ir 」
❤3👍1
#رادیو_تارآوا ⋅╌┈───╼ ╾───┈╌⋅ «شبها پرچمِ خونخواهی در دست... روزها خبرِ مذاکره روی خروجی رسانهها...» گاهی تناقضها، پیش از آنکه پاسخ بخواهند، ذهن را آشفته میکنند. چرا بعضی اتفاقها با آنچه پیشتر شنیدهایم متفاوت به نظر میرسند؟ و اگر میان روایتها سرگردان شویم، از کجا باید پاسخ را پیدا کنیم؟ گفتوگویی که شاید نگاهت را تغییر دهد. 🎙 روایت را بشنو... شاید پاسخ، آنجایی باشد که کمتر دنبالش گشتهای. ⋅╌┈────╼ ╾─…
❤3
#رادیو_تارآوا #روایتِحقیقت ━────◈────━ فریبِ روایتهای ناقص رو نخور! 🚫 شنیدنِ ماجرا فقط از یک زاویه، یعنی نشنیدنِ بخش بزرگی از واقعیت. خطرناکتر از دروغ، «نیمهحقیقتها» هستند؛ بخشهایی از واقعیت که عمداً انتخاب میشن تا ذهنِ تو رو جهتدهی کنن. مرز بین ایران دوستی و دین داری کجاست؟ آیا میشود هم به ایران باستان افتخار کرد و هم دینت اسلام باشه ؟ یا اینکه همیشه باید یکی را قربانی دیگری کرد؟ ━────◈────━ [🎙گویندگا…
❤4👌1
#رادیو_تارآوا #روایتِحقیقت ━────◈────━ گاهی ماجرا از یک سوال شروع میشود... گاهی فقط یک جمله، سالها باور را به چالش میکشد... اگر همهٔ چیزی که تا الان شنیدیم درست نبوده باشه چی؟! اصلاً کی گفته باید برای امام حسین عزاداری کنیم؟ اینا همون اعرابی هستن که تو جنگ قادسیه کلی ایرانیو کشتن... شاید این حرفها ساده به نظر بیان، اما اگر جواب درستشون رو ندونی، کم کم روی باور هات اثر میزارن. برای رسیدن به جوابِ درست و حقیقت، …
❤3👌1
میان اگر ها «اگه همهٔ چیزی که شنیدیم، درست نبوده باشه چی؟» این سؤال، شروع داستان لیلا و فریباست. داستانی از شک، تردید، سوال و پیدا کردن پاسخ از میان روایتهای مختلف؛ نه از میان هیاهوی فضای مجازی. 🎙️ انتشار در دو قسمت با ما همراه باشید. 『کاری از کارگروه رادیوییِ تارآوا』 تارآوا | پژواک آگاهی 「 @tarava_ir 」
❤3
پَسِ خِیمه پادکستِ قسمت دوم از روایت محرم روایتی از نگاه امام سجاد(ع) از وداع، عطش و داغی که قرنها خاموش نشده است. 『کاری از کارگروه رادیوییِ تاراوا』 تارآوا | صدایاَندیشهها 「 @tarava_ir 」
❤5🕊1
#رادیو_تارآوا #روایت_محرم ━────◆────━ فرات جاری بود… اما سهم خیمهها تنها عطش بود... آن روز دشمن گمان میکرد کار حسین را تمام کرده است، گمان میکرد با نیزه و شمشیر میتوان نور خدا را خاموش کرد و با غرور خود را پیروز میدان نامیدند. اما آنان نمیدانستند که گاهی شکست چهره پیروزی به خود میگیرد و گاهی پیروزی آغاز نابودی است... وداعها یکییکی آغاز شدند، و هر وداع، تکهای از قلب حسین(ع) را با خود برد. این پادکست فقط یک …
❤4👍1💔1
#رادیو_تارآوا #روایت_محرم ∙————≍✦≍————∙ محرم آمده است... با همان داغِ قدیمی، اما با درکی تازه. گاهی باید از میان اشک ها عبور کرد تا حقیقت را واضح تر دید؛ حقیقتِ وفاداری، ایثار، غربت و ایستادگی. فراق واژهای است که قرن ها،این سرزمین آن را میشناسد. سرزمینی که مردان بسیاری را بدرقه کرد، اما هرگز یادشان را به خاک نسپرد... این، دعوتنامهی ماست برای سفری به اعماقِ یک قصه که هیچوقت تمام نمیشود، این قصه را تا اربعین،…
❤3🕊1
از سوگواری تا آگاهی... پادکستِ قسمت اول از روایت محرم بعضی قصهها پایان ندارند... قرن ها میگذرند، اما هنوز تازهاند؛ مثل عاشورا، مثل کربلا، مثل نامِ حسین(ع) به راستی، چه کسی فکر میکرد روزی در چنین سرزمینی محرم و کربلا اینگونه، تازه تر از هر سال و ماهی قد علم کند... روایتی از اشک، شعور و حقیقت 『کاری از کارگروه رادیوییِ تاراوا』 تارآوا | صدایاَندیشهها 「 @tarava_ir 」
❤3
#رادیو_تارآوا📻 #پادمَکث ━━━༺❀༻━━━ وقتی میگفتی مَردِکوچولوی خونه و مامان ذوق میکرد... 🔸️روایتِاحساسی از آنچه رُخ داد در نگاهِ فرزند شهیدِ جنگ رمضان: ~اَمیرمحمد علیمحمدی~ 🔗 بهقلم و گویندگی تارآوا🎶 ━━━༺❀༻━━━ 🎙گویندگان: نیانحسینی، سارا ابراهیمیان 🎧تدوینصوتومتن: خانمنصیری تارآوا |صِدایاَندیشهها 「 @Tarava_313 」
💔6❤2👍2
#عکس_نوشت 📻پادمَکث: ایستگاهی کوتاه میان رِوایتها . 🖇حال، شاید که فرزند شِشماهه او، بعدها با عنوانِ روایت یک قهرمان به داستان پدر بنگرد... 🔸️بازآفرینی آنچه رُخداد؛ از نگاهِ فرزند شهید، به قلم و گویندگیِ تارآوا🔸️ باحالِمناسببشنوید🎧 تارآوا |صِدایاَندیشهها 「 @Tarava_313 」
❤6💔3🕊1
#رادیو_تارآوا📻 #روایت_لاله ◈━═════✦═════━◈ از هیئت تا حرم...🕌 از خدمت تا شهادت...🪽 روایتیمُختصر از پاسدارشهید: •✦•هادی اَحمدی•✦• مردی که عشق به خدا و اهلبیت(ع) را در عمل معنا کرد و در راه دفاع از حق، آسمانی شد. 🎙گویندگان:آقایمهدیشعبانی، خانمآرامجعفری 🎧تدوین: فاطمهسرگشته 📲باهمکاری: رسانهیشهید؛ هادیاَحمدی⬅️ < rubika.ir/shahidhadiahmadi > ◈━═════✦═════━◈ تارآوا |صِدایاَندیشهها 「 @Tarava_313 」
❤9
Showing the 12 most recent of 20 posts we hold for @tarava_ir. 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 — 117,143 of 1,481,306entries 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“تارآوا๛📻” (@tarava_ir), 840 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/tarava_ir.
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.