正在搞新机
👍32

Channel
@windnb6
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,261subscribers
+4,102 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002181071863 |
|---|---|
| Type | Channel |
| Username | @windnb6 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/windnb6 |
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 13 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 |
|---|---|---|---|
| @windnb6/54 · this entry31 Jul 2026, 11:46 UTC | @CN_OnceHuman/493431 Jul 2026, 11:50 UTC | 1.00 | 5 minutes |
| @windnb6/60 · this entry2 Aug 2026, 08:29 UTC | @CN_OnceHuman/49872 Aug 2026, 08:44 UTC | 1.00 | 15 minutes |
| @windnb6/69 · this entry3 Aug 2026, 17:10 UTC | @CN_OnceHuman/50253 Aug 2026, 17:11 UTC | 1.00 | under a minute |
| @windnb6/140 · this entry14 Sept 2026, 07:23 UTC | @CN_OnceHuman/598914 Sept 2026, 07:33 UTC | 1.00 | 10 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @CN_OnceHuman | 7 (7/7 hand-verifiable sample passed) | 1.00 | 5 minutes | this entry (7–0) |
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 14 comparable posts for this entry, running 31 July 2026 to 24 October 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 2 channels, the one whose matching posts we hold earliest is @windnb6 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key 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 2 registered channels linked by matching posts. 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 |
|---|---|---|
| 16 Nov 2026, 07:57 | 6,261 | -10 |
| 10 Nov 2026, 10:59 | 6,271 | +6 |
| 6 Nov 2026, 21:40 | 6,265 | +2 |
| 4 Nov 2026, 06:58 | 6,263 | +1 |
| 1 Nov 2026, 13:39 | 6,262 | +13 |
| 29 Oct 2026, 08:57 | 6,249 | +33 |
| 26 Oct 2026, 05:17 | 6,216 | +97 |
| 23 Oct 2026, 04:16 | 6,119 | +100 |
| 19 Oct 2026, 23:07 | 6,019 | +84 |
| 17 Oct 2026, 04:46 | 5,935 | +58 |
| 13 Oct 2026, 22:38 | 5,877 | +83 |
| 8 Oct 2026, 06:21 | 5,794 | +118 |
| 1 Oct 2026, 10:38 | 5,676 | +576 |
| 16 Sept 2026, 07:16 | 5,100 | +285 |
| 12 Sept 2026, 08:36 | 4,815 | +989 |
| 8 Sept 2026, 08:58 | 3,826 | +156 |
| 3 Sept 2026, 08:56 | 3,670 | +31 |
| 31 Aug 2026, 04:27 | 3,639 | +49 |
| 27 Aug 2026, 20:47 | 3,590 | +57 |
| 24 Aug 2026, 22:14 | 3,533 | first reading |
48 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 6 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 6 November 2026 |
|---|---|
| Posts held | 48 (31 July 2026 – 6 November 2026) |
| Views total | 49,525 |
| Reactions total | 406 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 14:49 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 8 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.
865 reactions across 44 posts, in 16 distinct kinds. The most used accounts for 71.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 614 | 71.0% | |
| ❤ | 211 | 24.4% | |
| 🖕 | 9 | 1.04% | |
| 💋 | 6 | 0.694% | |
| 🤬 | 4 | 0.462% | |
| 👎 | 3 | 0.347% | |
| 🤡 | 3 | 0.347% | |
| 🤷♂ | 3 | 0.347% | |
| ❤🔥 | 2 | 0.231% | |
| 🍌 | 2 | 0.231% | |
| 💩 | 2 | 0.231% | |
| 🥰 | 2 | 0.231% | |
| 🐳 | 1 | 0.116% | |
| 👏 | 1 | 0.116% | |
| 😢 | 1 | 0.116% | |
| 🤯 | 1 | 0.116% |
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 44 of the 48 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 865 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 48 most recent posts we hold, published 31 July 2026 to 6 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: 3 of 16 posts held from the last 30 days (18.8%) 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).
正在搞新机
👍32
服务器到期了
👍28❤1
File, posted without a caption
👍16❤1😢1
File, posted without a caption
👍26🤬4
挂个死杂种: QQ号:3418193184 微信-电话:17783515482 李维鑫 500228200507285458 汉族 重庆市梁平区七星镇仁安村1组1号 王者排到的司马情侣 开局就狗叫
👍30❤7
开了台arm服务器修驱动兼容性
👍23🍌2🤯1
有需要改进的提交机器人,尽量详细点 有空了就修复@hhyhhk_bot
👍17
永劫无间 新功能 - 增加蓝顶、抓闪、抓振细项设置 - 增加抓蓄力后摇、受击、倒地、起跳、下蹲 - 增加自动断蓄 - 增加跳切打中后追击跳切 - 增加蓄力接近 优化 - 蓝顶、抓闪、抓振重做 - 修复按住蓄力松不开手 - 修复自动闪避失效 - 修复蓄力刚按就出白刀拼刀 - 被打中后能振3A - 修复弹刀时跳切失效 - 挥空后不再发呆 - 挨打起蓄不再被撤掉 - 被连段时会放逃脱技能 - 被击飞、起身时会放弦月 - 对手钩锁飞来会闪避 - 按对手武器判断够不够得着 - 挨打时不再后撤 失控进化 新功能 - 增加采集避开危险区和矿洞 - 增加炸家所需炸药数显示 - 补全物资和武器名称 优化 - 炸家路线改用游戏伤害数据 - 修复炸家路线不显示 - 炸家路线不再来回刷新 - 回家改为从家门进入 - 修复回家卡在门口左右转 - 修复隔墙开箱 - 修复到箱子前发呆 - 修复开箱后卡住、存不完 - 修复出门后往回走、撞墙 - 修复物资…
👍29❤16🖕1
永劫无间更新: - 增加手动跳切 - 增加闪避概率 - 增加冲刺1A - 增加切刀、跳切起手 - 增加挨打起蓄反打 - 增加钩锁连招 优化 - 蓝顶改为吃刀即放 - 自动闪避改为闪身 - 钩锁能钩中了 - 攻击距离按武器区分 - 不再跑到脸上才攻击 - 贴脸不再发呆 - 出刀后不再停顿 - 删除滑铲接近 - 挨打时不再放升龙 - 修复振刀自定义不生效 - 修复飞袭误振刀 - 修复离火下劈振不到 - 优化长剑3A振刀 - 修复天海钟绕圈、站着不动 - 修复连点跳跃跳切失效 固定卡密:windnb666 如果有bug请反馈频道机器人 主频道:https://t.me/windnb6
👍22❤5🖕3👎1
Video, posted without a caption
👍22❤1
给跳切修好了
👍21💩2
永劫无间 新功能 - 蓝顶抓A:1.0 前蓄力时,对手出白刀会自动松手反打。每把武器的延迟、距离可单独调。 - 抓闪:蓄到 1.0、2.0 时,对手闪避后自动松手,两档的延迟和距离分别可调,可用来规避闪身。 - 抓振刀:对手振刀(红光)后,延迟一会儿自动出蓄力,延迟和距离可调。 - 振刀概率:可设置每刀的振刀概率,每局随机,振刀更像真人。 - 物资页:新增左侧「物资」页,按魂玉、武器、果子、魂堆、补给、钥匙等大类分页,每样物资可单独开关,显示具体名称。 - 技能名显示:敌人的技能和奥义下方会显示名称,能看出对方带的是哪个版本。 优化 - 自动闪避改为长闪,无敌帧更长。 - 对手连招中不再翻滚贴脸。 - 修复放完技能后呆站。 - 修复打完连段后停顿,看着像人机。 - 修复对手出普通白刀时误判成蓝刀而站着挨打。 - 修复训练场中站着不追不打。 - 修复玩家昵称、人机名显示问号。 固定卡密:windnb666 如果有bug请反馈…
👍16❤7🖕1
Showing the 12 most recent of 48 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.
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 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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“Wind” (@windnb6), 6,261 subscribers as measured 16 November 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.