Channel
@WXHCG
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
3,660subscribers
+72 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002119455897 |
|---|---|
| Type | Channel |
| Username | @WXHCG |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/WXHCG |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 05:06 | 3,660 | -11 |
| 26 Aug 2026, 23:57 | 3,671 | -2 |
| 23 Aug 2026, 15:17 | 3,673 | +75 |
| 20 Aug 2026, 07:42 | 3,598 | -1 |
| 17 Aug 2026, 14:13 | 3,599 | +8 |
| 14 Aug 2026, 13:58 | 3,591 | +5 |
| 10 Aug 2026, 17:58 | 3,586 | -1 |
| 7 Aug 2026, 18:14 | 3,587 | -1 |
| 7 Aug 2026, 13:18 | 3,588 | first reading |
10 posts held, back to 11 October 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 10 posts for this entry, the most recent from 11 October 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 videos 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.
80 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 65.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 52 | 65.0% | |
| 👍 | 21 | 26.3% | |
| 😁 | 6 | 7.50% | |
| 🔥 | 1 | 1.25% |
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 10 of the 10 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 80reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 11 October 2024 to 11 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
📡TG直连 ⚡️超高速代理 ✅安全 ✅高速 ✅免费 ✅ ⬅️🇭🇰香港高速线路A👉 ⬅️🇭🇰香港高速线路B👉 ⬅️🇭🇰香港高速线路C👉 ⬅️🇭🇰香港高速线路D👉 💬 建议同时设置4条代理，在失效时能够及时切换至备用代理以免掉线影响使用！ 分享到五個千人交流群，可終身提速百分百😀 永久更新 永久使用 高速官方频道😃😃😃@wanyin66666
❤28👍8😁4
NG爆奖图!南宫牛逼！ NG系列大水不断 ➡️😀壹号🤑多多 ➡️😎亿万 😏旺财🤓狗子 使用本频道链接注册可以提高爆率 （本频道为内部链接超高爆率返水） 🏆新用户首存100送100 🏆周期内存满800送388 活动必须通过以下链接才可以参加 📱📱📱📱📱📱📱📱 🤩官方注册地址： 👌 28zp.cc 【打不开关闭代理VPN即可】 《🉑玩🉑代理，点击邀请好友分享推广链接可领取超高人头奖励》 下载后发uid给客服 @wanyin66666 申请加入VIP加速充提通道！ 充值提现等平台问题可咨询 😀😃😃😃😃 @wanyin66666
❤6👍1
#童锦程 #奶味仙女 最近曝出童锦程睡女粉丝，奶味仙女爆料童锦程摸她不洗手，让她发炎了，气的可爱小猪大早上连发好几条抖音回怼！ 童锦程：做了一辈子陈冠希，没想到这次做了会张柏芝！
👍5❤4
#KTV #群p #3p #淫乱 #做爱 真乱啊
❤7
罕见 美景！10月11日凌晨，受地磁暴影响，北京 迎来 #极光 大爆发，天边肉眼可见红成一片。据了解，这是中国北纬40°第二次可观测到极光。
👍2❤1
找女朋友就得找这样的 #肌肉女 安全感 ！
👍3
怎么就知道玩手机？
又有新景点看一看了
❤3😁2
10月8日 四川 乐山 一男生在校门口与 母亲 争夺 手机，将 母亲 拖拽在地。知情者称，事件源于男孩爷爷瞒着母亲给孙子购买手机。男孩母亲发现后欲没收，引发争执。
我儿子被网上的男婊子害惨了
❤3👍2🔥1
Showing the 10 most recent of 10 posts we hold for @WXHCG. 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.
Citation-graph rank — 401,374 of 1,628,524entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
@WXHCG named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“吃瓜中心（免费高速代理）” (@WXHCG), 3,660 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/WXHCG.
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.