Channel
@s520v
On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry
16,516subscribers
-3,391 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002705172438 |
|---|---|
| Type | Channel |
| Usernames | @s520v @wzsgkkf @xbofi |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 91 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/s520v |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 05:47 | 16,516 | +229 |
| 10 Oct 2026, 11:57 | 16,287 | +6 |
| 9 Oct 2026, 01:41 | 16,281 | no change |
| 8 Oct 2026, 23:55 | 16,281 | -255 |
| 6 Oct 2026, 09:00 | 16,536 | -89 |
| 4 Oct 2026, 15:40 | 16,625 | -17 |
| 4 Oct 2026, 10:36 | 16,642 | -53 |
| 1 Oct 2026, 07:01 | 16,695 | -99 |
| 26 Sept 2026, 15:58 | 16,794 | -12 |
| 25 Sept 2026, 21:56 | 16,806 | -451 |
| 18 Sept 2026, 11:16 | 17,257 | -12 |
| 17 Sept 2026, 11:57 | 17,269 | -14 |
| 17 Sept 2026, 06:58 | 17,283 | -91 |
| 16 Sept 2026, 01:39 | 17,374 | -63 |
| 15 Sept 2026, 07:58 | 17,437 | -31 |
| 15 Sept 2026, 06:16 | 17,468 | -31 |
| 14 Sept 2026, 05:37 | 17,499 | -86 |
| 13 Sept 2026, 16:58 | 17,585 | no change |
| 13 Sept 2026, 16:20 | 17,585 | -42 |
| 12 Sept 2026, 16:56 | 17,627 | first reading |
28 posts held, back to 17 June 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 43 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 28 posts for this entry, the most recent from 3 September 2026. An engagement rate over an empty window would be a number about nothing.
#频道互推 #相似推荐 ------------------------------ 📢 哦耶免费社工库官方频道 📢 灰太狼社工库 开户/查档源头价格 免费社工库 📢 五月天免费社工库开户查人找人 📢 专业查人 查档 查地址 聊天信息 📢 全能免费社工库开户开盒查档查人查车找人客户交流频道 📢 开户机主+ 人肉开盒 📢 DragonSage 📢 东南亚吃瓜 好用社工库分享 📢 开户开盒社工库资源分享 📢 犯罪记录+车主信息 ------------------------------ ☁️ 互推入口：@souso
#频道互推 #相似推荐 ------------------------------ 📢 数据商城 📢 免费社工库分享 📢 【法拉利免费社工库】查档查人｜开盒开户 📢 全网最强社工库分享 📢 太极开户查档全网免费社工库｜开盒源头价格 📢 全球通数据 📢 吃瓜赚钱新闻 📢 朝阳侦探社·查档开户开盒 📢 悟空查档重金寻条（网逃，立案，定位，外卖，流水，微返） 📢 华盛助贷精准源头（DPI.SDK） ------------------------------ ☁️ 互推入口：@sooo
已修复 新社工库 @WztdSgKbot
社工库马上修复大家先别急
大头市场变化涨价了 我们依旧特价 2️⃣5️⃣🔤🔤🔤一单 市场最低批量代理联系 @mvppy 或 @wztdbot 提供身份证+名字 如果没有身份证提供手机号+名字查身份证大头一条龙1️⃣6️⃣8️⃣🔤🔤🔤特价! 全天在线秒出
社工库被恶意举报等待处理通知
@wangzepg 本群转让有意联系 @mvppy 或 @wztdbot 查询去 @wangzejlq
25一单
不了解TG使用方法可以加一下这个频道了解一下 https://t.me/TGsyjc
大头市场变化涨价了 我们依旧特价 4️⃣5️⃣🔤🔤🔤一单 市场最低批量代理联系 @mvppy 或 @wztdbot 提供身份证+名字 如果没有身份证提供手机号+名字查身份证大头一条龙1️⃣8️⃣8️⃣🔤🔤🔤特价! 全天在线秒出
1
消息不撤回就一直都有
Showing the 12 most recent of 28 posts we hold for @s520v. 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.
@s520v edited 3 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.
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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“kaihu” (@s520v), 16,516 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/s520v.
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.