3 measurements spanning 21 days, net +3. 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 312–315 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
26 Aug 2026, 12:38
315
+3
6 Aug 2026, 22:17
312
no change
5 Aug 2026, 23:41
312
first reading
Engagement
12 posts held, back to 4 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 · 30 days
39.2%
avg views ÷ 315 subscribers
Avg views / post
124
4 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
4
of 12 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
Window
Rolling 30 days · latest post in window 4 August 2026
Posts held
12 (4 June 2026 – 4 August 2026)
Views total
494
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Aug 2026, 22:17 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
6 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
3
50.0%
👏
2
33.3%
❤
1
16.7%
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 4 of the 12 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 4 June 2026 to 4 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.
چندسالی هست که در مورد پیازکاری در حومه شهر چالانچولان انتقاد میکنیم که واقعا بوی سم این نوع کشت مردم چالانچولان رو اذییت میکنه امسال شخصی زمینی که نصفش در خونههای مردم هست رو پیاز کاشته و هرشب سمپاشی میکنه فکرشو بکنید هرشب جلوی خونت سم بزنن ما نمیگیم کشاورزا کشاورزی نکنن ولی به فکر مردم هم باشید دیگه حداقل زمینی که نصفش داخل شهر هست پیاز نکارید چالانچولان شهر کوچکی هست وفوری بوی سم همهجا پخش میشه فردا پس فردا ا…
مرکزدرمانی چالانچولان در محوطه درمانگاه به جای گل خار پرورش میدن خارسیاه تا ارتفاع یک متر کناردیوارها رشد کرده درختها هم مثل نخلهای بیسر زمانجنگ دارن از بین میرن حداقل این درختها رو آببدید
کارگران شهرداری چالانچولان تو گرمای تابستان زحمت کشیده و کانالهای فاضلاب رو تمیز میکنن ولی متاسفانه یه جایی دیگه دپو میکنن و همینجور به حال خود رها میکنن تا دوباره وارد چرخه زبالهها شوند
این کامیونت تخلیهچاه فضولات انسانی رو تو زمینهای کاشاورزی روبروی چالانچولان خالی کرده که
به هر حال هرکی مسئول اینطور مسائل هست پیگیری کنن چون با سلامت مردم مرتبط هست
البته پلاک هم نداره یه پلاک قدیمی چهلسال پیش
با تشکر از ادارهراه وپیمانکار پروژه دوربرگردان چالانچولان جهت ایجاد سرعتگیر بخاطر کاهش تصادفات اگه زحمت کشیده و چندتا خطموازی روی آسفالتایجاد کرده یا سرعتگیر را رنگ کنندکار نیک وپسندیدهای است چون شبا اصلا سرعتگیر به چشم نمیاد و این ممکناستخودباعث تصادف شود
یه مسئلهای این وسط هست که چند وقته بنده پیگیر شدم متاسفانه برخی اهالی روستاهای بخش سیلاخور وقتی سگ پیری یا به قولی سگ پیسی یا سگ مادهای دارن میارن اطراف چالانچولان رها میکنن و پیش خودشون میگن اینجا چیزی گیرشون میاد میخورن در صورتیکه اونا رو نجات که نمیدن بلکه به کشتارگاه میفرستن روز یا شب نیست که در جاده عبوری چالانچولان خودرویی با سگی تصادف نکنه و یا بعد مدتی به علت تعداد بالای سگای ولگرد و شکایت اهالی به شهرداری …
چندشب پیش شهرداری محترم زحمت کشیده و اقدام به جمعآوری سگهای ولگرد و بلاصاحب کرده و ظاهرا سگهایی هم بینشون بوده که صاحب داشتن و این موجب اعتراض شخص یا اشخاصی شده بهتر اینه که شهرداری محترم قبل از اقدام از طریق رسانههای مختلفی که هست اطلاعرسانیکنند تا باعث اعتراض اهالی نشود
شب گذشته در چالانچولان دو تا تصادف به فاصله یک ساعت اتفاق افتاد دلیلش هم کندهکاری برای ایجاد دوربرگردان در این مسیر بوده متاسفانه هیچگونه علائم هشدار دهنده یا سرعتگیر ایجاد نشده و پیمانکار بدون علائم هشداردهنده دوسال است که مشغول بکار است
پل عابر چالانچولان که درزمان جنگ تحمیلیسوم طی حادثهای بشدت آسیب دیده همینطور به امان خدا رها شده از مسئولین محترم اینشهر تقاضا داریم که پیگیر باشن حداقل جمعش کنن چون ممکنه باعث حادثهای دیگر شود
Signed Reza
Showing the 12 most recent of 12 posts we hold for @chalancholan. 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.
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 26 August 2026 — this
entry's latest reading, not the date you are reading this.
“کانال رسمی چالانچولان” (@chalancholan), 315 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/chalancholan.
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.