Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔨锤子

Channel

🔨锤子

@CHUIZINB

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

22,518subscribers

-1,104 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002181164489
TypeChannel
Username@CHUIZINB
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 October 2026
Measurements held55
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/CHUIZINB

Topic

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

Growth

22,51823,62223,0707 August 2026 — 23,622 subscribers7 August 2026 — 23,622 subscribers8 August 2026 — 23,610 subscribers9 August 2026 — 23,607 subscribers10 August 2026 — 23,586 subscribers11 August 2026 — 23,568 subscribers12 August 2026 — 23,556 subscribers13 August 2026 — 23,538 subscribers14 August 2026 — 23,504 subscribers16 August 2026 — 23,478 subscribers17 August 2026 — 23,457 subscribers18 August 2026 — 23,423 subscribers19 August 2026 — 23,394 subscribers20 August 2026 — 23,387 subscribers21 August 2026 — 23,383 subscribers22 August 2026 — 23,355 subscribers24 August 2026 — 23,340 subscribers25 August 2026 — 23,322 subscribers26 August 2026 — 23,309 subscribers27 August 2026 — 23,302 subscribers28 August 2026 — 23,281 subscribers29 August 2026 — 23,271 subscribers30 August 2026 — 23,256 subscribers31 August 2026 — 23,241 subscribers1 September 2026 — 23,227 subscribers2 September 2026 — 23,198 subscribers3 September 2026 — 23,182 subscribers5 September 2026 — 23,165 subscribers8 September 2026 — 23,137 subscribers11 September 2026 — 23,115 subscribers13 September 2026 — 23,095 subscribers14 September 2026 — 23,074 subscribers16 September 2026 — 23,067 subscribers19 September 2026 — 23,035 subscribers26 September 2026 — 22,936 subscribers4 October 2026 — 22,835 subscribers8 October 2026 — 22,775 subscribers13 October 2026 — 22,727 subscribers14 October 2026 — 22,700 subscribers15 October 2026 — 22,685 subscribers16 October 2026 — 22,670 subscribers17 October 2026 — 22,664 subscribers18 October 2026 — 22,644 subscribers19 October 2026 — 22,634 subscribers20 October 2026 — 22,624 subscribers21 October 2026 — 22,608 subscribers22 October 2026 — 22,600 subscribers23 October 2026 — 22,588 subscribers24 October 2026 — 22,572 subscribers25 October 2026 — 22,566 subscribers26 October 2026 — 22,556 subscribers27 October 2026 — 22,543 subscribers28 October 2026 — 22,537 subscribers29 October 2026 — 22,532 subscribers30 October 2026 — 22,518 subscribers7 August 202630 October 2026
55 measurements spanning 84 days, net -1,104. 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 22,352–23,788 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 55
Measured (UTC)SubscribersChange
30 Oct 2026, 17:1422,518-14
29 Oct 2026, 18:4922,532-5
28 Oct 2026, 19:4122,537-6
27 Oct 2026, 18:5122,543-13
26 Oct 2026, 17:5522,556-10
25 Oct 2026, 16:5022,566-6
24 Oct 2026, 14:0022,572-16
23 Oct 2026, 17:1422,588-12
22 Oct 2026, 20:0722,600-8
21 Oct 2026, 17:5822,608-16
20 Oct 2026, 13:0922,624-10
19 Oct 2026, 10:5622,634-10
18 Oct 2026, 11:3122,644-20
17 Oct 2026, 11:2822,664-6
16 Oct 2026, 13:5822,670-15
15 Oct 2026, 13:0122,685-15
14 Oct 2026, 15:3722,700-27
13 Oct 2026, 02:4622,727-48
8 Oct 2026, 21:5722,775-60
4 Oct 2026, 12:5422,835first reading

Engagement

27 posts held, back to 30 July 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 86 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.57%
avg views ÷ 22,518 subscribers
Avg views / post
804
10 posts measured
Reaction rate
1.27%
reactions ÷ views · ER floor
Posts in window
10
of 27 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 21 October 2026
Posts held27 (30 July 2026 – 21 October 2026)
Views total8,040
Reactions total102
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Oct 2026, 08:11 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.

Reaction mix

163 reactions across 23 posts, in 6 distinct kinds. The most used accounts for 85.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍14085.9%
❤1811.0%
🤔21.23%
😴10.613%
🤯10.613%
🥰10.613%

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 23 of the 27 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 163 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 27 most recent posts we hold, published 30 July 2026 to 21 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

21 Oct 2026, 05:55 UTC58 views10 reactionsread 21 October 2026
Forwarded from @yuzhou86

⚜️星冠 StarCrown|内部专属项目 全新版本 业内顶配全功能配齐,你所想的极致上分体验,星冠全部拥有! 摒弃花里胡哨的冗余设计,只专注两件事:极致体验、全程稳定 ✨项目核心优势 ✔️精准手感优化——指哪打哪,操作手感直接拉满,先手压制全场 ✔️全局同步视野——开黑组队信息互通,对局节奏尽在掌握 ✔️极速阵容切换——BP环节秒切阵容配置,抢占开局优势 ✔️独立自研算法+高清养眼绘制——运行流畅零卡顿,对局体验拉满 不玩套路,专注品质! 所有功能一站式配齐,想轻松登顶上分,星冠全权安排! 🔥关于品质 定价高端,不做廉价流水线产品 一人一包、一对一定制调试 专属适配优化,拒绝批量同质化 郑重承诺:体验不稳,全额退款!!! 以星为冕,实力为王 用极致细节,碾压全场对局 想解锁顶级上分体验,直接联系作者专属定制:@XingGua123 官方频道:https://t.me/TkML01

👍10

21 Oct 2026, 05:53 UTC64 views8 reactionsread 21 October 2026
Forwarded from @yuzhou86File

更新日志: 1. 增加自动适配 2. 增加自动扁鹊大招 3. 更换UI绘图 4. 适配TwT驱动和临时root 5. 优化部分bug ------------------------ 小地图/斩杀惩戒/自瞄等都无需手动调试 扁鹊大招和斩杀都会自动识别减伤/无敌/名刀等情况 新的UI绘图,以后不能再说Apex版本丑了 应该改为夯爆了! ------------------------ 点击此频道头像即可验证电报或使用过验证文件 点击加入宇宙交流群

👍8

18 Oct 2026, 10:19 UTC474 views15 reactionsread 21 October 2026
File

开源这个解密思路目前依赖性很强,比较一般兄弟,会用的拿去用了 解密给你摆出来了,不要狗叫了,最垃圾的模拟执行解密 直接让你的DeepSeek或者ChatGPT接入你的项目即可使用,解密不了让他按着你自己设备进行适配

👍14❤1

17 Oct 2026, 08:22 UTC648 views15 reactionsread 21 October 2026

🔥 新版本 A6 即将上线! 1.内置算法解密|自由开关,按需开启 2.全英雄自适应自瞄|无需手动调参,上手即用 3.自瞄自动释放扳机|自动把握出手时机,抓准 Timing 4.马超自动收枪、戳枪|收枪与强化普攻连贯衔接 5.镜飞雷神全新优化|连招更顺畅,减少中断 6.扁鹊大招自动斩杀|把握大招收割时机未到 7.暃大招自动斩杀|自动判断二段大招释放时机 8.通用智能斩杀|根据目标血量判断释放时机 9.自动换装|无需录制脚本,点击即可自动识别并绘制 10.貂蝉二技能卡 CD 与触摸脚本|支持操作录制、保存与回放 11.全新 BP 查询|不动内存,支持查看敌方预选与已选英雄 12.BP 战力与胜率查询|常用英雄、历史纪录、推荐禁用 13.AI 托管战斗|一键接管,挂机练账号等级,不触发挂机警告 14.网页实时共享|地图、英雄头像、血量与技能冷却同步观看 15.自动净化 · 智能惩戒 · 上帝视角 · 皮…

👍13❤2

15 Oct 2026, 22:07 UTC948 views3 reactionsread 21 October 2026
Forwarded from @AcenbAcenbFile

优化部分人会一天的问题 账号密码 Spraknb 各种问题 欢迎反馈,有问必答不管是bug反馈还是什么反馈都会处理哦 反馈客服 @HKnb6663

👍3

13 Oct 2026, 08:24 UTC≈1,100 views16 reactionsread 21 October 2026
Forwarded from @AcenbAcenbFile

🎮 王者 × 三角洲|双端通用端口 🎁 工作室级技术 · 限时公益免费开放 ⚡ 独家封包技术,云端持续更新 🔗 双端通用:王者、三角洲一体支持 📦 无视文件下发:从容应对下发变化 💎 行业独家封包技术:打造核心技术优势 ☁️ 云端快速更新:及时响应最新加密变化 🛡️ 无视加密、三方、异常等限制 👑 王者专属:行为 180 → 7 🔺 三角洲专属:协议 3680 → 7 🔑 公益账号 / 密码:Spraknb 📢 账号密码不定期更新,请加入频道及时关注: 👉 进入公益频道 🎯 王者可搭配辅助 反馈客服 @HKnb6663

👍16

12 Oct 2026, 15:45 UTC≈1,310 views16 reactionsread 21 October 2026
Forwarded from @AcenbAcenbFile

优化启动速度,非强制更新 🔥 Sprak 独家王者解密绘制 🎁 公益免费|独家解密思路|全功能绘制与雷达 ✅ 不改写游戏内存 基于独家解密方案实现绘制,运行稳定,体验流畅。 🎯 全英雄自瞄支持 覆盖指向性与范围类技能,百里守约、元歌等英雄均可使用,本命英雄同样支持。 📱 全安卓设备适配 兼容各类安卓设备,适配范围广。 🛡️ 无视下发|不闪框|无第三方内置后门 功能透明,使用安心。 ☁️ 远程云更新 版本更新后启动即可自动获取,无需反复下载启动文件。 💎 免费不减配,体验不妥协 公益分享,完整功能,欢迎体验! 反馈@HKnb6663 驱动包获取

👍15❤1

10 Oct 2026, 11:46 UTC≈1,440 views11 reactionsread 21 October 2026
Forwarded from @huahainbFile

花海三角洲1.2版本(公益中) 公益卡密:huahainb 公告: 更新掩体判断,漏打自瞄。优化绘制显示,优化自瞄调节。 ✅方框-射线-距离-名字 ✅干员-骨骼-血量-手持 ✅护甲-物资-盒子-自瞄 ✅掩体判断-漏打自瞄 ✅绘制美观流畅超低延迟 🔥毫无bug和内存的算法解密 掩体判断模型安装: https://t.me/huahainb/9595 官方TG:@huahainb 有问题联系: @shshi985

👍11

5 Oct 2026, 09:03 UTC798 views4 reactionsread 21 October 2026
Forwarded from @huahainbFile

花海三角洲1.0版本 公益卡密:huahainb 不动内存,纯算法解密。 算法无漏人,无延迟问题 保证不动内存算法不会追封 绘制效果非常出色,无bug 陀螺仪➕触摸自由选择自瞄 TG主频道:@huahainb 有问题反馈 @shshi985

👍4

4 Oct 2026, 19:19 UTC≈1,200 views4 reactionsread 21 October 2026
Forwarded from @huahainbFile

花海三角洲1.0版本 公益卡密:huahainb 不动内存,纯算法解密。 绘制效果非常出色,无bug 有问题反馈 @shshi985

👍4

23 Sept 2026, 17:06 UTC≈2,350 views12 reactionsread 21 October 2026
Forwarded from @XFchartFile

XF公益内核v2.0.更新内容: 1.修复自动净化失效 2.修复镜飞雷神失效 3.修复自瞄局内失效 4.公益增加 头像和技能解密[如卡框人物不动 须坐标解密 建议使用赞助版] 5.修复国际服解密 6.∞∞∞[忘记还修复啥了 应该是都没有问题了] 公益解密须输入指定卡密 XFchart [公益解密将在9.24下午5点关闭] 必须输入指定卡密 mt显示进入赞助版 那才是真正的进入了不然你还是公益 你体验个锤子解密

👍8❤3😴1

22 Sept 2026, 19:53 UTC≈2,540 views5 reactionsread 21 October 2026
Forwarded from @yuzhou86File

更新日志: 适配s45赛季 ------------------------ 点击此频道头像即可验证电报或使用过验证文件 点击加入宇宙交流群

👍3❤2

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

Forward network

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

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

“🔨锤子” (@CHUIZINB), 22,518 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/CHUIZINB.

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.