今晚在来波更新🎉
👍1
Signed 大狗熊

Channel
@XDGY6
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Cite this entry
95,896subscribers
+23,269 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| 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 | 26 October 2026 |
| Measurements held | 51 |
| Confirmed unchanged | 1 time, most recently 26 October 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 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 | +88 |
| 20 Oct 2026, 16:27 | 94,481 | +231 |
| 19 Oct 2026, 16:58 | 94,250 | +309 |
| 18 Oct 2026, 13:48 | 93,941 | +324 |
| 17 Oct 2026, 13:37 | 93,617 | +366 |
| 16 Oct 2026, 17:09 | 93,251 | +419 |
| 15 Oct 2026, 14:38 | 92,832 | +67 |
| 14 Oct 2026, 11:31 | 92,765 | +576 |
| 12 Oct 2026, 20:44 | 92,189 | +1,560 |
| 8 Oct 2026, 10:17 | 90,629 | +1,865 |
| 3 Oct 2026, 23:20 | 88,764 | +5,217 |
| 25 Sept 2026, 04:41 | 83,547 | +458 |
| 18 Sept 2026, 23:37 | 83,089 | +49 |
| 16 Sept 2026, 16:36 | 83,040 | +135 |
| 14 Sept 2026, 19:01 | 82,905 | +22 |
| 13 Sept 2026, 06:38 | 82,883 | first reading |
432 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 191 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 26 October 2026 |
|---|---|
| Posts held | 432 (2 August 2026 – 26 October 2026) |
| Views total | 868,626 |
| Reactions total | 12,581 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Oct 2026, 10:07 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 26 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.
Measured directly from 10 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.
27,923 reactions across 404 posts, in 7 distinct kinds. The most used accounts for 91.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 25,567 | 91.6% | |
| ❤ | 1,895 | 6.79% | |
| 🤩 | 148 | 0.53% | |
| 👻 | 116 | 0.415% | |
| 🔥 | 97 | 0.347% | |
| 🙏 | 52 | 0.186% | |
| 🥰 | 48 | 0.172% |
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 410 of the 432 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 28,126 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 432 most recent posts we hold, published 2 August 2026 to 26 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.
今晚在来波更新🎉
👍1
Signed 大狗熊
😃😀😃 🌟全功能直装😂🔤🔤🔤🔤🔤😂 AORUS国外顶级开发者开发,真正做到安全稳定,出现问题第一时间更新⭐ 支持游戏⬇️ 1️⃣.三角洲🎮 (适配 国服 国际服 台湾服) 2️⃣.无畏契约🫥 3️⃣.和平精英🎮 4️⃣ 失控进化 功能介绍:⬇️ 1️⃣独家一体启动器直装安装包🐮 2️⃣高清绘制真正做到丝滑游戏 3️⃣独家自瞄追踪,安全稳定高效运作真正做到枪枪到肉 🌟 抓紧点击下方体验 😂加入频道 😂 😂加入频道😂 🔥频道 https://t.me/Aorus68 全网收管理位 联系 @Aorus66bot
👍66
Signed 大狗熊
还要新版想要加什么 想要优化什么 都可以说我尽量满足
👍140❤1
Signed 大狗熊
新版熊大驱动是对标vt驱动的所以自瞄不适配部分机型问题我在想办法给你们解决 耐心等待就好
👍121❤3
Signed 大狗熊
我不知道你们老说新版不好 到底哪里不好又说不上来 我已经说过了旧版局限行太多已经停止更新 新版本我也一直按照你们的反馈在改进争取做到更好!
👍114❤2
Signed 大狗熊
换新包兄弟们;优化了启动器
👍129
Signed 大狗熊
🎮 和平内核apk V9:本次更新需换包 1.完美修复开启数组解密之后 人物蹲下或者趴下骨骼读取异常问题 2.完美解决开启模型解密之后 人物模型会出现时不时失效问题 3.完全重构自瞄底层逻辑 4.完全重写版自瞄压枪逻辑吊打旧版本 5.完全重写新版本预判逻辑吊打旧版本 6.修复防录屏无效问题 7.完全重定向新版本整体代码布局逻辑 8.修复闪框解密 🥰 apk登录卡密随便输入 😙熊大公益卡密已更换为;XDGY6 ⚠️欢迎加入交流群一起探讨 @XDGY9 🥰有任何bug或者需要增加的内容可以联系我 @XDGY0
👍202❤16🙏1
熊大公益频道 pinned «【玩王者的都加一下这个频道】 好朋友项目 公益的很好用 还在玩泛滥驱动的解密项目? 兄弟吃点好的吧,对自己好点 独家驱动 稳定性拉满 不磨叽 直接公益 独家驱动+自瞄+bp查询 该有的都有 点我加入频道领卡密 点我加入QQ群 https://t.me/C11nb000 https://t.me/C11nb000 https://t.me/C11nb000»
【玩王者的都加一下这个频道】 好朋友项目 公益的很好用 还在玩泛滥驱动的解密项目? 兄弟吃点好的吧,对自己好点 独家驱动 稳定性拉满 不磨叽 直接公益 独家驱动+自瞄+bp查询 该有的都有 点我加入频道领卡密 点我加入QQ群 https://t.me/C11nb000 https://t.me/C11nb000 https://t.me/C11nb000
👍177❤5🤩2
Signed 大狗熊
🎮熊大官方自营低价货源 😀😀😀😀😀😀😀😀 🎈·物美价廉·保姆售后·精品享受 🎈·高端Duo独家授权 🎈·精品独家低价直登号 📱 ·TG权重账号全网独家 😀😀😀😀😀😀😀😀@xdshkf 👉各位爸爸爷爷们卡网点我跳转 👉各位爸爸爷爷们卡网点我跳转 👉各位爸爸爷爷们卡网点我跳转
👍149❤3
🎮 和平内核apk V8:本次更新需换包 1.秒杀和平最新数组加密以及物资加密和载具加密 2.秒杀和平最新坐标解密 3.秒杀和平最新模型解密 4.优化调整账号加密预判 🥰 apk登录卡密随便输入 😙熊大公益卡密已更换为;XDGY6 ⚠️欢迎加入交流群一起探讨 @XDGY9 🥰有任何bug或者需要增加的内容可以联系我 @XDGY0
👍144❤18
Signed 大狗熊
一直公益不赚钱要饿死了准备接几个广告有想法联系我,效果拉满 @xdgy0
👍159❤1
Showing the 12 most recent of 432 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.
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 432 most recent posts we hold, published 2 August 2026 to 26 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.
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 26 October 2026 — this entry's latest reading, not the date you are reading this.
“熊大公益频道” (@XDGY6), 95,896 subscribers as measured 26 October 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.