九九新ID @jiujiuyfsff

Channel
风花雪月担保频道
@FHXYDB0
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
44,508subscribers
-153 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 | -1002203066627 |
|---|---|
| Type | Channel |
| Username | @FHXYDB0 |
| Description | 相知多年 值得托付 安稳唯一✈️ @FHXY00 担保验证机器人 @FHXYyzdb_bot VIP通知群: @AW520000000 公开通知群: @AW5200000000 风花雪月担保频道: @FHXYDB0 |
| Created | 2 August 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/FHXYDB0 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 15:56 | 44,508 | -24 |
| 20 Aug 2026, 17:22 | 44,532 | +12 |
| 19 Aug 2026, 13:55 | 44,520 | +8 |
| 18 Aug 2026, 16:47 | 44,512 | -3 |
| 17 Aug 2026, 19:48 | 44,515 | -13 |
| 16 Aug 2026, 16:49 | 44,528 | -9 |
| 14 Aug 2026, 22:45 | 44,537 | +3 |
| 13 Aug 2026, 11:26 | 44,534 | +2 |
| 12 Aug 2026, 13:06 | 44,532 | -12 |
| 11 Aug 2026, 16:22 | 44,544 | -31 |
| 10 Aug 2026, 14:14 | 44,575 | -11 |
| 9 Aug 2026, 15:14 | 44,586 | -18 |
| 8 Aug 2026, 17:44 | 44,604 | -61 |
| 7 Aug 2026, 20:15 | 44,665 | +4 |
| 7 Aug 2026, 14:45 | 44,661 | first reading |
Engagement
66 posts held, back to 2 August 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 36 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.60%
- avg views ÷ 44,508 subscribers
- Avg views / post
- 1,600
- 61 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 61
- of 66 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 22 August 2026 |
|---|---|
| Posts held | 66 (2 August 2024 – 22 August 2026) |
| Views total | 97,867 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Aug 2026, 03:08 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
- 1
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 23 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
冰封新id: @bfnnn
九九: @yffsjiujiu 账号被盗,暂停担保
近期代码猖獗 一定要分清楚用户名和个人简介 不放心的担保进款打开录屏以防双清 风花担保验证机器人:@FHXYyzdb_bot
两难:@FHXY_LN 加压现DB10000U HX代打
金灿:@jincan123 加压到7000u 后续代打
堕落:@duoluo 担保7000U 主攻HX
逃兵:@FH6650 变心担保3000u
各位可以给担保人员设置一个备注方便分辨真假(进款之前也需要验证一下是否还有担保) 近期代码猖狂请各位担保擦亮眼睛 记得验证和看清楚是不是个人简介
人为峰:@RWF0880 申请退押不再担保
士兵 @shibing222 《那年春db3000u》
李凡:@xf1098 申请退押 不再担保
Showing the 12 most recent of 66 posts we hold for @FHXYDB0. 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
@FHXYDB0 edited 2 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.
- First edit seen
- 8 August 2026
- Most recent edit
- 20 August 2026
Mentions
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“风花雪月担保频道” (@FHXYDB0), 44,508 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/FHXYDB0.
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.