关于管理员 [@Xiaozhe1337] 在本频道售卖 [小哲網截] 一事 本人说明如下: 该项目的宣传、收款均由 @Xiaozhe1337 个人操作,本人未参与任何环节,未收取一分钱。但作为频道主,我在人员审核上存在疏忽,监管责任我不会推卸。 给大家带来损失,我深表歉意。 如有其他问题可联系 @TANG0085 2026年9月2日
👍6🤬3
Signed 妙妙屋

Channel
@TNGHNB66
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
13,612subscribers
-449 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001606158340 |
|---|---|
| Type | Channel |
| Username | @TNGHNB66 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/TNGHNB66 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 18 Sept 2026, 14:15 | 13,612 | -15 |
| 16 Sept 2026, 03:17 | 13,627 | -8 |
| 14 Sept 2026, 07:55 | 13,635 | -12 |
| 12 Sept 2026, 18:56 | 13,647 | -19 |
| 10 Sept 2026, 20:37 | 13,666 | -34 |
| 7 Sept 2026, 19:37 | 13,700 | -37 |
| 4 Sept 2026, 22:38 | 13,737 | -8 |
| 3 Sept 2026, 10:02 | 13,745 | -20 |
| 2 Sept 2026, 06:53 | 13,765 | -1 |
| 1 Sept 2026, 03:27 | 13,766 | -4 |
| 31 Aug 2026, 00:07 | 13,770 | -2 |
| 29 Aug 2026, 23:02 | 13,772 | -13 |
| 28 Aug 2026, 23:48 | 13,785 | -8 |
| 27 Aug 2026, 22:12 | 13,793 | -3 |
| 27 Aug 2026, 00:58 | 13,796 | -7 |
| 26 Aug 2026, 03:42 | 13,803 | -18 |
| 25 Aug 2026, 04:48 | 13,821 | -14 |
| 24 Aug 2026, 01:05 | 13,835 | -39 |
| 22 Aug 2026, 11:36 | 13,874 | -21 |
| 20 Aug 2026, 22:18 | 13,895 | first reading |
48 posts held, back to 26 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 49 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 2 September 2026 |
|---|---|
| Posts held | 48 (26 June 2026 – 2 September 2026) |
| Views total | 16,560 |
| Reactions total | 143 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 19:47 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.
Measured directly from 6 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.
300 reactions across 45 posts, in 7 distinct kinds. The most used accounts for 74.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 224 | 74.7% | |
| ❤ | 65 | 21.7% | |
| 🤬 | 5 | 1.67% | |
| 🤩 | 3 | 1.00% | |
| 🎉 | 1 | 0.333% | |
| 👏 | 1 | 0.333% | |
| 🤯 | 1 | 0.333% |
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 46 of the 48 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 300 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 48 most recent posts we hold, published 26 June 2026 to 2 September 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.
关于管理员 [@Xiaozhe1337] 在本频道售卖 [小哲網截] 一事 本人说明如下: 该项目的宣传、收款均由 @Xiaozhe1337 个人操作,本人未参与任何环节,未收取一分钱。但作为频道主,我在人员审核上存在疏忽,监管责任我不会推卸。 给大家带来损失,我深表歉意。 如有其他问题可联系 @TANG0085 2026年9月2日
👍6🤬3
Signed 妙妙屋
挑战全网最速18杀
👍2
Signed 逆境
已无任何名额
👍3
Signed 逆境
————PUBG-CN———— 更新内容为 优化全部东西 更新3种解密方式 选择自动回退自动选择解密方案 (无断点) 更新ptebp 追踪 不在使用hwbp 我这里说一下 hwbp就是 市面上大部分项目的断点方式 但是我听说已经上检测 所以全部换成ptebp 除非上时序检测要不然不会拉闸 优化整体流畅度 驱动如果刷不上的建议换6系以上的使用 很多功能没加什么锁轮胎 迫击炮自瞄等等 没有必要的功能 其他该有的功能全部都有 后续可能更新防高风险 目前还在测试阶段 卡密跟瓦的 一样
👍3
Signed ollllll
一觉睡醒准度变高了🤓🤓
👍13❤1
Signed 呆呆
Android端网截 真正意义上的网截 局内随意全火 看权重 权重低 最低也能吃十多个举报局外才行为 无视所有垃圾环境 名额就三个 先到先得 有意联系 可开会议直播打 一把不杀天才直接死全家 @fengshenking
👍8
Signed 域
已修复所有问题 已优化完美udp抓包解密 移植pc自瞄算法 10枪中10枪 地图模型漏打 大地图雷达 接入twt驱动 永久卡密:@TNGHNB66 Bug反馈 @fengshenking
👍10
Signed 域
想第二天追10 ban机器码的找⬆️
👍11
Signed ollllll
也出成品 一机一特征
👍11
Signed 域
出售pc单内三角洲全功能 带共享雷达(前端后端带5个月低运高防服务器) 模拟人手曲线自瞄算法 非垃圾内存xy自瞄 全物资全干员 模型漏打 非算法模型 非劫持hook 自动查找特征码更新 无视所有更新 每个赛季查找非泛滥特征地址 自带acepass绕过 擦除pe 反截图/录屏 承诺200t死全家 当场/回溯10年死全家 有意带价来联系 @fengshenking
👍11
Signed 域
PC三角洲来人测试单机全功能
👍5
Signed 域
三角洲UDP➕坐标解密 地图模型漏打 大地图雷达 接入twt驱动 Bug反馈 @fengshenking
👍10
Signed 域
Showing the 12 most recent of 48 posts we hold for @TNGHNB66. 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.
@TNGHNB66 edited 3 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.
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.
@TNGHNB66 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.
References a handle that is not a live channel — we have no record it ever was one.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“妙妙屋通知频道” (@TNGHNB66), 13,612 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/TNGHNB66.
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.