https://t.me/+xAOKjmoRDcE2ZTVh 新公群 要报备的进~

Channel
少妇发财中2.0
@shaofuu002
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
26,716subscribers
+4,926 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001276598915 |
|---|---|
| Type | Channel |
| Username | @shaofuu002 |
| Description | 唯一业务号 @shaofuu 查人调档 精准找人 多元化查找信息~ 童叟无欺 诚招代理~权限部门合作捞金~ |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/shaofuu002 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:44 | 26,716 | +4,909 |
| 12 Aug 2026, 02:02 | 21,807 | +12 |
| 11 Aug 2026, 04:27 | 21,795 | +4 |
| 10 Aug 2026, 03:51 | 21,791 | +1 |
| 9 Aug 2026, 19:46 | 21,790 | first reading |
Engagement
23 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 9 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.32%
- avg views ÷ 26,716 subscribers
- Avg views / post
- 886
- 23 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 23
- of 23 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 13 August 2026 |
|---|---|
| Posts held | 23 (25 July 2026 – 13 August 2026) |
| Views total | 20,372 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 03:26 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
- 50
- Links
- 3
Lifetime counters from Telegram’s own channel header, read 14 August 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
最全婚姻渠道~ 图1 文字婚姻全天秒~只有配偶 图2 老板红板婚姻~当天3点前报当天回~出单至今0售后 图3 早8-晚8秒线婚姻~ 纯民政~部分单昨天结婚今天出不来~
三合一公网名下卡 稳定回 花一样加钱带走三样 合适 名下卡 名下车 名下公司一体~
老版开普勒手机轨迹 复活 提供手机号 出近一年手机轨迹 数据超5条默认出单 包真不包漏 识别基于WIFI IP GPS APP软件 基站等 多重识别方式 结果直接导出未经过人为编辑,所以个别位置会有误导识别现象,产生经纬跳跃 结果以总体较多出现的位置为准。
公网违反一件套 暂时涨价 每天发车 不翻车 隔天回 急单可加钱加急 当天报 当天回 公网违反二件套,降价开~
移动专线定位 高速出单 联通电信转网移动的都可以出 10分钟内回单 出必准 出单率高 目前只要移动号码 定位回复不及时请刷屏!
公网户籍地 大库户籍地 慢线公网一体真地址 秒线大头👉
Photo, posted without a caption
人行征信开 非便宜大数据版本 报单提供 名字-身份证-手机号 工作日1-3天回 代理可拿优势 批量可以来谈价格 包含房贷、车贷、信用卡、网贷记录、关联相关还款责任 人民银行征信报告有哪些欠款记录就体现哪些记录 用途:婚前调查,相亲对象,男女朋友,奔着结婚目的。还有一些合作伙伴, 一定要查一下,现在很多人都有网贷,不要被那些假大款骗了 人行征信敏感可接,自觉说明情况,发现不符合情况的不听理由直接扣 未告知敏感直接扣 具体价格根据情况决定 ‼️‼️
婚姻开,保民政,换板了,秒线 一分钟回单~ 不秒直接白送 早8-晚8
医疗记录~ 秒单~ 发票秒单~
小红书反,开~ 不出旧绑,出来就是现绑 包验证
Showing the 12 most recent of 23 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.
Posts edited after publishing
@shaofuu002 edited 1 post 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.
- First edit seen
- 10 August 2026
- Most recent edit
- 10 August 2026
Citation-graph rank
Citation-graph rank — 811,135 of 1,189,255entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 3 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“少妇发财中2.0” (@shaofuu002), 26,716 subscribers as measured 12 August 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.