Telegram RegisterThe public register of Telegram
Telegram profile photo for 痛

Channel

@xingtong886

On this record: Growth · Engagement · Posts · Polls · Citations · Cite this entry

900subscribers

+3 since we began measuring on 22 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003710746664
TypeChannel
Username@xingtong886
Created6 February 2026measured — dated from the channel’s first post
First recorded22 August 2026
Last confirmed live29 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/xingtong886

Growth

897904900.522 August 2026 — 897 subscribers23 August 2026 — 904 subscribers29 August 2026 — 900 subscribers90022 August 202629 August 2026
3 measurements spanning 7 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 896–905 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 21:07900-4
23 Aug 2026, 10:25904+7
22 Aug 2026, 14:46897first reading

Engagement

13 posts held, back to 6 February 2026the 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.

ERR · 30 days
5.21%
avg views ÷ 900 subscribers
Avg views / post
46.9
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
of 13 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 22 August 2026
Posts held13 (6 February 202622 August 2026)
Views total375
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 14:46 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.

Recent posts

22 Aug 2026, 13:23 UTC2 viewsread 22 August 2026
Photo

⚠️❗️❗️❗️❗️❗️❗️❗️❗️ ♥️秋辞互推挑战全网最强互管 100人以上都可以参与🔤 ✉️你还在求爷爷告奶奶找别人要神秘代码吗? 🔗一键加入📱优质频道 🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰 本人频道 1️⃣飞天稳定战神的直装 2️⃣无敌高跳最强改文件 3️⃣实体美化最强改文件 PUBG账号源头卡网 ⬇️ https://4xg.66url.cn/qhN 加入互推要求 频道1k+ 机器人 @QIUCIHUTUIBOT 🀄️🀄️🀄️🀄️🀄️🀄️ ⬇️⬇️⬇️⬇️⬇️⬇️ (如果你加入了其他文件夹 请尽快退出 都是诈骗!)

Signed 频道主

22 Aug 2026, 12:48 UTC2 viewsread 22 August 2026

秋辞互推(2026年08月22日)频道推荐 1 卤蛋数据号(免费数据号) 2 雾岛董香公益项目主频道 3 高速代理 | 飞机代理 | 公益代理 4 代付频道 5 作恶多端数据号『高质量首选🎉』 6 少萝 自慰 户外 7 秋小鹤八级号【官方正版】 8 雾鱼直装官方频道 9 七辰官方频道 10 仙鹤冰快手领域 11 小豆低价脸书 12 七辰主频道 13 路飞の封号频道 14 七小辰官方频道 15 𝐶𝑙𝑜𝑣𝑒𝑟-四叶草官方频道🍀 互推入口 @QIUCITGHUTUIBOT [秋辞互推自动自荐频道互推]

Signed 频道主

21 Aug 2026, 01:07 UTCviews —

痛 pinned «—————心痛の低价飞机账号————— 🪽卡网商品🪽 TG账号: +91(印度🇮🇳)+880(孟加拉🇧🇩) +86(中国🇨🇳)+57(哥伦比亚🇨🇴) +213(阿尔及利亚🇩🇿) +299(格陵兰🇬🇱六位短号) 卡网库存拉满—正常号最低2元即可购买 低价飞机账号 🔗卡网链接: https://qy.71ywl.com/shop/wxnb 售后: @chanzi887»

21 Aug 2026, 01:05 UTC19 viewsread 22 August 2026

—————心痛の低价飞机账号————— 🪽卡网商品🪽 TG账号: +91(印度🇮🇳)+880(孟加拉🇧🇩) +86(中国🇨🇳)+57(哥伦比亚🇨🇴) +213(阿尔及利亚🇩🇿) +299(格陵兰🇬🇱六位短号) 卡网库存拉满—正常号最低2元即可购买 低价飞机账号 🔗卡网链接: https://qy.71ywl.com/shop/wxnb 售后: @chanzi887

Signed 心痛

20 Aug 2026, 14:19 UTC17 viewsread 22 August 2026
Forwarded from @qmxht

✅少萝互推✅❗️❗️❗️ 🔥专业少萝互推团队❤️效率极高⚡ 0️⃣见雨改文件 1️⃣ 2️⃣云雾改文件 3️⃣ 4️⃣神楚频道 5️⃣空余需要此位置联系 6️⃣空余.需要此位置联系 7️⃣空余.需要此位置联系 8️⃣大甘蔗无限授权号 频道达到3️⃣0️⃣0️⃣人,日浏览量不低于1️⃣5️⃣0️⃣即可参加,浏览量高可上榜😁,榜前5️⃣频道5️⃣k可上 点我加入所有频道 点我加入所有频道 点我加入所有频道 ‼️不存在偷偷塞频道的问题 1️⃣小时内🚫删除 🔘点击参加互推✅ 😃😀😃 😃😃 🕠🕠✅少萝互推✅❗️❗️❗️

19 Aug 2026, 16:19 UTC225 viewsread 22 August 2026
Poll

频道运营什么

  1. 改文件17%
  2. 全防29%
  3. 防人脸55%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

19 Aug 2026, 16:11 UTC40 viewsread 22 August 2026

心痛主频道 https://t.me/wxdjtg 心痛业务频道 https://t.me/wxfhtgh 心痛本人TG @chanzi887

24 Feb 2026, 03:22 UTC≈1,120 viewsread 22 August 2026

Dear Channel Administrators, Members, and Telegram Team: This channel strictly prohibits posting any information in any areas that violates legal regulations or Telegram's policies, including content related to politics, violence, or infringement of others' rights. Recently, we have noticed a large number of users maliciously inciting reports against this channel. Once verified, we will immediately preserve complete

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

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.

19 Aug 2026, 16:19 UTCAnonymous Poll42 voters

频道运营什么

  1. 改文件17%
  2. 全防29%
  3. 防人脸55%

Shares as published, totalling 101%. 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 13 most recent posts we hold, published 6 February 2026 to 22 August 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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 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.

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

“痛” (@xingtong886), 900 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/xingtong886.

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.