Video message, posted without a caption
❤🔥25🔥4❤1

Channel
@chitarunn
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
365subscribers
-25 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003786523277 |
|---|---|
| Type | Channel |
| Username | @chitarunn |
| Created | Between 1 February 2026 and 4 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/chitarunn |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 18:14 | 365 | -7 |
| 5 Sept 2026, 01:00 | 372 | -6 |
| 27 Aug 2026, 13:42 | 378 | -7 |
| 21 Aug 2026, 00:04 | 385 | -3 |
| 14 Aug 2026, 06:53 | 388 | -3 |
| 6 Aug 2026, 22:40 | 391 | +1 |
| 6 Aug 2026, 20:05 | 390 | no change |
| 6 Aug 2026, 02:33 | 390 | first reading |
20 posts held, back to 4 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
385 reactions across 20 posts, in 19 distinct kinds. The most used accounts for 49.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 189 | 49.1% | |
| 👎 | 43 | 11.2% | |
| 🔥 | 33 | 8.57% | |
| ❤🔥 | 31 | 8.05% | |
| 👏 | 27 | 7.01% | |
| 🏆 | 12 | 3.12% | |
| 🆒 | 8 | 2.08% | |
| 😐 | 7 | 1.82% | |
| 👀 | 6 | 1.56% | |
| 🤯 | 6 | 1.56% | |
| 🤩 | 5 | 1.30% | |
| 😈 | 4 | 1.04% | |
| 🗿 | 3 | 0.779% | |
| ⚡ | 2 | 0.519% | |
| 🎉 | 2 | 0.519% | |
| 😍 | 2 | 0.519% | |
| 😢 | 2 | 0.519% | |
| 😴 | 2 | 0.519% | |
| 🐳 | 1 | 0.26% |
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 385 reactions 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 4 July 2026 to 2 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.
Video message, posted without a caption
❤🔥25🔥4❤1
🥉نفر سوم🏆 ⚡️خانم مرضیه چراغی 👏🎉🌟
❤4😍1😴1
Video message, posted without a caption
❤18❤🔥2⚡1🔥1
🥈 نفر دوم 🏆 ⚡️آقای ماهان خسرویزاده!👏🎉🌟
❤6🔥1😴1
Video message, posted without a caption
❤24👎20🗿2
🥇 نفر اول رویداد چیتاران 🏆 ⚡️آقای محمد شربتی! 👏🎉👑
❤7👎4
سلام به همگی! 🐆✨ جوایز چیتاران اهدا شد 🎁🏆 و حالا بشنویم آخرین سخن قهرمانان چیتایی خودمون رو... 🎤🥇👑
❤6
🎉 پرونده اولین دوره چیتاران با یک دستاورد فوقالعاده بسته شد. در این ۱۴ روز، شما در مجموع ۵٬۷۴۸٬۱۷۳ قدم برداشتید؛ یعنی چیزی حدود ۴٬۵۹۸ کیلومتر مسیر را با هم طی کردیم. 🚶💛 اما این فقط یک عدد نیست... 🏅 ۲۵ نفر از شرکتکنندهها به اندازه یک ماراتن کامل (۴۲٫۱۹۵ کیلومتر) یا بیشتر قدم برداشتند. 💪 ۳۵ نفر هم حداقل به اندازه یک نیمهماراتن (۲۱٫۱ کیلومتر) مسیر را طی کردند. این آمار نشان میدهد که چیتاران فقط یک مسابقه نبود؛ …
🔥8❤3😐3🏆2👏2
مسابقهمون تموم شده و خسته نباشید میگیم به همه چیتاها🐆 به هر سه تا عزیز دل خسته نباشید میگیم🩵🤍 جزئیات تعداد قدم ها و امتیازات هر سه نفر برای هر روز و هر بخش در گوگل شیت که لینکش در همین پیام در دسترسه، نوشته شدن. چندتا نکته مهم پایانی: ✅این نفرات برتر چطوری قراره جایزههاشون رو دریافت کنن؟🧐 برندگان لطفا به اکانت پشتیبانی پیام بدن و شماره شبا و شماره کارتی که به نام خودشان هست را برای ما ارسال کنند ✅نامه نفرات برتر…
❤13👎2👏1🔥1🤩1
🥉نفر سوم خانم مرضیه چراغی که در رقابت جذابی با خواهرش قرار داشت و در روزهای آخر با شکستن رکورد ها، مجموع تعداد قدمهای بیشتری از نفر اول داشت اما بخاطر قوانین سقف امتیاز روزانه مسابقه در این رده قرار گرفت. ضمن عرض تبریک فراوان امیدواریم همیشه با همین انگیزه و قدرت به مسیر موفقیت ادامه دهند.💛💫🐆
❤13❤🔥2👎2👏2
🥈 نفر دوم، آقای ماهان خسرویزاده؛ کسی که با وجود شرایط سخت جسمانی در هفته اخر، با اراده و پشتکار، عملکردی تحسینبرانگیز را رقم زد. تبریک به ایشان بابت این دستاورد ارزشمند🐆👏🎉
❤9👏3❤🔥2🐳1👎1🔥1🆒1
🥇نفر اول آقای محمد شربتی بود که از روز اول خستگی ناپذیر پیش رفت و تمام امتیاز های ممکن رو کسب کرد! کسب این مقام ارزشمند را صمیمانه به اقای شربتی تبریک میگوییم🐆🎉👏
👏16👎8❤5🤩3🗿1
Showing the 12 most recent of 20 posts we hold for @chitarunn. 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.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Chitarun” (@chitarunn), 365 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/chitarunn.
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.