卧槽 QQ2026年史诗级更新!
😁3❤1
Signed Tartarus

Channel
@HellCellZC123
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
10,849subscribers
-36 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001216399002 |
|---|---|
| Type | Channel |
| Username | @HellCellZC123 |
| Created | 16 February 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 2 times, most recently 11 September 2026 |
| On Telegram | t.me/HellCellZC123 |
Technology — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 |
|---|---|---|
| 8 Sept 2026, 12:38 | 10,849 | -6 |
| 5 Sept 2026, 05:58 | 10,855 | -2 |
| 3 Sept 2026, 09:17 | 10,857 | -2 |
| 2 Sept 2026, 05:23 | 10,859 | -5 |
| 31 Aug 2026, 08:06 | 10,864 | -1 |
| 30 Aug 2026, 05:07 | 10,865 | +1 |
| 29 Aug 2026, 01:57 | 10,864 | -2 |
| 28 Aug 2026, 04:43 | 10,866 | +2 |
| 26 Aug 2026, 03:08 | 10,864 | -2 |
| 23 Aug 2026, 17:47 | 10,866 | +5 |
| 22 Aug 2026, 04:36 | 10,861 | -4 |
| 20 Aug 2026, 21:45 | 10,865 | -3 |
| 19 Aug 2026, 18:37 | 10,868 | -1 |
| 18 Aug 2026, 21:02 | 10,869 | -4 |
| 17 Aug 2026, 19:38 | 10,873 | -3 |
| 16 Aug 2026, 17:26 | 10,876 | -4 |
| 15 Aug 2026, 02:09 | 10,880 | -1 |
| 13 Aug 2026, 17:58 | 10,881 | +1 |
| 12 Aug 2026, 14:54 | 10,880 | -1 |
| 11 Aug 2026, 16:34 | 10,881 | first reading |
15 posts held, back to 15 June 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 40 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 24 August 2026 |
|---|---|
| Posts held | 15 (15 June 2026 – 24 August 2026) |
| Views total | 7,227 |
| Reactions total | 25 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Sept 2026, 19:59 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.
81 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 38.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 31 | 38.3% | |
| 👍 | 30 | 37.0% | |
| ❤ | 12 | 14.8% | |
| 👎 | 8 | 9.88% |
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 14 of the 15 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 81 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 15 June 2026 to 24 August 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.
卧槽 QQ2026年史诗级更新!
😁3❤1
Signed Tartarus
不错
😁17👍2
Signed Tartarus
#Test #Loon4Mac Loon for Mac 0.3.0(66)版本已准备好在 Mac OS上进行测试。 - 全新的 UI - 整个 App 使用 Appkit 完全重新实现,丢弃原来的 SwiftUI - 侧边栏支持展开收起 状态栏面板鼠标放在 menu 上会自动出现子面板 - 重构整个引导流程,激活、安装帮助工具更加方便安全 - 重构XPC 进程交互模块,主 app 和 NE 内核交互更加安全便捷 - 调整进程统计数据逻辑,更加精准高效 - 优化节点、策略组测速逻辑,减少节点过多导致的 UI 卡顿和 CPU 占用率高的问题 - 增加状态栏配置,可以自己设置显示内容、显示策略组的数量 - 增加 UI 主题,可以自己设置或者导入他人主题 - 优化插件详情页的 UI 设计 PS : 目前主要重新设计了一二级的展示内容的 UI,编辑配置的 UI 后续会更进 最新包下载地址:https://github.com/Lo…
Signed Tartarus
#Test #Loon4Mac Loon for Mac 0.3.0(66)版本已准备好在 Mac OS上进行测试。 - 全新的 UI - 整个 App 使用 Appkit 完全重新实现,丢弃原来的 SwiftUI - 侧边栏支持展开收起 状态栏面板鼠标放在 menu 上会自动出现子面板 - 重构整个引导流程,激活、安装帮助工具更加方便安全 - 重构XPC 进程交互模块,主 app 和 NE 内核交互更加安全便捷 - 调整进程统计数据逻辑,更加精准高效 - 优化节点、策略组测速逻辑,减少节点过多导致的 UI 卡顿和 CPU 占用率高的问题 - 增加状态栏配置,可以自己设置显示内容、显示策略组的数量 - 增加 UI 主题,可以自己设置或者导入他人主题 - 优化插件详情页的 UI 设计 PS : 目前主要重新设计了一二级的展示内容的 UI,编辑配置的 UI 后续会更进 最新包下载地址:https://github.com/Lo…
❤2
Signed Tartarus
#TestFlight #iOS #website Loon 3.5.1(978)版本已准备好在iOS 上进行测试。 - Rewrite 现已支持更灵活的条件组合、变量引用和多 Action 执行,可同时处理URL、Header、Body、JSON、Mock 等内容,也可以同时匹配执行多个 Rewrite。详细语法请查看 Rewrite 使用文档( https://nsloon.app/docs/Rewrite/rewrite_v2 ) - 新的匹配机制通过优化匹配算法减少无效匹配,提升大量 Rewrite 配置下的匹配速度,并降低运行时内存占用。同时兼容旧版配置,新增可视化编辑、配置校验和语法预览,并统一了 HTTP、HTTPS 与 HTTP/2 下的 Rewrite 执行行为。 - 新语法重构了整个 rewire 模块,改动较大,如遇到问题请及时反馈。 Website - 官网( https://nsloo…
Signed Tartarus
#TestFlight #iOS #website Loon 3.5.1(978)版本已准备好在iOS 上进行测试。 - Rewrite 现已支持更灵活的条件组合、变量引用和多 Action 执行,可同时处理URL、Header、Body、JSON、Mock 等内容,也可以同时匹配执行多个 Rewrite。详细语法请查看 Rewrite 使用文档(https://nsloon.app/docs/Rewrite/rewrite_v2)。 - 新的匹配机制通过优化匹配算法减少无效匹配,提升大量 Rewrite 配置下的匹配速度,并降低运行时内存占用。同时兼容旧版配置,新增可视化编辑、配置校验和语法预览,并统一了 HTTP、HTTPS 与 HTTP/2 下的 Rewrite 执行行为。 - 新语法重构了整个 rewire 模块,改动较大,如遇到问题请及时反馈。 Website - 官网(https://nsloon.app)优…
❤1
Signed Tartarus
#Test #Loon4Mac Loon for Mac 0.3.0(63)版本已准备好在 Mac OS上进行测试。 • 新的菜单栏面板 • 添加按进程进程分流,PROCESS-NAME,Xcode,DIRECT (key 大小写不敏感;这里的 key 显示的是 app 的进程名称,不是 app 的名字,如果不知道进程具体名称,可以到请求记录页面中查看) • 优化节点延迟测试后的 UI 刷新,修复节点较多时的卡顿问题 • 优化网速计算方式 最新包下载地址:https://github.com/Loon0x00/Loon4Mac/releases/download/0.3.0(63)/Loon-0.3.0-beta-63.dmg 👥 频道: @LoonNews 💬 群组: @Loon0x00
👍6❤1
Signed Tartarus
小米、OPPO、vivo、荣耀四家组成的金标联盟,近期完成了一轮安卓生态的集中升级。 下一代 OS,普通用户日常用机,会在这几个地方感受到变化: ·VoIP 通话方面 ,钉钉、飞书已经接入,企业微信即将接入,简单说,就是以后用APP打网络电话,接通更稳定,弹窗、接听的交互体验和系统自带电话几乎没差别 ·联系人 Picker 新增支持可选收藏联系人,支持多选不同类型数据并且可自定义最大选择数量 ·照片 Picker 支持内嵌到应用,保持应用统一风格且无需申请相册访问权限 ·新增定位 Picker 与相机 Picker,可快速接入系统相机,使用原生相机功能与算法 ·新增 SharedView Kit 一镜到底无缝动画统一接口SDK,适配后打开APP、点内容跳转、返回退出的过渡动画会更跟手自然,像“一镜到底”一样连贯,不会有生硬的割裂感。一次适配可在小米、OPPO、vivo、荣耀手机上生效,将系统流畅动画延伸至三方应用内,…
Signed Tartarus
#Test #Loon4Mac Loon for Mac 0.2(61)版本已准备好在 Mac OS上进行测试。 1.同步 Loon 最新内核 2.修复首页路由、DNS 在测试延迟时偶现异常的 bug 3.修复配置文件偶现的同步异常 bug 4.调整代码架构,方便多平台编译发布 最新包下载地址:https://github.com/Loon0x00/Loon4Mac/releases/download/0.2.0(61)/Loon-0.2.0-beta-61.dmg 👥 频道: @LoonNews 💬 群组: @Loon0x00
❤2
Signed Tartarus
国民应用:微信,已接入金标联盟的公平运行内存机制。 oppo:https://open.oppomobile.com/documentation/page/info?id=13825 vivo:https://dev.vivo.com.cn/wap/documentCenter/doc/1013 小米:https://dev.mi.com/xiaomihyperos/documentation/detail?pId=2304 参阅 https://android- developers.googleblog.com/2026/04/the-fourth-beta-of-android-17.html?m=1
❤1
Signed Tartarus
华为Mate 80 Pro性能测评解禁!
😁11❤1
Signed Tartarus
Loon的分流规则生成器 - Winodws版 这是我用Rust+Slint GUI库写的小工具,全程AI搞定,反正我也不懂一行代码😁 自动识别应用名称 自动过滤非iOS代理工具产生的假IP 支持子域合并 支持过滤系统应用 由于我没有macOS设备,所以只写了Winodws版。 详细的教程晚点发 🔗 可莉的插件中心 🔗 机场推荐 🔗 iOS 苹果上架服务 ❗️ 禁止中国境内传播 ✈️ 发布频道 @ibilibili #Software
❤1
Signed Tartarus
Showing the 12 most recent of 15 posts we hold for @HellCellZC123. 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.
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 3 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 14 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Hell Cell 功能教学” (@HellCellZC123), 10,849 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/HellCellZC123.
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.