VT- PUBG公益1.1.5更新⚠️ 1.修复部分追踪开枪闪退 2.修复6.12内核陀螺仪用不了 3.修复自定义物资距离限制问题 4.修复狙击自瞄预判下坠问题 5.修复一些已知问题 6.新增追踪预判调节 7.新增追踪扫车预判调节 8.适配4.7.0版本 9.优化软锁模式 10.优化追踪预判 下载地址 🔴 https://drive.uc.cn/s/63feab1163424?public=1 讨论群组 @VTKernelhook
👍234❤1

Channel
@VTKernel
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Declared links · Cite this entry
105,912subscribers
+65,744 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1003669053186 |
|---|---|
| Type | Channel |
| Username | @VTKernel |
| Description | VT内核聊天群 @VTKernelhook 广告位联系 @xuezang886 双向联系 @xuezang886_bot |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/VTKernel |
Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 12 other registered channels. This entry also sits inside a group of 3 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 |
|---|---|---|---|
| @VTKernel/9088 · this entry8 Oct 2026, 04:32 UTC | @VTKernelNo/678 Oct 2026, 04:32 UTC | 1.00 | under a minute |
| @VTKernel/9198 · this entry13 Oct 2026, 15:54 UTC | @VTKernelNo/7113 Oct 2026, 15:54 UTC | 1.00 | under a minute |
| @VTKernel/9206 · this entry14 Oct 2026, 05:26 UTC | @VTKernelNo/7214 Oct 2026, 05:26 UTC | 1.00 | under a minute |
| @VTKernel/9328 · this entry18 Oct 2026, 16:11 UTC | @VTKernelNo/7318 Oct 2026, 16:11 UTC | 1.00 | under a minute |
| @VTKernel/9366 · this entry22 Oct 2026, 11:00 UTC | @VTKernelNo/7622 Oct 2026, 11:00 UTC | 1.00 | under a minute |
| @VTKernel/9452 · this entry27 Oct 2026, 09:33 UTC | @VTKernelNo/8127 Oct 2026, 09:33 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @VTKernelNo | 25 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @VTKernelNo (23–2) |
| @ASGA8 | 10 (8/8 hand-verifiable sample passed) | 1.00 | 13 hours | even |
| @LinYuKernel | 12 (8/8 hand-verifiable sample passed) | 1.00 | 18 hours | this entry (8–4) |
| @TwT_update | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @TwT_update (6–2) |
| @TwT_driver | 8 (8/8 hand-verifiable sample passed) | 1.00 | 13 hours | @TwT_driver (5–3) |
| @zwaaa333 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 13 hours | @zwaaa333 (4–2) |
| @kjyhhnb | 5 (5/5 hand-verifiable sample passed) | 1.00 | 18 hours | this entry (4–1) |
| @luoyenb521 | 20 (8/8 hand-verifiable sample passed) | 1.00 | 3.7 hours | @luoyenb521 (19–1) |
| @GROKZS | 8 (8/8 hand-verifiable sample passed) | 1.00 | 45 minutes | @GROKZS (5–3) |
| @HeiXuePD | 7 (7/7 hand-verifiable sample passed) | 1.00 | 3.3 hours | @HeiXuePD (6–1) |
| @hb52066 | 15 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @hb52066 (13–2) |
| @luoyeop | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @luoyeop (13–1) |
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. 54 of the 54 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 564 comparable posts for this entry, running 3 August 2026 to 10 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 3 channels, the one whose matching posts we hold earliest is @libai7072. 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 keys clone_copy · clone_mutual · clone_source, last confirmed 11 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 3 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 16:51 | 105,912 | +1,067 |
| 9 Nov 2026, 03:46 | 104,845 | +1,101 |
| 7 Nov 2026, 22:39 | 103,744 | +1,364 |
| 6 Nov 2026, 18:49 | 102,380 | +998 |
| 5 Nov 2026, 19:46 | 101,382 | +742 |
| 4 Nov 2026, 16:17 | 100,640 | +718 |
| 3 Nov 2026, 15:36 | 99,922 | +495 |
| 2 Nov 2026, 17:26 | 99,427 | +599 |
| 1 Nov 2026, 15:39 | 98,828 | +1,124 |
| 31 Oct 2026, 13:36 | 97,704 | +1,058 |
| 30 Oct 2026, 16:40 | 96,646 | +905 |
| 29 Oct 2026, 15:58 | 95,741 | +720 |
| 28 Oct 2026, 12:16 | 95,021 | +510 |
| 27 Oct 2026, 14:08 | 94,511 | +677 |
| 26 Oct 2026, 14:07 | 93,834 | +390 |
| 25 Oct 2026, 14:11 | 93,444 | +1,218 |
| 24 Oct 2026, 13:30 | 92,226 | +1,046 |
| 23 Oct 2026, 16:04 | 91,180 | +735 |
| 22 Oct 2026, 18:28 | 90,445 | +727 |
| 21 Oct 2026, 12:59 | 89,718 | first reading |
1,025 posts held, back to 3 August 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 196 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 11 November 2026 |
|---|---|
| Posts held | 1,025 (3 August 2026 – 11 November 2026) |
| Views total | 2,571,636 |
| Reactions total | 59,702 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 09:33 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 11 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.
Measured directly from 15 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.
111,537 reactions across 993 posts, in 49 distinct kinds. The most used accounts for 91.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 102,114 | 91.6% | |
| ❤ | 4,461 | 4.00% | |
| 😭 | 1,473 | 1.32% | |
| 🤔 | 487 | 0.437% | |
| 🤡 | 462 | 0.414% | |
| 🤬 | 434 | 0.389% | |
| 😱 | 298 | 0.267% | |
| 🔥 | 235 | 0.211% | |
| 🤯 | 212 | 0.19% | |
| 🕊 | 181 | 0.162% | |
| 😍 | 161 | 0.144% | |
| 😡 | 151 | 0.135% | |
| 🍌 | 116 | 0.104% | |
| 🤓 | 100 | 0.09% | |
| 😨 | 87 | 0.078% | |
| 😁 | 76 | 0.068% | |
| 👏 | 64 | 0.057% | |
| 🤪 | 54 | 0.048% | |
| 💯 | 48 | 0.043% | |
| 🤩 | 48 | 0.043% | |
| 29 further kinds | 275 | 0.247% |
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 996 of the 1,000 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 111,537 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 8 August 2026 to 11 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @VTKernel. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 8 August 2026 to 11 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 23 of 297 posts held from the last 30 days (7.74%) 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).
VT- PUBG公益1.1.5更新⚠️ 1.修复部分追踪开枪闪退 2.修复6.12内核陀螺仪用不了 3.修复自定义物资距离限制问题 4.修复狙击自瞄预判下坠问题 5.修复一些已知问题 6.新增追踪预判调节 7.新增追踪扫车预判调节 8.适配4.7.0版本 9.优化软锁模式 10.优化追踪预判 下载地址 🔴 https://drive.uc.cn/s/63feab1163424?public=1 讨论群组 @VTKernelhook
👍234❤1
开挂没号玩? 不敢用自己大号开挂? 害怕😨被封? 想体验皮肤? 想要游戏资产多的号? 想免费玩号? ❤️老八高质量三角洲数据号源头自营✔️ ➡️😃😃退游号😃😃高质量号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 ➡️全网最质量最低价格 最强售后😒 🥇一年诚信经营,三年售后兜底 😙😍😗😋😝🙃😜🤨😜 👍👍 ❤️主推-购买地址: https://buy.heevcmlz.cn/ ❤️备用2-购买地址 https://buy.sjhnb.com/ 上面两个卡网都可以用,哪个能打开用哪个 ❤️老八数据号官方频道:https://t.me/xcnb666 ✅客服:@djsjhnb6
👍218❤1🤡1🤬1
你游戏更新到最新版本了VT也要更新,你游戏没有更新你VT也不要更新
👍224🤡3🍌2
🔥HERO免费开盒助手🔥 🌈开盒专用🌈 🌈HERO户籍猎手 安装包下载链接 https://wwaqk.lanzoub.com/i7JQI4epmicb 密码:8888 🔨支持免费查询:手机号、身份证、QQ号、微信号、抖音号、银行卡、车牌号、邮箱、贴吧ID、微博ID、钉钉、快手、闲鱼号、小红书、网易云ID、脸书、推特、名下财产、开房记录、IMEI。涵括多元档案信息。支持模糊身份证、手机号补齐,支持全国猎魔/更多功能看软件详情... 🥰官方卡密售卖机器人⬇️⬇️ 👉 @ATC_AutoShop_Bot 👈 注: 最老猎手之一 也是唯一猎手其余仿冒 唯一权威官方频道 t.me/PLCOINP/8
👍210🤡2❤1🤔1
驱动刷不了的暂时在VT网盘下载驱动文件手动输入
👍196❤1🤔1
🎮三角洲 无畏契约 和平精英 CFM解密 落叶公益算法解密 已更新三角洲最新算法解密 不闪框 不漏人 不遁地 不协议 落叶自研队列明文MRA算法解密 动态解密算法 防止对局内二次加密 ✨点我验证落叶算法解密真实性 😀官方频道:@luoyenb521
👍201❤4
VT公益内核4.8.8更新⚠️ 1.修复了多个已知问题 下载地址 🔴 https://drive.uc.cn/s/63feab1163424?public=1 解密说明点我 自瞄说明等我 讨论群组 @VTKernelhook
👍209
👍-VT专业root刷机 😃😀😃最新PCation技术已经上线~ 😃元刷机!😃元刷机!😃元刷机! 🔹🔹🔹🔹🔹🔹🔹🔹🔹🔹🔹 ❤️三角洲不偏框不遁地 🎮暗区不偏不漏 🎮和平精英解决加密问题 ⭐全网最完美调度实测特训岛满人不掉帧状态功率占用率最低能耗稳定不发烫 🫥🫥🫥🫥🫥🫥🫥🫥🫥🫥🫥🫥 致力于各大游戏环境/检测完美服务 极致清理手机让您的手机焕然一新 服务渠道:咸鱼店铺点我跳转
👍199❤4🤔1
😃😀😃VT官方直营卡网 🥰我VT直接推出-0.4米福利号 🥰0.4米福利号-0.4米福利号-4米福利号 🥰0.4米福利号-0.4米福利号-4米福利号 🥰0.4米福利号-0.4米福利号-4米福利号 限时福利抢完既止 ➡卡网链接点我跳转 ➡卡网链接点我跳转
👍199🤔1
VT公益内核4.8.7更新⚠️ 1.修复自定义物资距离限制问题 2.修复狙击自瞄预判下坠问题 3.修复一些已知问题 4.新增敌人手雷落点预测 5.新增迫击炮落点预测 6.新增决斗协议道具绘制 7.新增一些新主题道具绘制 8.适配新疆阿勒泰版本 9.适配载具冰狼雪橇 10.适配M1887霰弹枪 11.优化自瞄算法 下载地址 🔴 https://drive.uc.cn/s/63feab1163424?public=1 解密说明点我 自瞄说明等我 讨论群组 @VTKernelhook
👍101❤18🤩3💯1
🔥HERO免费开盒助手🔥 🌈开盒专用🌈 🌈HERO户籍猎手 安装包下载链接 https://wwaqk.lanzoub.com/i7JQI4epmicb 密码:8888 🔨支持免费查询:手机号、身份证、QQ号、微信号、抖音号、银行卡、车牌号、邮箱、贴吧ID、微博ID、钉钉、快手、闲鱼号、小红书、网易云ID、脸书、推特、名下财产、开房记录、IMEI。涵括多元档案信息。支持模糊身份证、手机号补齐,支持全国猎魔/更多功能看软件详情... 🥰官方卡密售卖机器人⬇️⬇️ 👉 @ATC_AutoShop_Bot 👈 注: 最老猎手之一 也是唯一猎手其余仿冒 唯一权威官方频道 t.me/PLCOINP/8
👍132😍1
😃😀😃VT官方直营卡网 刚听说隔壁老光头整了个啥?0.5毛钱号,你们也想要是不是,老光头有的我vt粉丝必须有 🥰我VT直接推出-0.4米福利号 🥰0.4米福利号-0.4米福利号-4米福利号 🥰0.4米福利号-0.4米福利号-4米福利号 🥰0.4米福利号-0.4米福利号-4米福利号 限时福利抢完既止 ➡卡网链接点我跳转 ➡卡网链接点我跳转
👍154❤1😍1
Showing the 12 most recent of 1,025 posts we hold for @VTKernel. 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.
@VTKernel edited 4 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.
We recorded 7 posts on @VTKernel 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.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
要不要上架硬件断点版本(可能会拉闸因为有专门对此的检测)
The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
数据好售后好不好次此次投票确认
The shares total 107%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 8 August 2026 to 11 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 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.
@VTKernel named 4 handles 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“VicTorious公益内核频道” (@VTKernel), 105,912 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/VTKernel.
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.