#更新 🏥增加医疗发票业务(主要出医疗但实际是所有发票都可以出) 积分消耗:普通用户20积分 会员免费 指令:/ylfp 姓名 身份号 🪪 增加营业执照查询 真实数据 并非ps图片 积分消耗:普通用户10积分 会员免费 指令:/yyzz 统一社会信用代码 ⭐️优化了部分ui 看着更整洁 诺纹一直在前进,希望前进之路有您的相伴,感谢使用与支持 官方客服/商家投诉建议:@nwadmin_bot

Channel
诺纹官方通知频道
@nwsgk
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
13,018subscribers
+1,084 since we began measuring on 7 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002546691328 |
|---|---|
| Type | Channel |
| Username | @nwsgk |
| Created | 18 March 2025 — measured — dated from the channel’s first post |
| First recorded | 7 September 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 28 September 2026 |
| On Telegram | t.me/nwsgk |
Topic
Hacking & security — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 05:59 | 13,018 | +464 |
| 17 Sept 2026, 21:37 | 12,554 | +101 |
| 15 Sept 2026, 16:57 | 12,453 | +84 |
| 13 Sept 2026, 23:19 | 12,369 | +155 |
| 12 Sept 2026, 07:00 | 12,214 | +64 |
| 10 Sept 2026, 05:16 | 12,150 | +216 |
| 7 Sept 2026, 07:22 | 11,934 | no change |
| 7 Sept 2026, 06:48 | 11,934 | first reading |
Engagement
16 posts held, back to 18 March 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.51%
- avg views ÷ 13,018 subscribers
- Avg views / post
- 457
- 4 posts measured
- Reaction rate
- 0.326%
- reactions ÷ views · ER floor
- Posts in window
- 5
- of 16 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 2 of 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 September 2026 |
|---|---|
| Posts held | 16 (18 March 2025 – 7 September 2026) |
| Views total | 1,826 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Sept 2026, 07:22 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.
Reaction mix
4 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 50.0% | |
| 😁 | 1 | 25.0% | |
| 🤣 | 1 | 25.0% |
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 2 of the 16 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 18 March 2025 to 7 September 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
📣📣定位恢复 优化普通查询排序 尽情开户吧,邪恶的恶俗者😀 定位指令 /dw 18888888888
👍2😁1
定位维护两小时 已完成
✅重磅更新 手机定位(已接入高德地图) 🔥全网独家首发 在机器人 @nwsgkbot 发送/start 刷新定位功能 指令:/dw 18888888888 积分消耗:普通用户20积分/会员10积分 签到/邀请用户获得积分即可白嫖,有实力的用户可以进行赞助 🌐诺纹只服务客户,更新不间断,请持续保持关注 (根据基站分析出位置) 此功能是基站直出,位置可能会存在偏差,近期位置 “你以为一个手机号只有归属地?” 在诺纹社工库里,输入手机号后: ▸ 三网运营商识别 ▸ 归属地解析 ▸ 地图位置可视化 ▸ 数据关联分析 ▸ 信息碰撞模拟 诺纹社工库|把“查数据”做成赛博朋克。
🤣1
Channel photo removed
预告:今天将重大更新 功能:手机定位(全网首发) 期待吗🎲 已更新
🔊致客户的肺腑之言:乱象丛生,唯有信誉与稳定是王道 各位尊敬的客户与同行,请允许我分享一些行业内幕与肺腑之言: ⚠️警惕市场乱象!低价陷阱与跑路风险剧增! 这一年,查档加密领域涌入了太多的新人机器人,市场鱼龙混杂: ⚡️🎣 诱骗预存: 很多平台为了骗取用户预存资金,故意放出极低甚至不合理的“优势价格”,目的就是引诱你大额充值,最终卷钱跑路。 ❌小作坊 口子: 还有一些是依靠自建的“小作坊”渠道。这种渠道一旦出现问题(即“口子死了”),基本不会退还任何资金! 我们深有体会: 就在前两年,我们也曾踩过同样的雷,因渠道跑路被坑了几十万多。这个行业的水深,骗局数不胜数。 📊从小白到走到现在:我们用口碑和实力说话! 在这个行业摸爬滚打多年,踩过的雷无数,付出的学费巨大。但正是这些经历让诺纹从一个“小白”成长为行业内经验丰富的玩家 口碑和信誉是生命线: 我们深知在这个混乱的市场中,口碑和信誉是唯一能够立足的根本。去年,我们仅…
👍社工库已经更新情报局同款全户数据 数据量10亿+ 发送身份证号基本都可以查出全户 你们的喜欢就是我们更新最大的动力 感谢使用👍 社工库直通:@Nwsgkbot
马上更新全户数据🎲
🎲【重大更新】 🎲全国照片户籍查询🎲 ✨因为客户需求我们决定推出免费查询个人户籍的系统 ✨全网唯一一家可以白嫖户籍的社工库 🐮查询入口-@nwsgkbot
Photo, posted without a caption
社工库RMB自动充值如果付不进款的用户可以联系客服进行操作 @nwadmin_bot
Showing the 12 most recent of 16 posts we hold for @nwsgk. 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.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“诺纹官方通知频道” (@nwsgk), 13,018 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/nwsgk.
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.