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.
Views per post sit far above this size band
5,300 average views per post against 6,710 subscribers — an engagement rate of 79.0%. Across the 6,376 registered channels in the same cohort — 3,166–9,999 subscribers, posting mainly in Persian — the middle half sit between 4.11% and 17.9%, with a median of 9.12%.
What this was computed from
Window
30 days (8 August 2026 – 7 September 2026)
Posts measured
21 of 22 published in the window (4 exact, 17 rounded by Telegram)
Views totalled
111,259
Mature posts only
86.9% over 19 posts read at least 24h after publication
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 7 September 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.
Growth
9 measurements spanning 22 days, net +715. 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,681–8,402 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
2 Sept 2026, 06:34
6,710
-128
30 Aug 2026, 11:15
6,838
-167
27 Aug 2026, 07:03
7,005
-254
23 Aug 2026, 21:14
7,259
-431
20 Aug 2026, 15:53
7,690
-398
17 Aug 2026, 16:06
8,088
+973
14 Aug 2026, 17:59
7,115
+629
11 Aug 2026, 07:16
6,486
+491
10 Aug 2026, 22:15
5,995
first reading
Engagement
30 posts held, back to 24 May 2021 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 10 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
79.0%
avg views ÷ 6,710 subscribers
Avg views / post
5,300
21 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
22
of 30 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 21 August 2026
Posts held
30 (24 May 2021 – 21 August 2026)
Views total
111,259
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Aug 2026, 20:54 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.
What this channel posts
Video runtime
29s
Average length
29s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
PingX Premium VPN😎
کانفیگهای ما با سرعت و کیفیت بسیار عالی ارائه میشوند 👉
قیمت؟ فقط گیگی ۶ هزار تومان 🤑
بدون محدودیت تعداد کاربر ❌
بدون محدودیت دانلود ♾
پینگ کمتر از 100 🛞
موقعیت جغرافیایی ثابت📍
بدون ضریب❌
مناسب برای تمامی اپراتورها 🛜🛜🛜🛜
لینک پنل ساب 🌂
پشتیبانی از تمامی برنامهها 🔐❤️😍🔐
تضمین اتصال تا پایان حجم❤️
🔥 تست رایگان + و خرید آنی از طریق بات:
🤟 @Thepingxbot
🤩 پشتیبانی | بات | چنل
این قیمتایی که میذارین دیگه رقابت نیست، حراج آخر فصله 😂
بعد مشتری میاد پیش ما میگه:
ولی فلان جا n ماهه رو اینقدر میده!
مشتریه عزیز، ۶ ماه دیگه کی مرده کی زنده، طرف از الان نشسته VPN شش ماهه میفروشه...
🤩 پشتیبانی | بات | چنل
ریجن های 🇫🇮🇺🇸🇳🇱🇩🇪و... همه در یک ساب فعال و موجود هست
🤑مناسب اینستا تلگرام یوتیوب گیم و...
🤑سرعت و کیفیت تضمین شده
🤝 @ThePingxBot
🤩 پشتیبانی | بات | چنل
🤩 PingX Premium Config
اگر دنبال یه کانفیگ سریع و پایدار هستی، PingX رو امتحان کن 😎
✅ از فقط گیگی ۶ هزار تومان
✅ آیپی ثابت
✅ دستگاه نامحدود
✅ سرورهای متنوع
✅ مناسب استفاده روزانه، استریم، بازی و شبکههای اجتماعی
همراه با تست رایگان 👑
🤩 پشتیبانی | بات | چنل
تانل آلمان به پینگاکس اضافه شد🇩🇪
برای اتصال پایدارتر روی اینترنتها و اپراتورهای مختلف، مسیر Germany Tunnel به سرویسها اضافه شد.
✅ اتصال پایدارتر
✅ سازگار با اینترنتهای مختلف
برای دریافت، لینک ساب خود را آپدیت کنید.
⚠️ضریب مصرف تانل: ×2.5
🤩 پشتیبانی | بات | چنل
🔴سرور های TCP و direct روی ایرانسل اوکی شدن 🤩
بعد از کلی اسکن بالاخره شد...
🔴 توجه داشته باشید که ممکنه مجدد sni هارو ببندن پس کانفیگ هایی که پسوند Irancell دارن داخل سرویس باقی میمونن که عزیزان ایرانسل براشون مشکلی پیش نیاد 🤑
🤩 پشتیبانی | بات | چنل
Showing the 12 most recent of 30 posts we hold for @ThePingX. 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.
Forward network
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.
Mentions
Named by 5 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.
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 2 September 2026 — this
entry's latest reading, not the date you are reading this.
“PingX ™” (@ThePingX), 6,710 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/ThePingX.
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.
