高德轨迹恢复,积攒的单可以上了,随时阵亡
Signed 少妇u@shaofuu

Channel
@shaofuu002
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
27,677subscribers
+5,887 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001276598915 |
|---|---|
| Type | Channel |
| Usernames | @i520n @shaofuu002 |
| Description | 唯一业务号 @shaofuu 查人调档 精准找人 多元化查找信息~ 童叟无欺 诚招代理~权限部门合作捞金~ |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 91 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/shaofuu002 |
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 48% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 21:49 | 27,677 | -13 |
| 16 Nov 2026, 02:28 | 27,690 | -72 |
| 13 Nov 2026, 10:06 | 27,762 | -13 |
| 12 Nov 2026, 15:17 | 27,775 | -58 |
| 11 Nov 2026, 00:09 | 27,833 | no change |
| 10 Nov 2026, 13:40 | 27,833 | +16 |
| 9 Nov 2026, 08:38 | 27,817 | -6 |
| 8 Nov 2026, 22:17 | 27,823 | +1 |
| 8 Nov 2026, 01:31 | 27,822 | -2 |
| 7 Nov 2026, 12:25 | 27,824 | +6 |
| 6 Nov 2026, 22:51 | 27,818 | +1 |
| 6 Nov 2026, 09:21 | 27,817 | +7 |
| 5 Nov 2026, 20:55 | 27,810 | +4 |
| 5 Nov 2026, 06:07 | 27,806 | no change |
| 4 Nov 2026, 23:31 | 27,806 | +11 |
| 4 Nov 2026, 03:06 | 27,795 | +4 |
| 3 Nov 2026, 20:47 | 27,791 | +4 |
| 3 Nov 2026, 03:41 | 27,787 | -2 |
| 2 Nov 2026, 23:26 | 27,789 | +10 |
| 2 Nov 2026, 04:00 | 27,779 | first reading |
210 posts held, back to 25 July 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 117 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. It is computed over the 91 of 122 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 210 (25 July 2026 – 16 November 2026) |
| Views total | 73,109 |
| Reactions total | 224 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 04:58 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 17 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.
289 reactions across 111 posts, in 6 distinct kinds. The most used accounts for 70.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 203 | 70.2% | |
| ❤ | 72 | 24.9% | |
| 👏 | 5 | 1.73% | |
| 🤣 | 4 | 1.38% | |
| 👎 | 3 | 1.04% | |
| 🤩 | 2 | 0.692% |
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 119 of the 210 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 289 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 210 most recent posts we hold, published 25 July 2026 to 16 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: 25 of 123 posts held from the last 30 days (20.3%) 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).
高德轨迹恢复,积攒的单可以上了,随时阵亡
Signed 少妇u@shaofuu
天眼地址(半年版) 每天早10晚6 提供身份证 优点介绍:出现居住地址 户籍地址 个人关联名下常用支付账号 关联名下公司 婚姻记录 人员社会人群分类等详情信息 重点!!!! 出半年内的 轨迹分析 经常在那个城市 包括落脚点地址分析 带时间的 落脚点地址分析都是比较详细的地址 包括去过哪些城市这段时间 上面落脚点分析地址时间 是真实的 个别人员可出实时地址 地区原因 并不是市面上 什么p的 数据库地址 外卖地址 有现居住地址 包括落脚点分析 双地址 保驾护航 只出半年内的 不是半年内 按空 不会让客户 买单 真正的让客户花 最少的钱体验到 真正的公网业务 可以随便埋雷 条哥 每天 回多批 找人必备
❤1
Signed 少妇u@shaofuu
安徽 湖南 广西 上海 浙江 湖北 江西 黑龙江 重庆 海南 山东 天津 河北 山西 内蒙古 辽宁 吉林 江苏 福建 河南 四川 贵州 云南 西藏 陕西 甘肃 青海 宁夏 新疆 广东 最全地区房产 降价 😃😃出全套
Signed 少妇u@shaofuu
QQ反 稳定回单 返回 二 三要素 姓名 身份证 手机号 确定好有实名再报上来,新号不要
❤6👍4👏2
Signed 少妇u@shaofuu
开同特价 ❤️❤️❤️ 单开出近5年记录 同住人出近1-3年记录 1-3天回单
👍4
Signed 少妇u@shaofuu
全行 ❤️😀单 行😃 文字回单 无遗漏 中信银行 交通银行 光大银行 兴业银行 华夏银行 恒丰银行 浙商银行 渤海银行 中国银行 建设银行 十大行 名下全部卡 单行查询可备注一张不出
Signed 少妇u@shaofuu
11.14号 定位 老二网定位 维护❌ 每天 早11点到晚1点 (境外卡 电信 还在维护中) 发现历史赔5000 发现假位置赔10000 提供证据 秒款不嘴硬! ————————————————— 三网定位 开✔️ 每天晚9点半到晚1点 移动 联通 电信 一小时左右回单 误差普遍几十-几百米 ————————————————— 移动定位 开✔️ 目前只开通移动路线 联通 电信 陆续开放中 每天中午11点到晚上2点 误差就在10米到50米左右 出单速度快 出单率高 精准!
Signed 少妇u@shaofuu
微支流水 稳定回
👍1
Signed 少妇u@shaofuu
柜台无遗漏个户公户 个户开卡 ❤️❤️❤️ 公户开卡 ❤️❤️❤️ 中国银行 农业银行 工商银行 招商银行 浦发银行 中信银行 光大银行 民生银行 兴业银行 平安银行 广发银行 华夏银行 浙商银行 渤海银行 恒丰银行 汉口银行 湖北银行 武汉农村商业银行 只要以上银行 每个银行反馈时间不一样 遇到回单只有利息 信息费的 也正常收费 出单即收费 对回单有疑问的支持任何渠道复查 比此渠道出的多的 都支持无条件免单 周末发车 5工作日内回完
👍1
Signed 少妇u@shaofuu
老板顺丰地址 ❤️❤️❤️ 手机号下单 出3个月内最新一条 带顺丰面单回单 限量 当天隔天回
👍3
Signed 少妇u@shaofuu
出入境 全天在
👍1
Signed 少妇u@shaofuu
价格特价,质量不特价,日开几十单的七合一地址,便宜好用
Signed 少妇u@shaofuu
Showing the 12 most recent of 210 posts we hold for @shaofuu002. 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.
@shaofuu002 edited 16 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.
We recorded 8 posts on @shaofuu002 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Named by 4 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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“少妇发财中2.0” (@shaofuu002), 27,677 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/shaofuu002.
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.