此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道
👍5
Signed 全网收质量频道 @adggku

Channel
@GTQNB003
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
14,191subscribers
+3,606 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002778336587 |
|---|---|
| Type | Channel |
| Username | @GTQNB003 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/GTQNB003 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 35% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 6 other registered channels. This entry also sits inside a group of 56 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @GTQNB003/9027 · this entry9 Aug 2026, 14:07 UTC | @LMGWJWD6/402519 Aug 2026, 14:09 UTC | 1.00 | 72 seconds |
| @LMGWJWD6/4125717 Aug 2026, 13:45 UTC | @GTQNB003/9604 · this entry17 Aug 2026, 13:45 UTC | 1.00 | under a minute |
| @LMGWJWD6/4215224 Aug 2026, 15:25 UTC | @GTQNB003/10111 · this entry24 Aug 2026, 15:25 UTC | 1.00 | under a minute |
| @HUIYIYYDS6/3313224 Aug 2026, 15:25 UTC | @GTQNB003/10111 · this entry24 Aug 2026, 15:25 UTC | 1.00 | under a minute |
| @LMY1015/320395 Aug 2026, 00:45 UTC | @GTQNB003/8659 · this entry5 Aug 2026, 00:45 UTC | 1.00 | under a minute |
| @wjhshsne/812875 Aug 2026, 00:45 UTC | @GTQNB003/8660 · this entry5 Aug 2026, 00:45 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @LMGWJWD6 | 31 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @LMGWJWD6 (22–9) |
| @HUIYIYYDS6 | 33 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @HUIYIYYDS6 (21–12) |
| @LMY1015 | 28 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @LMY1015 (19–9) |
| @wjhshsne | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @wjhshsne (5–3) |
| @XiaoxueVkernel6 | 37 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @XiaoxueVkernel6 (24–13) |
| @HeixuePD6 | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @HeixuePD6 (10–7) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 167 comparable posts for this entry, running 21 June 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 56 channels, the one whose matching posts we hold earliest is @LMGWJWD. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 56 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
5 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 02:50 | 14,191 | +2 |
| 13 Nov 2026, 16:01 | 14,189 | +3 |
| 9 Nov 2026, 08:15 | 14,186 | -44 |
| 8 Nov 2026, 00:51 | 14,230 | +3 |
| 6 Nov 2026, 22:29 | 14,227 | +10 |
| 5 Nov 2026, 20:00 | 14,217 | -3 |
| 4 Nov 2026, 22:26 | 14,220 | -10 |
| 4 Nov 2026, 01:30 | 14,230 | -20 |
| 3 Nov 2026, 04:01 | 14,250 | -27 |
| 2 Nov 2026, 03:48 | 14,277 | +2 |
| 1 Nov 2026, 03:29 | 14,275 | -2 |
| 31 Oct 2026, 01:58 | 14,277 | -6 |
| 29 Oct 2026, 22:35 | 14,283 | -5 |
| 28 Oct 2026, 19:19 | 14,288 | +8 |
| 27 Oct 2026, 19:41 | 14,280 | +26 |
| 26 Oct 2026, 18:39 | 14,254 | -3 |
| 25 Oct 2026, 15:45 | 14,257 | +19 |
| 24 Oct 2026, 15:59 | 14,238 | +38 |
| 23 Oct 2026, 16:46 | 14,200 | +40 |
| 22 Oct 2026, 18:40 | 14,160 | first reading |
297 posts held, back to 21 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 76 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 16 November 2026 |
|---|---|
| Posts held | 297 (21 June 2026 – 16 November 2026) |
| Views total | 73,395 |
| Reactions total | 530 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 23:37 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 4 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.
1,186 reactions across 274 posts, in 5 distinct kinds. The most used accounts for 87.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,035 | 87.3% | |
| ❤ | 141 | 11.9% | |
| 🤔 | 7 | 0.59% | |
| 😁 | 2 | 0.169% | |
| 👎 | 1 | 0.084% |
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 280 of the 297 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 1,216 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 297 most recent posts we hold, published 21 June 2026 to 16 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: 8 of 64 posts held from the last 30 days (12.5%) 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).
此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道
👍5
Signed 全网收质量频道 @adggku
你们好 很抱歉 我的频道被人骗走了 今天正式回归,我将在今天晚上12点更新最强公益 注:只有加入频道才能获得 我的新频道: https://t.me/+RHS1HkYv-qU4YjY1
👍12
Signed 全网收质量频道 @adggku
失控进化公益: 1.频道跳转 2.人机动物单独调色 3.修复大飞机归位小飞 4.石头改成灰色,铁银色 5.物资位置上有个圆点 6.支持悬浮栏开关 网盘:https://drive.uc.cn/s/90c463ef7aed4?public=1 注:美化要搭配端口使用,否则拉一天。子追校验失败了重新初始化就行。 适配驱动:twt pat ks rt
👍8
光头强公益频道: 高能英雄: 功能介绍: 1.齐全的绘制 2.四种自瞄算法 3.硬件断点与PTE断点追踪 4.稳定的内存功能 注意事项: 1.除了被提交不可能10年 2.注意游戏这游戏绿玩非常极端觉得你有一点点嫌疑就去官方提交 3.闪退是不兼容 和平美化: 美化界属于很不错的美化了建议娱乐使用别到时候封号怪着怪那,我只是要做大公益满足每个人需求你不需要可以不开很简单道理 更新内容: 1.修复全局部分情况没效果问题 2.修复锁帧没效果问题 3.修复大厅异常判断导致的误写入导致的闪退问题 此版本必须用最新版配置文件 否则无效果! 迷你枪战精英: 本次更新: 1.适配最新版本 2.更换开火开镜判断 注意事项: 1.自瞄或追踪没效果请游戏内或大厅执行 三角洲解密: -修复vivo/天机 -修复部分人解密失效问题 -优化自瞄逻辑 -优化绘制流畅度 -几乎适配全机型 解密方式:算法解密 Udp解密 模拟解密等 丝滑流畅支持vk opengl…
👍8
葫芦娃11.0版本 更新和平坐标解密 葫芦娃PUBG更新内容 修复乘车绘制问题 相机信息读取调整 修复广角功能 修复广角绘制偏差问题 适配全球 台湾 越南 日韩服 修复绘制偶发轻微闪烁问题 有bug反馈评论区 葫芦娃公益频道: @HLWNHNB2 网盘更新下载: https://pan.baidu.com/s/11pxYvr9c5_ERtJuoCE_41Q?pwd=6666 葫芦娃频道点我加入 葫芦娃交流群 @PUBGMAMTLS 支持的可以去网盘下载了谢谢各位义父了❤️ 保存文件 然后再下载 以免出错❤️ #和平精英 #无畏契约 #pubg #内核 #三角洲
👍3❤1
此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道
👍3
Signed 全网收质量频道 @adggku
❤️ 纸飞机无法加载登录使用? 👍聊天群里 发送“ 签到 ” 获取专属代理 点我加入高速代理群聊获取代理
❤1👍1
Signed 阿呆 (全网收管理) @adggku
❤️ 纸飞机无法加载登录 👍聊天群里 发送“ 签到 ” 获取专属代理 点我加入高速代理群聊获取代理
👍13
Signed 阿呆 (全网收管理) @adggku
此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道
👍8
Signed 全网收质量频道 @adggku
1.三角洲行动国服 (DFM: China) 2.三角洲行动国际 (DFM: Global) 3.三角洲行动台湾 (DFM: Taiwan) 4.暗区突围国服 (UAM: China) 5.暗区突围国际 (UAM: Global) 6.使命召唤国服 (CODM: China) 7.使命召唤国际 (CODM: Global) 8.使命召唤台湾 (CODM: Taiwan) 9.穿越火线国服 (CFM: China) 10.穿越火线国际 (CFM: Global) 11.迷你世界全服 (MiniPVE: All) 12.王者荣耀国际 (SGAME: Google) 13.萤火突击渠道 (YHTJ: China) 14.萤火突击国际 (Lost Light: Global) 15.英雄联盟手游 (LOLM : China) 16.英雄联盟手游 (LOLM : Gogbal) 17.无畏契约手游 (Valorant : China) …
👍21
此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道
👍4🤔1
Signed 全网收质量频道 @adggku
1.三角洲行动国服 (DFM: China) 2.三角洲行动国际 (DFM: Global) 3.三角洲行动台湾 (DFM: Taiwan) 4.暗区突围国服 (UAM: China) 5.暗区突围国际 (UAM: Global) 6.使命召唤国服 (CODM: China) 7.使命召唤国际 (CODM: Global) 8.使命召唤台湾 (CODM: Taiwan) 9.穿越火线国服 (CFM: China) 10.穿越火线国际 (CFM: Global) 11.迷你世界全服 (MiniPVE: All) 12.王者荣耀国际 (SGAME: Google) 13.萤火突击渠道 (YHTJ: China) 14.萤火突击国际 (Lost Light: Global) 15.英雄联盟手游 (LOLM : China) 16.英雄联盟手游 (LOLM : Gogbal) 17.无畏契约手游 (Valorant : China) …
👍8
Showing the 12 most recent of 297 posts we hold for @GTQNB003. 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.
We recorded 4 posts on @GTQNB003 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. 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 15 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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“光头强公益内核通知频道” (@GTQNB003), 14,191 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/GTQNB003.
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.