🤩情话人物范围31.0(lua版) 支持功能: 11.11全新范围思路 全自动lua文件 范围大小可以自调 0.80-0.60全身环绕范围 0..50-0.25头部环绕范围 全枪软锁(软锁神力) 人物掩体变色内透 人物全皮肤lua美化 软锁搭配范围稳定乱穿 全枪范围 支持裸奔 支持全模式(地铁或者经典) 蓝圈记得导入原版 使用方法: 公告导入功能 经典大厅删掉功能 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #情话
👍3

Channel
@NL666NB
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
8,246subscribers
-900 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002249750467 |
|---|---|
| Type | Channel |
| Username | @NL666NB |
| Description | 欢迎各位加入「奶龙收集文件」 认准 8.2 K 频道 谨防上当受骗 让每个学生党都玩得上文件 永远保持公益 网盘只是为了生活 合作/反馈 @XEZLH 交流群 @qwgwjnb 感谢各位一直以来的选择【为玩家服务】 —————————————————— •本频道严格遵守 Telegram 规则 •本频道不涉及任何违法犯罪活动 •本频道坚持履约行使合规审计义务 @ Telegram 官方,涉及本频道投诉实为同行恶意竞争所作。若需要您可随时联系,我方定全力配合贵司工作! |
| Created | Between 1 June 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/NL666NB |
Gaming — 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 96% 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 54 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 |
|---|---|---|---|
| @qwgwj666/128763 Aug 2026, 03:27 UTC | @NL666NB/19765 · this entry3 Aug 2026, 03:27 UTC | 1.00 | under a minute |
| @qwgwj666/129198 Aug 2026, 04:23 UTC | @NL666NB/19788 · this entry8 Aug 2026, 04:24 UTC | 1.00 | 72 seconds |
| @qwgwj666/1293510 Aug 2026, 05:30 UTC | @NL666NB/19799 · this entry10 Aug 2026, 05:31 UTC | 1.00 | under a minute |
| @qwgwj666/1293710 Aug 2026, 05:30 UTC | @NL666NB/19801 · this entry10 Aug 2026, 05:31 UTC | 1.00 | under a minute |
| @qwgwj666/1294412 Aug 2026, 06:53 UTC | @NL666NB/19806 · this entry12 Aug 2026, 06:56 UTC | 1.00 | 3 minutes |
| @qwgwj666/1297515 Aug 2026, 04:43 UTC | @NL666NB/19832 · this entry15 Aug 2026, 04:43 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @qwgwj666 | 169 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @qwgwj666 (169–0) |
| @SNGF666888 | 137 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (132–5) |
| @apple666o | 81 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (81–0) |
| @yannb6 | 20 (8/8 hand-verifiable sample passed) | 1.00 | 45 hours | this entry (20–0) |
| @HUIYIYYDS6 | 17 (8/8 hand-verifiable sample passed) | 1.00 | 45 hours | this entry (17–0) |
| @LMGWJWD6 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 45 hours | 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. 165 of the 174 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 195 comparable posts for this entry, running 3 August 2026 to 11 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 54 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 keys clone_copy · clone_source, last confirmed 12 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 54 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.
3 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 17:36 | 8,246 | -34 |
| 5 Nov 2026, 01:50 | 8,280 | -17 |
| 2 Nov 2026, 05:48 | 8,297 | -20 |
| 30 Oct 2026, 01:47 | 8,317 | -21 |
| 27 Oct 2026, 04:49 | 8,338 | -28 |
| 23 Oct 2026, 19:18 | 8,366 | -36 |
| 20 Oct 2026, 09:08 | 8,402 | -14 |
| 17 Oct 2026, 14:00 | 8,416 | -24 |
| 14 Oct 2026, 14:08 | 8,440 | -26 |
| 11 Oct 2026, 01:20 | 8,466 | -38 |
| 5 Oct 2026, 06:14 | 8,504 | -62 |
| 26 Sept 2026, 08:40 | 8,566 | -93 |
| 17 Sept 2026, 20:37 | 8,659 | -19 |
| 13 Sept 2026, 20:17 | 8,678 | -28 |
| 9 Sept 2026, 20:20 | 8,706 | -39 |
| 4 Sept 2026, 16:38 | 8,745 | -29 |
| 1 Sept 2026, 07:06 | 8,774 | -18 |
| 29 Aug 2026, 15:34 | 8,792 | -19 |
| 27 Aug 2026, 00:24 | 8,811 | -34 |
| 24 Aug 2026, 10:35 | 8,845 | first reading |
197 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 48 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 | 197 (3 August 2026 – 11 November 2026) |
| Views total | 1,989 |
| Reactions total | 229 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 13:26 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 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
378 reactions across 146 posts, in 3 distinct kinds. The most used accounts for 96.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 365 | 96.6% | |
| ❤ | 9 | 2.38% | |
| 😍 | 4 | 1.06% |
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 146 of the 197 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 378 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 197 most recent posts we hold, published 3 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.
Telegram’s own ‘edited’ marker: 0 of 52 posts held from the last 30 days (0%) 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).
🤩情话人物范围31.0(lua版) 支持功能: 11.11全新范围思路 全自动lua文件 范围大小可以自调 0.80-0.60全身环绕范围 0..50-0.25头部环绕范围 全枪软锁(软锁神力) 人物掩体变色内透 人物全皮肤lua美化 软锁搭配范围稳定乱穿 全枪范围 支持裸奔 支持全模式(地铁或者经典) 蓝圈记得导入原版 使用方法: 公告导入功能 经典大厅删掉功能 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #情话
👍3
🤩喜喜盒瓶【穷途末路】第三剑 ❤️支持功能: ✅ 头部、腿部、身体部位识别模拟 ✅ 全枪械范围参数适配 ✅ SAV / JSON 范围配置示例 ✅ 动态目标跟随训练模块 ✅ 目标识别与追踪演示 ✅ 腰射子弹散布参数调节 ✅ 后坐力模拟降低 ✅ 视角抖动参数优化 ✅ 腰射集中度训练 ✅ 开镜速度参数配置 ✅ 射速参数模拟 ✅ 枪械稳定性模块 ✅ 弹道手感平滑增强 ✅ 辅助减少枪械后坐力 ✅ 辅助减少枪械部分抖动 ✅ AI 平滑瞄准模拟 ✅ 目标识别与追踪演示 ✅ 动态目标跟随训练 ✅ 瞄准速度参数调节 ✅ 触摸操作训练方案 ✅ Java / C++ 训练模块设计 ✅ 智能锁定响应优化 ✅ AI 平滑只需激发即可锁住敌人 ✅ 自瞄速度加快增强 ✅ 配置参数精细化✅ 设备性能适配 ✅ 运行稳定性优化✅ 个性化参数调整 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #喜喜
👍3
🤩LK全皮肤美化2.8版本 修复了部分bug 适配最新版本 部分模式没适配等下午 绿洲模式枪械配件 绿洲模式枪皮 主页显示枪皮和载具 大厅枪皮载具显示 大厅枪械配件和枪械专属动作 适配荣都 山谷 雨林地图 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #LK
👍3
🤩九七和平新版本V67 ❤️支持功能: ✅53°平滑拉抢自瞄 ❤️辅助瞄准范围增大 ✅新思路+经典+地铁-有效 ✅演戏对局防巡查 📱新增独家其玖柒思路 📱聚点 无后 快切 防抖 🎚支持枪械: 🟢AKM🟢AUG🟢M416 🟢M762🟢SCAR🟢QBU 🟢MK14🟢Mk47🟢QBZ ⚠️更新思路大幅提升稳定 ⚠️设备黑了请刷机后使用 👍稳定性:97% 搭配端口 ✅大厅/桌面替换替换两次 ✅蓝圈/局内替换原版 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #期九期
👍3
🤩情话和平自用v67 支持功能: 无后100% 防抖100% 十字架100% 快速切枪 强锁自瞄 人物全皮肤美化 人物物资内透 人物绘制内透 密钥内透 人物广角 有效枪械: AUG MK QBZ SKS TMP UMP45 UZI M16A4 法玛斯 AWM G36C M249 AKM M762 M249 狗砸 维克多 死噶 使用方法: 公告导入功能 局内导入原版 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #情话
👍6
🤩九七和平新版本V66 ❤️支持功能: ✅69°强锁拉抢自瞄 ❤️辅助瞄准范围增大 ✅新思路+经典+地铁-有效 ✅演戏对局防巡查 📱新增独家其玖柒思路 📱聚点 无后 快切 🎚支持枪械: 🟢AKM🟢AUG🟢M416 🟢M762🟢DP28🟢Groza 🟢M249🟢SLR🟢SKS ⚠️更新思路大幅提升稳定 ⚠️设备黑了请刷机后使用 👍稳定性:95% 搭配端口 ✅大厅/桌面替换替换两次 ✅蓝圈/局内替换原版 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #期九期
👍6
🤩风屿V45[最大化]乱杀版 👑 风屿配置 V45【最大化】 MAX EDITION · 巅峰进阶版 📅 版本:V45🔥 版本主题:最大化 ✅ 头部、腿部、身体部位识别模拟 ✅ 全枪械范围参数适配 ✅ SAV / JSON 范围配置示例 ✅ 动态目标跟随训练模块 ✅ 目标识别与追踪演示 ✅ 腰射子弹散布参数调节 ✅ 后坐力模拟降低 ✅ 视角抖动参数优化 ✅ 腰射集中度训练 ✅ 开镜速度参数配置 ✅ 射速参数模拟 ✅ 枪械稳定性模块 ✅ 弹道手感平滑增强 ✅ 辅助减少枪械后坐力 ✅ 辅助减少枪械部分抖动 ✅ AI 平滑瞄准模拟 ✅ 目标识别与追踪演示 ✅ 动态目标跟随训练 ✅ 瞄准速度参数调节 ✅ 触摸操作训练方案 ✅ Java / C++ 训练模块设计 ✅ 智能锁定响应优化 ✅ AI 平滑只需激发即可锁住敌人 ✅ 自瞄速度加快增强 ✅ 配置参数精细化✅ 设备性能适配 ✅ 运行稳定性优化✅ 个性化参数调整 ✅以上功能100%稳定…
👍6
🤩XW秒刷美化正式版2.9 地铁训练场实体传世武器 大飞机 彩色名字 全网首发召唤大飞机效果 地铁仓库美化 地铁"实体"效果 出生岛名字logo 炫彩颜色 全局名字更换 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #XW
👍6
🤩情话和平古墓自用v10 支持功能: 无后100% 防抖100% 十字100% 快速切枪 强锁自瞄 平滑自瞄 人物全皮肤美化 人物绘制透视 无跳弹 支持裸奔 支持全模式 有效枪械: M4 AK AKM QBZ M249 M762 蜜獾 AKS74U UMP45 SKS UZI S12K G36C M16A4 UZI AKS74U 法玛斯 死噶 MG36 M24 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #情话
👍5
🤩九七和平新版本V65 ❤️支持功能: ✅47°平滑拉抢自瞄 ❤️辅助瞄准范围增大 ✅新思路+经典+地铁-有效 ✅演戏对局防巡查 📱新增独家其玖柒思路 📱聚点 无后 快切 🎚支持枪械: 🟢AKM🟢AUG🟢M416 🟢M762🟢M249🟢Groza 🟢M16a4🟢MK14🟢SCAR ⚠️更新思路大幅提升稳定 ⚠️设备黑了请刷机后使用 👍稳定性:97% 搭配端口 ✅大厅/桌面替换替换两次 ✅蓝圈/局内替换原版 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #期九期
👍5
🤩喜喜盒瓶【穷途末路】第二剑 【地铁/经典/创意工坊|手感调校方案】 ✅锁定优先级:头部→颈部→胸腔 ✅目标判定适配范围 +80% ✅瞄准框适配幅度 +180% ✅轮廓识别缓冲区间 24cm ✅预瞄预判响应 0.4s ✅队友识别过滤 100% ✅载具跟枪持续跟随 ✅静默吸附角度 12° ✅边缘柔和过渡区 3.5° ✅中心跟枪黏滞强度 +45% ✅开镜黏滞增益 +12%|腰射黏滞增益 +38% ✅画面外目标衔接锁定 ✅三路目标轮换跟枪 ✅目标切换牵引顺滑度 +60% ✅甩枪角速度上限 340°/s ✅弹道预修正强度 +70% ✅提前量预判 1.2身位 ✅后坐力反向补偿 -92% ✅枪口散布抑制 -48% ✅手感微抖模拟 ±1.8° ✅操作容错缓冲 8% ✅命中率柔和上限 87% ✅鼠标贝塞尔轨迹平滑 ✅跟枪响应窗口 0.02s 适配枪械: 全步枪|全冲锋枪|全射手步枪 ✅稳定性拉满 ✅修复多设备闪退、配置失效问题 ✅适配全客户…
👍5
🤩LK全皮肤美化2.7版本 修复了部分bug 提升稳定性 绿洲模式枪械配件 绿洲模式枪皮 主页显示枪皮和载具 大厅枪皮载具显示 大厅枪械配件和枪械专属动作 适配荣都 山谷 雨林地图 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #LK
👍5
Showing the 12 most recent of 197 posts we hold for @NL666NB. 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.
@NL666NB edited 1 post 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.
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.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“奶龙泛滥改文件🇨🇳” (@NL666NB), 8,246 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/NL666NB.
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.