雪花查档 @xuehi pinned «社工库 换新机器人了 @xueppbbot 不要在问我为啥社工库不能用了»

Channel
雪花查档 @xuehi
@xuehi
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
47,187subscribers
-113,277 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001072689801 |
|---|---|
| Type | Channel |
| Usernames | @xuehi @xuehi_xuepp |
| Description | 💎免费社工库 @xueppbbot 💎价格表 @xuehi 💎身份证机器人 @datou5bot 💎核验机器人 @heyan11bot 💎唯一客服 @xuepp 💎双向点我 @p5abot |
| Created | Between 1 September 2016 and 2 September 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 October 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 44 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/xuehi |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 19 October 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 06:18 | 47,187 | -2,296 |
| 5 Nov 2026, 03:36 | 49,483 | +47,648 |
| 2 Nov 2026, 03:00 | 1,835 | +196 |
| 29 Oct 2026, 19:17 | 1,639 | +283 |
| 26 Oct 2026, 22:25 | 1,356 | +1,260 |
| 19 Oct 2026, 00:46 | 96 | +17 |
| 19 Oct 2026, 00:22 | 79 | -71,590 |
| 15 Oct 2026, 12:57 | 71,669 | -299 |
| 14 Oct 2026, 11:27 | 71,968 | -1,471 |
| 13 Oct 2026, 01:21 | 73,439 | -878 |
| 8 Oct 2026, 19:36 | 74,317 | -1,803 |
| 4 Oct 2026, 06:02 | 76,120 | -2,890 |
| 25 Sept 2026, 13:58 | 79,010 | -6,116 |
| 17 Sept 2026, 08:37 | 85,126 | -5,062 |
| 15 Sept 2026, 11:41 | 90,188 | -5,429 |
| 13 Sept 2026, 17:37 | 95,617 | -6,753 |
| 11 Sept 2026, 19:18 | 102,370 | -8,027 |
| 9 Sept 2026, 06:00 | 110,397 | -12,913 |
| 5 Sept 2026, 20:14 | 123,310 | -7,999 |
| 3 Sept 2026, 18:01 | 131,309 | first reading |
Engagement
39 posts held, back to 2 September 2016 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.12%
- avg views ÷ 47,187 subscribers
- Avg views / post
- 999
- 21 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 23
- of 39 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.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 39 (2 September 2016 – 5 November 2026) |
| Views total | 20,978 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 15:54 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
- Photos
- 59
- Links
- 3
Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
Telegram’s own ‘edited’ marker: 4 of 23 posts held from the last 30 days (17.4%) 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).
全是假货,注意分辨客服号,别被骗子骗了
社工库 换新机器人了 @xueppbbot 不要在问我为啥社工库不能用了
🕠雪花查档项目🕠 【微信/QQ好友提取】 【微信/qq聊天记录】 🔥🔥【消除案底*重新做人】 【各种大反查】 【微信反查】 【照片找人】 【护照/通行证反查】 【支付宝收款码反查】 【小红书/快手/qq 反查】 社交账号评论提取 小红书 抖音 等社交账号 关注粉丝列表 📱📱【地址】 【邮政地址】 【水电地址】 【京东快递】 【美团外卖】 淘宝闪购 刑侦地址 【疫苗预留地址】 📌【行踪-轨迹】 【出入境记录】 小关联 【抖音购物记录】 【通话记录】 高速记录 【手机轨迹】 【手机定位】 【人物轨迹】 【开房记录】 【飞火记录】 【车辆轨迹】 【停车场记录】 滴滴打车记录 【人物关联】 短信记录 抖音联系人互动关联 【背景大调查】 【婚姻记录】 【学信网】 【出生证明】 【征信报告】 【社保记录】 【医保记录】 【全家户籍】 【医疗记录】 【人员背景】 【出入境证件】 【个人风险评估】 sfz正反/盖章 名…
雪花查档 @xuehi pinned a photo
查档认准雪花 @xuepp 永久飞机id @xuehi
@xueppbbot 新社工库机器人 登录数据积分都会同步
🔥🔥🔥🔥 提取微信聊天记录 删除的也可以提取 提取微信聊天记录 删除的也可以提取 提取微信聊天记录 删除的也可以提取 挖对手商业资源 找对象的出轨对象 🔥🔥🔥🔥😂😂😂😂 🔥认准雪花查档唯一客服 @xuepp
身份证人际关系网综合关联人,超级齐全
“玩商战还敢不带透视挂?一键扫描敌方企业发票面板。他的核心客户名单、真实报价底线全量掉落。直接闪现贴脸抢怪,按着对方的底价精准报价,这波属于是物理偷家级别的爽局!”
商业无间道 / 竞业调查(降维打击友商): 竞争对手底牌全开。看对方的真实经营情况、投资版图和核心骨干(董事/监事/财务)底细,直接拿捏对方的商业软肋。 企业工商内档 法人+股东+董事+监事+财务 资料 公司章程+投资情况+证书+诉讼+股权架构+利润表+负债表+经营情况+备案内容+执照+身份证+公司地址租赁协议+
医保记录一出,谁在裸奔一目了然!🚨 抓奸/相亲: 别听她说是“母胎单身”,查查医保记录里有没有**“人工流产”和“术后修复”?别听他说力拔山河,看他医保卡里是不是全是“西地那非”和“补肾神方”! 反骗婚: 吹牛逼在事业单位上班?查查医保缴费单位,看看他到底是公职人员,还是工地搬砖的临时工! 盘口自保: 老板们注意!查查手下人的医保记录,看他以前的五险一金是谁交的,别把“戴袖章的”**当兄弟养! 认准雪花查档唯一客服 @xuepp
Showing the 12 most recent of 39 posts we hold for @xuehi. 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.
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.
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.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“雪花查档 @xuehi” (@xuehi), 47,187 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/xuehi.
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.