🎮和平精英 🥰11.12日-更新 本次更新全部功能已适配新版本 1.重构新版本自瞄逻辑 2.重构新版本追踪逻辑 3.修复掩体变色 🥰卡密:@XDGY6 本次更新不上传网盘! 大家玩的开心! 有问题随时向我反馈 @XDGY0
👍104❤1
Signed 大狗熊

Channel
@XDGY6
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Cite this entry
100,867subscribers
+28,240 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002369172266 |
|---|---|
| Type | Channel |
| Username | @XDGY6 |
| Description | 做一个平凡的人交流群:@XDGY9 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/XDGY6 |
Gaming — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 47% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 16:01 | 100,867 | +636 |
| 9 Nov 2026, 17:56 | 100,231 | +519 |
| 8 Nov 2026, 08:04 | 99,712 | +371 |
| 7 Nov 2026, 06:19 | 99,341 | +400 |
| 6 Nov 2026, 03:44 | 98,941 | +452 |
| 5 Nov 2026, 04:59 | 98,489 | +66 |
| 4 Nov 2026, 07:51 | 98,423 | +270 |
| 3 Nov 2026, 05:46 | 98,153 | +249 |
| 2 Nov 2026, 03:18 | 97,904 | +348 |
| 1 Nov 2026, 02:38 | 97,556 | +440 |
| 31 Oct 2026, 03:40 | 97,116 | +341 |
| 30 Oct 2026, 06:36 | 96,775 | +241 |
| 29 Oct 2026, 04:38 | 96,534 | +176 |
| 28 Oct 2026, 05:02 | 96,358 | +216 |
| 27 Oct 2026, 02:19 | 96,142 | +246 |
| 26 Oct 2026, 01:37 | 95,896 | +303 |
| 25 Oct 2026, 03:48 | 95,593 | +381 |
| 24 Oct 2026, 01:46 | 95,212 | +440 |
| 22 Oct 2026, 22:56 | 94,772 | +203 |
| 21 Oct 2026, 23:48 | 94,569 | first reading |
453 posts held, back to 2 August 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 231 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 12 November 2026 |
|---|---|
| Posts held | 453 (2 August 2026 – 12 November 2026) |
| Views total | 828,911 |
| Reactions total | 9,874 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 07:55 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.
Lifetime counters from Telegram’s own channel header, read 12 November 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.
Measured directly from 11 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.
30,831 reactions across 420 posts, in 7 distinct kinds. The most used accounts for 91.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 28,261 | 91.7% | |
| ❤ | 2,076 | 6.73% | |
| 🤩 | 154 | 0.499% | |
| 👻 | 126 | 0.409% | |
| 🔥 | 101 | 0.328% | |
| 🙏 | 58 | 0.188% | |
| 🥰 | 55 | 0.178% |
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 426 of the 453 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 31,034 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 453 most recent posts we hold, published 2 August 2026 to 12 November 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.
Telegram’s own ‘edited’ marker: 20 of 83 posts held from the last 30 days (24.1%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🎮和平精英 🥰11.12日-更新 本次更新全部功能已适配新版本 1.重构新版本自瞄逻辑 2.重构新版本追踪逻辑 3.修复掩体变色 🥰卡密:@XDGY6 本次更新不上传网盘! 大家玩的开心! 有问题随时向我反馈 @XDGY0
👍104❤1
Signed 大狗熊
和平新赛季等我适配
👍128🙏3❤2
Signed 大狗熊
🐲迷你枪战 🥰11.9日-更新 1.修复锁帧问题 2.修复验证问题 3.修复追踪不流畅问题 4.增加防录屏功能 🎮和平精英 🥰11.9日-更新 本次更新换了个更舒服的ui 快去体验吧!!! 1.修复恰雷倒计时无效问题 2.增加自救倒计时 3.增加召回枪倒计时功能 4.增加近战模式调节 5.修复掩体漏打判断 🥰卡密:@XDGY6 👉👉下载点我👈👈
👍138❤18👻2
Signed 大狗熊
和平按照需求日常维护更新我们会持续维护公益的。还会继续开发新的游戏
👍196❤1🔥1
频道接广告干干净净效果好有需要联系 @xdgy0
👍192❤5🔥1🥰1
和平有啥要修复或更新的吗
👍121❤7
Signed 大狗熊
🐲迷你枪战 🥰11.5日-更新 1.修复部分用户twt无法刷入问题 2.全部功能进行优化(适配天堂) 3.增加同行显示 🎮和平精英 🥰11.5日-更新 1.增加无模块自瞄 2.增加自瞄选择部位 3.修复开启掩体不追问题 4.增加营地查询 5.增加UDP解密 6.增加同行显示 🥰卡密:@XDGY6 👉👉下载点我👈👈
👍209❤22🤩4👻1
Signed 大狗熊
准备更新
👍217❤4🥰1
Signed 大狗熊
【玩王者的都加一下这个频道】 好朋友项目 公益的很好用 玩这玩那的 不如玩C11 还在玩泛滥驱动的解密项目? 兄弟是真不怕月底拉闸嘛 独家驱动 稳定性拉满 不磨叽 直接公益 独家驱动+自瞄+bp查询 该有的都有 点我加入频道领卡密 点我加入QQ群
👍168❤12🥰2
Signed 大狗熊
🕊白鸽三角洲公益解密云更新 云更新内容: 完善所有解密更新内容 修复反馈已知bug问题 更新美化功能的完整性包含藏皮肤特效,检视动作,新增干员特效皮肤 ✔️白鸽更新频道:@BGGYJM ✔️交流群:@BGGYJM1
👍96❤3🥰1
twt频道过验证
👍94❤6
Signed 大狗熊
🐲迷你枪战 ✅11.2日-更新 1.增加-迷你枪战精英第一准追踪 2.增加-独家加速思路 3.增加-独家高跳思路 4.增加-独家飞天滞空思路 5.增加-人物实体穿墙 6.增加-无限子弹 7.增加-子弹穿墙 8.增加-裸奔大范围 9.增加-裸奔午后据点 快去体验吧 我只能说非常nb 谁玩谁知道!!!
👍102❤20
Signed 大狗熊
Showing the 12 most recent of 453 posts we hold for @XDGY6. 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.
@XDGY6 edited 2 posts 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.
We recorded 64 posts on @XDGY6 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
The 5 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
准备公益三角洲玩吗?
The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
我在想要不要弄个酸角粥呢
The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
更新后自瞄没效果?
The shares total 108%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
你们想要密钥解密?
The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
学生蛋们放假了吗🌟
The shares total 116%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 453 most recent posts we hold, published 2 August 2026 to 12 November 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.
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.
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.
@XDGY6 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“熊大公益频道” (@XDGY6), 100,867 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/XDGY6.
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.