Telegram RegisterThe public register of Telegram
Telegram profile photo for VS内核官方频道

Channel

VS内核官方频道

@VSNH6

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

43,370subscribers

+3,105 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001346470846
TypeChannel
Username@VSNH6
Descriptionbug反馈 @Kelocyl 没有任何交流群 只有此频道 谨防上当受骗 只玩自己的和谁都不熟 不给任何人做担保
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live6 November 2026
Measurements held54
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/VSNH6

Topic

Software piracy — 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 60% 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.

Growth

39,48644,67642,08113 August 2026 — 40,265 subscribers14 August 2026 — 40,235 subscribers15 August 2026 — 40,081 subscribers17 August 2026 — 39,735 subscribers18 August 2026 — 39,605 subscribers19 August 2026 — 39,567 subscribers20 August 2026 — 39,510 subscribers21 August 2026 — 41,190 subscribers22 August 2026 — 42,005 subscribers24 August 2026 — 41,956 subscribers25 August 2026 — 41,922 subscribers26 August 2026 — 41,855 subscribers27 August 2026 — 41,836 subscribers28 August 2026 — 41,722 subscribers29 August 2026 — 41,428 subscribers30 August 2026 — 41,058 subscribers31 August 2026 — 40,898 subscribers1 September 2026 — 40,766 subscribers2 September 2026 — 40,633 subscribers3 September 2026 — 40,419 subscribers5 September 2026 — 40,189 subscribers8 September 2026 — 39,601 subscribers11 September 2026 — 42,095 subscribers13 September 2026 — 41,514 subscribers15 September 2026 — 40,989 subscribers17 September 2026 — 40,661 subscribers25 September 2026 — 44,676 subscribers3 October 2026 — 44,546 subscribers8 October 2026 — 44,488 subscribers12 October 2026 — 44,211 subscribers14 October 2026 — 44,017 subscribers15 October 2026 — 43,812 subscribers16 October 2026 — 43,749 subscribers17 October 2026 — 43,572 subscribers18 October 2026 — 43,596 subscribers19 October 2026 — 43,036 subscribers20 October 2026 — 42,959 subscribers21 October 2026 — 42,896 subscribers22 October 2026 — 42,120 subscribers23 October 2026 — 41,034 subscribers24 October 2026 — 40,715 subscribers25 October 2026 — 40,699 subscribers26 October 2026 — 40,385 subscribers27 October 2026 — 40,305 subscribers28 October 2026 — 40,045 subscribers29 October 2026 — 39,486 subscribers30 October 2026 — 44,277 subscribers31 October 2026 — 44,190 subscribers1 November 2026 — 44,055 subscribers2 November 2026 — 43,971 subscribers3 November 2026 — 43,946 subscribers4 November 2026 — 43,710 subscribers5 November 2026 — 43,617 subscribers6 November 2026 — 43,370 subscribers43,37013 August 20266 November 2026
54 measurements spanning 85 days, net +3,105. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 38,708–45,455 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 54
Measured (UTC)SubscribersChange
6 Nov 2026, 07:4943,370-247
5 Nov 2026, 10:3943,617-93
4 Nov 2026, 13:1743,710-236
3 Nov 2026, 12:0743,946-25
2 Nov 2026, 11:3543,971-84
1 Nov 2026, 13:0044,055-135
31 Oct 2026, 09:2744,190-87
30 Oct 2026, 09:4044,277+4,791
29 Oct 2026, 11:3739,486-559
28 Oct 2026, 12:2040,045-260
27 Oct 2026, 10:5940,305-80
26 Oct 2026, 12:2740,385-314
25 Oct 2026, 13:3740,699-16
24 Oct 2026, 11:4940,715-319
23 Oct 2026, 12:5641,034-1,086
22 Oct 2026, 15:4542,120-776
21 Oct 2026, 10:4842,896-63
20 Oct 2026, 08:5642,959-77
19 Oct 2026, 11:5443,036-560
18 Oct 2026, 10:5543,596first reading

Engagement

42 posts held, back to 31 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 159 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
14.0%
avg views ÷ 43,370 subscribers
Avg views / post
6,060
7 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
7
of 42 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 November 2026
Posts held42 (31 July 2026 – 3 November 2026)
Views total42,430
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 09:55 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.

What this channel posts

Photos
689
Videos
10
Links
90

Lifetime counters from Telegram’s own channel header, read 6 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.

Video runtime
11s
Average length
6s

Measured directly from 2 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 7 posts held from the last 30 days (28.6%) 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).

3 Nov 2026, 17:38 UTC≈3,220 viewsread 6 November 2026

⭐VS云更5.2 ➡️修复了闪框 有问题向 @Kelocyl 反馈🥰

1 Nov 2026, 08:15 UTC≈4,260 viewsread 6 November 2026
Photo

❤️2026年11月1日VS战神反馈,稳定奔放 💎点我进入官方卡网【复制在浏览器关闭VPN打开】 ⚠️ 本频道所有产品介绍点我(第一次玩必看) 💎当代理赚钱点我 💎没钱想免费玩点我 💎战绩反馈奖励点我 💎反馈问题点我 反馈/售后/举报低价/联系 @Kelocyl

30 Oct 2026, 14:59 UTC≈4,620 viewsread 6 November 2026

VS云更5.2 优化了部分设备卡顿 一加用户如果还是跑不满绘制帧率就去下个sc调度用ep就好了 有问题向 @Kelocyl 反馈

29 Oct 2026, 10:14 UTC≈7,030 viewsread 6 November 2026

如果你的设备出现帧率跑不满 跳的特别厉害 波动幅度特别大 可以向 @Kelocyl 反馈 截图你的关于本机: 描述掉帧与波动情况: 出现场景:训练营/局内主题/决赛圈 游戏是否出现掉帧:是/否

29 Oct 2026, 08:45 UTC≈7,150 viewsread 6 November 2026
Photo

❤️2026年10月9日-29日VS战神反馈,稳定奔放 💎点我进入官方卡网【复制在浏览器关闭VPN打开】 ⚠️ 本频道所有产品介绍点我(第一次玩必看) 💎当代理赚钱点我 💎没钱想免费玩点我 💎战绩反馈奖励点我 💎反馈问题点我 反馈/售后/举报低价/联系 @Kelocyl

29 Oct 2026, 08:45 UTC≈4,350 viewsread 31 October 2026
Photo

❤️2026年10月9日-29日VS战神反馈,稳定奔放 💎点我进入官方卡网【复制在浏览器关闭VPN打开】 ⚠️ 本频道所有产品介绍点我(第一次玩必看) 💎当代理赚钱点我 💎没钱想免费玩点我 💎战绩反馈奖励点我 💎反馈问题点我 反馈/售后/举报低价/联系 @Kelocyl

9 Oct 2026, 01:34 UTC≈11,800 viewsread 28 October 2026
Photo

❤️2026年10月9日VS战神反馈,稳定奔放 💎点我进入官方卡网【复制在浏览器关闭VPN打开】 ⚠️ 本频道所有产品介绍点我(第一次玩必看) 💎当代理赚钱点我 💎没钱想免费玩点我 💎战绩反馈奖励点我 💎反馈问题点我 反馈/售后/举报低价/联系 @Kelocyl

6 Oct 2026, 08:05 UTC≈12,600 viewsread 28 October 2026
Photo

❤️2026年10月6日VS战神9000淘汰分反馈,稳定奔放 💎点我进入官方卡网【复制在浏览器关闭VPN打开】 ⚠️ 本频道所有产品介绍点我(第一次玩必看) 💎当代理赚钱点我 💎没钱想免费玩点我 💎战绩反馈奖励点我 💎反馈问题点我 反馈/售后/举报低价/联系 @Kelocyl

5 Oct 2026, 09:52 UTC≈12,900 viewsread 28 October 2026

APK更新1.5(已下发云更新 无法云更用户可手动下载) 更新内如如下 1.优化排版和动画界面 2.修复了部分设备无法云更新APK 3.增加了防查(在应用伪装里)(支持自定义密码 这个密码只有你知道 不输入密码的情况下无法进入正常页面) 4.我们单独为一加/OPPO/真我设备添加了调度 如你绘制跑不满 可以在设置选项里找到调度点击开启(开启后有很明显提升 无效果可以多点几次 重启后需要重新开启 部分设备可能需要打开游戏后点击开启才有效果 ) 5.启动辅助后启动打开游戏且关闭APK(在启动程序下面 默认关闭 需要自己勾选) 网盘:https://1856559966.share.123pan.cn/123pan/O36rvd-fcgNA

5 Oct 2026, 09:50 UTC≈4,870 viewsread 9 October 2026
File

⭐目前最新驱动为2.0 ⭐辅助最新版本为4.9 ⭐APK最新版本为1.5 💎VS使用教程点我 💎应用伪装教程点我 💎账号备份教程点我 💎自定义物资教程点我 💎网盘下载链接点我 💎当代理赚钱点我 💎没钱想免费玩追锁版卡密点我 💎战绩反馈奖励点我 💎反馈问题点我 💎自瞄版公益卡密 @VSNH6 💎追踪版公益卡密 @VSNH6 💎追锁版提卡: https://shop.368fk.cn/shop/74S7KS0T

1 Oct 2026, 16:07 UTC≈8,130 viewsread 9 October 2026
Photo

❤️2026年10月2日VS战神反馈,稳定奔放 💎点我进入官方卡网【复制在浏览器关闭VPN打开】 ⚠️ 本频道所有产品介绍点我(第一次玩必看) 💎当代理赚钱点我 💎没钱想免费玩点我 💎战绩反馈奖励点我 💎反馈问题点我 反馈/售后/举报低价/联系 @Kelocyl

30 Sept 2026, 17:19 UTC≈6,830 viewsread 6 October 2026
Photo

❤️2026年10月1日VS战神反馈,稳定奔放 💎点我进入官方卡网【复制在浏览器关闭VPN打开】 ⚠️ 本频道所有产品介绍点我(第一次玩必看) 💎当代理赚钱点我 💎没钱想免费玩点我 💎战绩反馈奖励点我 💎反馈问题点我 反馈/售后/举报低价/联系 @Kelocyl

Showing the 12 most recent of 42 posts we hold for @VSNH6. 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.

Posts edited after publishing

@VSNH6 edited 2 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.

First edit seen
28 August 2026
Most recent edit
1 October 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @VSNH6 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.

First seen missing
25 August 2026
Most recent seen missing
25 August 2026
Median time before seen missing
21 days
Seen missing in the last 30 days
0

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 4 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.

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.

Cite this entry

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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“VS内核官方频道” (@VSNH6), 43,370 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/VSNH6.

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.