Telegram RegisterThe public register of Telegram
Telegram profile photo for Wind

Channel

Wind

@windnb6

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

3,229subscribers

+1,070 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002181071863
TypeChannel
Username@windnb6
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/windnb6

Growth

2,1593,2292,6947 August 2026 — 2,159 subscribers7 August 2026 — 2,159 subscribers8 August 2026 — 2,196 subscribers10 August 2026 — 2,527 subscribers14 August 2026 — 2,890 subscribers17 August 2026 — 3,229 subscribers7 August 202617 August 2026
6 measurements spanning 10 days, net +1,070. 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 1,999–3,390 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 23:023,229+339
14 Aug 2026, 16:322,890+363
10 Aug 2026, 22:052,527+331
8 Aug 2026, 02:012,196+37
7 Aug 2026, 15:472,159no change
7 Aug 2026, 15:332,159first reading

Engagement

12 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
54.2%
avg views ÷ 3,229 subscribers
Avg views / post
1,750
12 posts measured
Reaction rate
0.426%
reactions ÷ views · ER floor
Posts in window
12
of 12 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. It is computed over the 9 of 12 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held12 (31 July 20266 August 2026)
Views total21,011
Reactions total66
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 15: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.

What this channel posts

Video runtime
3m 00s
Average length
1m 00s

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

Reaction mix

66 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 77.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5177.3%
👍1319.7%
🥰23.03%

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 9 of the 12 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 66reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 31 July 2026 to 6 August 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.

Recent posts

4 Aug 2026, 13:00 UTC≈1,500 views16 reactionsread 7 August 2026
File

失控进化更新: 新增大地图领地柜归属 修复部分玩家骨骼固定在错误位置的问题。 永劫无间更新: 修复 3A 识别异常 增加重刃 2A 蓝霸体识别 优化不同距离下的振刀延迟 修复部分配置下只闪避、不振刀的问题 修复蓝霸体、3A、惊雷被全局防御模式错误覆盖的问题 优化振刀优先级,识别到可振窗口时优先振刀 修复先闪后振导致振刀时机过晚的问题 修复旧配置异常导致防御模式错误的问题 驱动更新: 新增sad驱动支持,自动采集不兼容,等待更新 新增音量键+控制菜单 固定卡密:windnb666 如果有bug请反馈频道机器人 主频道:https://t.me/windnb6

16

3 Aug 2026, 17:10 UTC≈1,770 views6 reactionsread 7 August 2026
File

失控进化更新: 修复自动采集切换工具异常问题 永劫无间更新: 优化完善武器振刀 目前已知bug: 训练营3a识别异常 实战好像正常 新增CFM: 单骨骼透视 关于驱动适配和陀螺仪问题等下个版本修复 固定卡密:windnb666 如果有bug请反馈频道机器人 主频道:https://t.me/windnb6

5👍1

3 Aug 2026, 11:37 UTC≈1,750 views5 reactionsread 7 August 2026
Video

基本覆盖全武器,还有一些乱七八糟的小问题

5

2 Aug 2026, 09:11 UTC≈1,890 viewsread 7 August 2026

驱动卡死的自己换一个驱动看看,都不支持我也没办法了。目前没有更新wind驱动的计划 没啥时间

2 Aug 2026, 08:29 UTC≈2,050 views14 reactionsread 7 August 2026
File

失控进化更新: 增加领地柜-门框-箱子3D方框 优化2D雷达显示调整 修复自瞄追踪选不中人bug 修复绘制自身bug 更换菜单渲染为Vulkan 自动解密改成手动,移动至功能页 永劫无间更新: 优化完善部分武器振刀(完成度低) 有好的建议可以反馈 需要进游戏再开辅助(下次修复) 如果出现没效果的话重启一下游戏能解决 驱动支持更新: 支持TwT--rt驱动,在登录页进行选择 twt支持全功能 但是有点卡 rt只支持透视陀螺仪自瞄 永劫请使用twt。频道过验证自己找一下 固定卡密:windnb666 如果有bug请反馈频道机器人 主频道:https://t.me/windnb6

8👍5🥰1

2 Aug 2026, 08:29 UTC≈1,670 views4 reactionsread 7 August 2026

关于永劫帮助完善方式: 设置-调试-采集数据,然后进行一段操作复现,训练营的自定义操作 完成之后关闭数据采集,复述武器招式并把下面的gz文件发送到机器人 /data/local/tmp/output/naraka_combat_dataset.jsonl.gz

4

31 Jul 2026, 11:46 UTC≈2,420 views12 reactionsread 7 August 2026
Photo

失控进化更新: 重构菜单UI 修复人机骨骼显示异常 增加2d固定雷达,大地图雷达 增加陀螺仪自瞄 重构自动采集(支持自动进食自动找食物自动避开野怪) 全自动采集回家放物品(测试中) 增加玩家列表,可加黑加白 增加断点切换第三人称 增加断点解锁120fps 修复自动解密(算法) 新增永劫无间: 骨骼--萤火虫 透视 长剑-太刀振刀(等待优化) 有搞玩的话可以把一些连招告诉我 驱动更新: 修复稳定性 修复读取效率异常 修复长时间运行重启 追踪乱射封号这种自己找个端口 可以不开 但是不能没有 固定卡密:windnb666 如果有bug请反馈频道主 主频道:https://t.me/windnb6

9👍2🥰1

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

Citation-graph rank

Citation-graph rank — 345,628 of 1,549,704entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 1 registered channel — 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.

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

“Wind” (@windnb6), 3,229 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/windnb6.

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.