NL项目高分反馈 点我进入官方卡网🥰 当代理赚大米点我🧸 咨询/反馈/售后服务/举报低价点我🥰
👍4❤1

Channel
@ZXGNB6
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Declared links · Cite this entry
5,979subscribers
-105 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002634384191 |
|---|---|
| Type | Channel |
| Username | @ZXGNB6 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/ZXGNB6 |
Hacking & security — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 |
|---|---|---|
| 5 Nov 2026, 01:16 | 5,979 | -4 |
| 1 Nov 2026, 18:58 | 5,983 | -9 |
| 30 Oct 2026, 00:47 | 5,992 | -9 |
| 26 Oct 2026, 22:41 | 6,001 | -12 |
| 23 Oct 2026, 20:39 | 6,013 | -9 |
| 14 Oct 2026, 22:10 | 6,022 | +5 |
| 11 Oct 2026, 06:57 | 6,017 | -25 |
| 5 Oct 2026, 00:19 | 6,042 | -9 |
| 26 Sept 2026, 05:57 | 6,051 | -18 |
| 15 Sept 2026, 17:41 | 6,069 | -1 |
| 12 Sept 2026, 08:21 | 6,070 | -14 |
| 8 Sept 2026, 01:57 | 6,084 | -6 |
| 2 Sept 2026, 14:37 | 6,090 | +2 |
| 30 Aug 2026, 16:28 | 6,088 | +6 |
| 27 Aug 2026, 15:39 | 6,082 | +1 |
| 24 Aug 2026, 09:02 | 6,081 | -8 |
| 20 Aug 2026, 22:44 | 6,089 | -4 |
| 17 Aug 2026, 23:35 | 6,093 | -6 |
| 15 Aug 2026, 09:04 | 6,099 | -4 |
| 12 Aug 2026, 02:43 | 6,103 | first reading |
8 posts held, back to 25 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 7 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 November 2026 |
|---|---|
| Posts held | 8 (25 July 2026 – 2 November 2026) |
| Views total | 431 |
| Reactions total | 31 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 01:00 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.
38 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 89.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 34 | 89.5% | |
| ❤ | 3 | 7.89% | |
| 🥰 | 1 | 2.63% |
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 6 of the 8 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 38 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 25 July 2026 to 2 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: 0 of 3 posts held from the last 30 days (0%) 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).
NL项目高分反馈 点我进入官方卡网🥰 当代理赚大米点我🧸 咨询/反馈/售后服务/举报低价点我🥰
👍4❤1
不好意思反馈有点多
👍12
Photo, posted without a caption
👍14
VS内核4.4云更新 1.修复解密漏打失效/修复漏打偶尔失效 2.优化辅助流畅度 3.修复载具只能一键开不能一键关 4.增加追踪内置打鸟预判(遇到傻逼直接打就行) 5.增加手雷预测和手雷落点和瞬爆倒计时(瞬爆倒计时在准心的左边)(手雷预测线默认红 瞄准敌人变成绿色就是能炸到的意思 直接丢就行) 6.增加血条变色(默认漏了红没漏黄 想要以前的纯绿就把漏和没漏都改成绿色就行) 7.更改死亡盒子显示目前为(xxx的盒子X米) 有bug请重置配置使用 有bug请重置配置使用 有bug请重置配置使用 追锁未到期用户加时6小时 自瞄/追踪用户等待服务器恢复
❤1👍1
身份证反馈
👍3❤1
https://v.kuaishou.com/KULhSt6c 疑似赛季初手机天花板 "9000淘汰分 "赛季初一天封神 "今天一穿四了吗 "vs耳机 该作品在快手被播放过19次,点击链接,打开【快手】直接观看!
🥰1
Photo, posted without a caption
Photo, posted without a caption
Showing the 8 most recent of 8 posts we hold for @ZXGNB6. 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.
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.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“秋白·项目主频道🇨🇳” (@ZXGNB6), 5,979 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ZXGNB6.
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.