Telegram RegisterThe public register of Telegram
Telegram profile photo for کانال پینگخور

Channel

کانال پینگخور

@pingkhor_cha

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry

387,644subscribers

+63,612 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1001487582677
TypeChannel
Username@pingkhor_cha
Descriptionکانال اطلاع رسانی پینگ خور لینک ربات پینگخور: @PingKhorbot
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 October 2026
Measurements held47
Confirmed unchanged1 time, most recently 25 October 2026
On Telegramt.me/pingkhor_cha

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 84% 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.

Growth

324,032387,644355,8387 August 2026 — 324,032 subscribers8 August 2026 — 324,685 subscribers9 August 2026 — 325,259 subscribers10 August 2026 — 326,230 subscribers11 August 2026 — 327,261 subscribers12 August 2026 — 328,043 subscribers13 August 2026 — 328,914 subscribers15 August 2026 — 330,070 subscribers16 August 2026 — 332,958 subscribers17 August 2026 — 333,782 subscribers18 August 2026 — 334,492 subscribers19 August 2026 — 335,647 subscribers20 August 2026 — 336,494 subscribers21 August 2026 — 337,584 subscribers23 August 2026 — 338,515 subscribers24 August 2026 — 339,727 subscribers25 August 2026 — 340,376 subscribers26 August 2026 — 341,190 subscribers27 August 2026 — 341,825 subscribers28 August 2026 — 342,427 subscribers29 August 2026 — 342,913 subscribers30 August 2026 — 343,621 subscribers1 September 2026 — 344,383 subscribers2 September 2026 — 344,880 subscribers3 September 2026 — 345,356 subscribers5 September 2026 — 346,320 subscribers8 September 2026 — 347,703 subscribers11 September 2026 — 349,883 subscribers13 September 2026 — 350,424 subscribers14 September 2026 — 351,291 subscribers16 September 2026 — 352,266 subscribers19 September 2026 — 353,994 subscribers25 September 2026 — 358,449 subscribers4 October 2026 — 366,908 subscribers8 October 2026 — 373,051 subscribers12 October 2026 — 379,294 subscribers14 October 2026 — 380,456 subscribers15 October 2026 — 381,522 subscribers16 October 2026 — 382,645 subscribers17 October 2026 — 383,356 subscribers18 October 2026 — 384,137 subscribers19 October 2026 — 385,036 subscribers20 October 2026 — 385,788 subscribers21 October 2026 — 386,659 subscribers22 October 2026 — 387,048 subscribers23 October 2026 — 387,419 subscribers25 October 2026 — 387,644 subscribers7 August 202625 October 2026
47 measurements spanning 78 days, net +63,612. 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 314,490–397,186 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
25 Oct 2026, 01:19387,644+225
23 Oct 2026, 22:59387,419+371
22 Oct 2026, 22:46387,048+389
21 Oct 2026, 20:56386,659+871
20 Oct 2026, 16:19385,788+752
19 Oct 2026, 14:58385,036+899
18 Oct 2026, 13:06384,137+781
17 Oct 2026, 09:48383,356+711
16 Oct 2026, 11:09382,645+1,123
15 Oct 2026, 08:56381,522+1,066
14 Oct 2026, 10:41380,456+1,162
12 Oct 2026, 23:15379,294+6,243
8 Oct 2026, 16:00373,051+6,143
4 Oct 2026, 08:38366,908+8,459
25 Sept 2026, 17:40358,449+4,455
19 Sept 2026, 03:36353,994+1,728
16 Sept 2026, 16:55352,266+975
14 Sept 2026, 17:38351,291+867
13 Sept 2026, 03:15350,424+541
11 Sept 2026, 07:02349,883first reading

Engagement

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

ERR · 30 days
30.2%
avg views ÷ 387,644 subscribers
Avg views / post
117,000
8 posts measured
Reaction rate
0.942%
reactions ÷ views · ER floor
Posts in window
8
of 28 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 24 October 2026
Posts held28 (21 June 2026 – 24 October 2026)
Views total936,200
Reactions total8,815
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Oct 2026, 03:44 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

Photos
50
Videos
15
Links
45

Lifetime counters from Telegram’s own channel header, read 25 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

24,530 reactions across 28 posts, in 2 distinct kinds. The most used accounts for 58.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤14,31158.3%
👎10,21941.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 28 of the 28 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 24,530 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 28 most recent posts we hold, published 21 June 2026 to 24 October 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

24 Oct 2026, 05:19 UTC≈37,500 views897 reactionsread 25 October 2026

❇️ضمن عذرخواهی مشکل برطرف شده و یک روز به تمام اشتراک ها اضافه شد

❤559👎338

23 Oct 2026, 17:19 UTC≈52,900 views1,027 reactionsread 25 October 2026

❇️اختلال در دیتاسنتر تهران داریم مشغول پیگیری هستیم، نتیجه رو همینجا اعلام میکنیم . . .

👎558❤469

22 Oct 2026, 12:05 UTC≈57,000 views1,155 reactionsread 24 October 2026

از امروز صبح شبکه پایدار شده و اختلال مرتفع شده ضمن عذرخواهی 1 روز به همه اشتراک ها اضافه شد

❤712👎443

21 Oct 2026, 18:23 UTC≈69,800 views760 reactionsread 24 October 2026

❇️دوستان عزیز سیستم کارت به کارت امروز موقتا به غیرفعال شده بود که در حال حاضر دوباره فعال شده و میتونید استفاده کنید ❇️از شب گذشته اختلال های لحظه ای شبکه اکثر دیتاسنتر های کشور مشاهده میشه که باعث قطعی های لحظه در اتصالات به خارج کشور میشه که در حال حاضر مشغول پیگیری موضوع از سمت دیتاسنتر هستیم

👎480❤280

3 Oct 2026, 08:38 UTC≈123,000 views1,894 reactionsread 21 October 2026

✅خوشبختانه از دیروز شبکه پایدار تر شده و اختلال ها برطرف شده ❇️ضمن عذرخواهی 1 روز به تمام اشتراک های فعال اضافه شد

❤1,220👎674

1 Oct 2026, 22:14 UTC≈146,000 views1,454 reactionsread 21 October 2026

❇️دوستان عزیز طی چند روز گذشته هم در زیرساخت دیتاسنتر ها و هم شبکه اپراتور های موبایل کشور اختلال شبکه به شدت زیاد شده و در 2 روز گذشته این اختلال ها به اوج خودش رسیده و حتی شبکه اینترنت داخلی کشور هم مختل شده ❇️ضمن عذر خواهی، در حال پیگیری اختلالات رخ داده در سطح دیتاسنتر هستیم و هر گونه تغییری رو اینجا اطلاع رسانی میکنیم

❤952👎502

1 Oct 2026, 14:55 UTC≈231,000 views905 reactionsread 25 October 2026
File

❇️اپلیکیشن پینگخور نسخه 1.2.0

❤647👎258

1 Oct 2026, 14:55 UTC≈219,000 views723 reactionsread 25 October 2026

✅نسخه 1.2.0 از اپلیکیشن اختصاصی پینگخور با تغییرات زیاد منتشر شد ❇️لیست تغییرات این نسخه 1⃣قابلیت اسپلیت تانلینگ که خیلی درخواست کرده بودید به برنامه اضافه شد، از این به بعد میتونید یکسری از برنامه های روی گوشی مثل همراه بانک یا اپلیکیشن های ایرانی رو انتخاب کنید تا ترافیکشون از داخل VPN رد نشه و از اینتدنت عادی خود گوشی استفاده کنه 2⃣ سرور های کاهش پینگ هم به برنامه اضافه شده و میتونید از بین لیست سرور ها انتخابش…

❤565👎158

15 Sept 2026, 16:01 UTC≈36,700 views282 reactionsread 17 September 2026

❇️دوستان گرامی سیستم کارت به کادت چند ساعتی در دسترس نبود که در حال حاضر برطرف شده

❤179👎103

11 Sept 2026, 17:20 UTC≈304,000 views966 reactionsread 25 October 2026

❇️گیمر های عزیز از دیروز عصر تغییراتی در روتینگ شبکه کشور رخ داده و به نظر میرسه مسیر فیبر نوری جنوب کشور قطع شده و ترافیک آی پی های کشور های جنوب خلیج فارس مثل امارات از مسیر آذربایجان و روسیه رد میشه که باعث شده پینگ سرور امارات بالا بره متاسفانه فعلا تا برطرف نشدن مشکل مسیر جنوب کشور پینگ سرور امارات به همین شکل میمونه هرگونه تغییری در این مورد رو همینجا داخل کانال اطلاع رسانی میکنیم ❇️اما اخیرا سرور ترکیه رو ک…

❤564👎402

11 Sept 2026, 07:31 UTC≈284,000 views560 reactionsread 25 October 2026

❇️تغییرات انجام شد و ربات در حال حاضر فعاله ❇️مشکل خطای بارگزاری اطلاعات اشتراک در اپلیکیشن پینگخور و مشکل وارد کردن کد فعال سازی به اپلیکیشن پینگخور برطرف شد بروزرسانی های بیشتری در راهه. . .

❤344👎216

11 Sept 2026, 06:17 UTC≈248,000 views383 reactionsread 25 October 2026

❇️ریات تلگرام جهت انجام یکسری بروزرسانی برای مدت کوتاهی خاموش میشه

👎243❤140

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

Posts edited after publishing

@pingkhor_cha edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
2 October 2026
Most recent edit
2 October 2026

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.

23 Jul 2026, 10:34 UTCAnonymous Poll22,000 voters approx.

به نظر شما خدمات پینگخور در چه زمینه ای نیاز بیشتری برای بهبود داره؟

  1. نظری ندارم (مشاهده نتایج)7%
  2. میزان محدودیت حجم اشتراک ها15%
  3. کیفیت و سرعت اشتراک ها27%
  4. قیمت گذاری اشتراک ها37%
  5. پشتیبانی6%
  6. راحت تر شدن فراید خرید7%

Shares as published, totalling 99%. 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 28 most recent posts we hold, published 21 June 2026 to 24 October 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.

Mentions

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.

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.

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

“کانال پینگخور” (@pingkhor_cha), 387,644 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/pingkhor_cha.

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.