Telegram RegisterThe public register of Telegram
Telegram profile photo for 雪花社工库 查档模板

Channel

雪花社工库 查档模板

@xuepp_xuehi

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

8,976subscribers

-1,485 since we began measuring on 4 November 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1004442199214
TypeChannel
Username@xuepp_xuehi
Description💎价格表 @xuehi 💎双向点我 @p5abot 💎身份证机器人 @datou5bot 💎核验机器人 @heyan11bot 唯一客服 @xuepp
CreatedBetween 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 November 2026
Last confirmed live7 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/xuepp_xuehi

Growth

8,97610,4619,718.54 November 2026 — 10,461 subscribers4 November 2026 — 9,799 subscribers7 November 2026 — 8,976 subscribers4 November 20267 November 2026
3 measurements spanning 3 days, net -1,485. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 8,753–10,684 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Nov 2026, 10:398,976-823
4 Nov 2026, 17:289,799-662
4 Nov 2026, 05:2210,461first reading

Engagement

14 posts held, back to 3 November 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 10 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.56%
avg views ÷ 8,976 subscribers
Avg views / post
589
14 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
14
of 14 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 November 2026
Posts held14 (3 November 2026 – 3 November 2026)
Views total8,244
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 23:34 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
126
Links
1

Lifetime counters from Telegram’s own channel header, read 8 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: 1 of 14 posts held from the last 30 days (7.14%) 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).

3 Nov 2026, 16:39 UTC≈1,020 viewsread 8 November 2026

🕠雪花查档项目🕠 【微信/QQ好友提取】 【微信/qq聊天记录】 🔥🔥【消除案底*重新做人】 【各种大反查】 【微信反查】 【照片找人】 【护照/通行证反查】 【支付宝收款码反查】 【小红书/快手/qq 反查】 社交账号评论提取 小红书 抖音 等社交账号 关注粉丝列表 📱📱【地址】 【邮政地址】 【水电地址】 【京东快递】 【美团外卖】 淘宝闪购 刑侦地址 【疫苗预留地址】 📌【行踪-轨迹】 【出入境记录】 小关联 【抖音购物记录】 【通话记录】 高速记录 【手机轨迹】 【手机定位】 【人物轨迹】 【开房记录】 【飞火记录】 【车辆轨迹】 【停车场记录】 滴滴打车记录 【人物关联】 短信记录 抖音联系人互动关联 【背景大调查】 【婚姻记录】 【学信网】 【出生证明】 【征信报告】 【社保记录】 【医保记录】 【全家户籍】 【医疗记录】 【人员背景】 【出入境证件】 【个人风险评估】 sfz正反/盖章 名…

3 Nov 2026, 15:55 UTC978 viewsread 8 November 2026
Photo

业务名称:警务通人脸识别 ❤️❤️❤️ 提供资料: 提供照片出最高相似度 提供照片+名字:对上默认出 提供照片+名字+地区:对上一条默认出 提供照片+名字+地区+年龄:对上一条默认出 出单结果:精准人脸点射 出单时间:当天隔天 或者直接出最高相似度3头

3 Nov 2026, 15:54 UTC987 viewsread 8 November 2026
Photo

业务名称:人物小关联 ❤️❤️❤️ 提供信息:身份号 当天 户籍地 常住地址 关联地址 关联人信息

3 Nov 2026, 15:53 UTC988 viewsread 8 November 2026
Photo

业务名称:全国 法人 ❤️❤️ 个体户法人 ❤️❤️❤️ 股东 高管 监视❤️❤️❤️ 提供: 姓名 公司名称 公司代码报单

3 Nov 2026, 15:52 UTC67 viewsread 8 November 2026
Photo

业务名称:护照反查 回单内容:反身份证信息 回单时效:当天隔天

3 Nov 2026, 15:52 UTC65 viewsread 8 November 2026
Photo

📱手机号查抖音 ❤️❤️❤️ 📱手机号查小红书❤️❤️❤️ 📱手机号查快手 ❤️❤️❤️ 📱手机号查网易云❤️❤️❤️ 当天回单 晚上报隔天回

3 Nov 2026, 15:51 UTC66 viewsread 8 November 2026
Photo

公司名下卡 ❤️❤️❤️ 公司名下卡提供公司名报单 出企业名下卡

Showing the 12 most recent of 14 posts we hold for @xuepp_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 2 registered channels — 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.

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 7 November 2026 — this entry's latest reading, not the date you are reading this.

“雪花社工库 查档模板” (@xuepp_xuehi), 8,976 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/xuepp_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.