Faker在吧务团队震慑与感召下主动投案
Signed Tartarus

Channel
@HellCellZC123
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
10,894subscribers
+9 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 |
| Description | YouTube视频教学频道 商务联系 @Tartarus2014 通过视频演示,讲解一些实用软件有用有趣的功能。 博主YouTube:http://bit.ly/HellCellYouTube 博主交流群:https://t.me/hellcell321 大家可以订阅一下,衷心感谢!撒花🎉 |
| Created | 16 February 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 55 |
| Confirmed unchanged | 1 time, most recently 10 November 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 16:39 | 10,894 | +5 |
| 9 Nov 2026, 04:16 | 10,889 | +10 |
| 7 Nov 2026, 21:07 | 10,879 | +1 |
| 6 Nov 2026, 17:37 | 10,878 | +2 |
| 5 Nov 2026, 17:01 | 10,876 | +2 |
| 4 Nov 2026, 17:00 | 10,874 | +2 |
| 3 Nov 2026, 18:49 | 10,872 | +6 |
| 2 Nov 2026, 16:40 | 10,866 | -2 |
| 1 Nov 2026, 13:10 | 10,868 | +3 |
| 31 Oct 2026, 12:44 | 10,865 | -1 |
| 29 Oct 2026, 09:54 | 10,866 | +2 |
| 27 Oct 2026, 06:58 | 10,864 | +4 |
| 26 Oct 2026, 09:09 | 10,860 | -1 |
| 25 Oct 2026, 12:41 | 10,861 | -2 |
| 24 Oct 2026, 15:45 | 10,863 | +3 |
| 23 Oct 2026, 15:08 | 10,860 | +2 |
| 22 Oct 2026, 15:55 | 10,858 | +12 |
| 21 Oct 2026, 08:59 | 10,846 | +5 |
| 20 Oct 2026, 08:56 | 10,841 | -2 |
| 19 Oct 2026, 05:27 | 10,843 | first reading |
35 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 59 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. It is computed over the 9 of 11 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 35 (15 June 2026 – 10 November 2026) |
| Views total | 25,150 |
| Reactions total | 22 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 10:06 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.
124 reactions across 24 posts, in 7 distinct kinds. The most used accounts for 40.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 50 | 40.3% | |
| 👍 | 38 | 30.6% | |
| ❤ | 16 | 12.9% | |
| 👎 | 8 | 6.45% | |
| 🌚 | 6 | 4.84% | |
| 😱 | 3 | 2.42% | |
| 🤡 | 3 | 2.42% |
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 29 of the 35 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 124 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 35 most recent posts we hold, published 15 June 2026 to 10 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: 1 of 11 posts held from the last 30 days (9.09%) 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).
Faker在吧务团队震慑与感召下主动投案
Signed Tartarus
屏幕上跳出下周五 -32℃ 的预报时,所有人都笑着说,是苹果天气又出bug了。 上一世的我,也是这么以为的。 等到寒潮毫无征兆倾覆城市,门窗结起厚冰,燃料耗尽,我在刺骨的寂静里失去意识。 再睁眼,我重新看见这条离谱的预报。 这一次我清楚,它不是故障,是末日提前递来的预警。
Signed Tartarus
https://nssurge.com/surge-ios-6 新刘可以啊 给surge搞了一套杀马特风 审美符合精神小伙
👍1
Signed Tartarus
Lightweight self-hosted web panel for Mihomo: listeners, users, subscriptions, SSL/ACME, Telegram, and multi-node cluster. Github:https://github.com/kazeyukiro/3m-ui 官网:https://3m-ui.top/
Signed Tartarus
喜欢我么? 刷新率是60Hz,SDR亮度600 尼特,HDR内容峰值亮度1200尼特的iPad mini? 仅仅5499起哦
👍7
Signed Tartarus
勇敢牛牛,不怕困难!
🌚6
Signed Tartarus
#Test #Loon4Mac Loon for Mac 0.5.0(1009)版本已准备好在 Mac OS上进行测试。 - 新增网关功能,具体功能和教程见:https://nsloon.app/blog/loon4mac-gateway - 新增 DHCP 功能,具体功能和教程见:https://nsloon.app/blog/loon4mac-dhcp - 优化进程规则,加入更多匹配方式,具体见:https://nsloon.app/docs/Rule/process_rule - 性能优化,最新版本在m1 max macbook 上的回环测试为:单流上传12G,单流下载 14G,具体测试结果和测试方式见:https://nsloon.app/blog/loon4mac-tcp-performance - 优化首页布局显示 - 合并最新版 iOS 功能 最新包下载地址:https://github.com/Loon0…
❤1
Signed Tartarus
开放模型。开放内核。开放推理。 从私有部署到公共云,我们将继续与社区合作,使大规模推理更高效。 探索代码、贡献力量,并与我们一起构建! https://x.com/deepseek_ai/status/2112476496283775135 梁大圣人哎
Signed Tartarus
安卓第三方TG的插件生态正在开枝散叶 不久之前,nagramXF、exteraless等第三方TG开始支持了插件生态,因为除了它们APP里自带的第三方功能,还有一些国内外大佬自发写的插件对于TG的使用也是非常有帮助。 但是,有些不明插件会把你的账号数据损毁,我就深受其害,结果是把我一个重要的备忘群和男娘群给彻底搞炸了,还自动给我退了很多群聊。所以,最好少装或者不装陌生插件,是各位使用之前需要警醒的点! 一、安装支持插件的第三方TG 目前主流有3个,我喜欢用nagramXF,秀儿姐喜欢用exteraless,ayugram目前我不怎么了解。 🏷exteraless 【 https://t.me/exteraless 】 秀儿姐说是切换效果比nagramXF用起来丝滑些,而且比nagramXF少一些bug,我试了也不错,更为推荐一些。 🏷nagramXF 正式版本群【 https://t.me/NagramXF 】 其中文件名…
❤2
Signed Tartarus
锁了一单 是这个吗 我看着挺像的 是我就付款了 凑个热闹 +1000出给你了
Signed Tartarus
Loon for Mac 网关功能即将到来
😁5
Signed Tartarus
无门槛红包,最高11111等你来抢 京东11.11,又便宜又好 抢购链接: https://u.jd.com/FOpj7UU
🤡3
Signed Tartarus
Showing the 12 most recent of 35 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 23 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“Hell Cell 功能教学” (@HellCellZC123), 10,894 subscribers as measured 10 November 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.