靖哥哥 @duoyusad 《担保3000u》

Channel
风花雪月担保频道
@FHXYDB0
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
39,864subscribers
-4,797 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 | 相知多年 值得托付 安稳唯一✈️ @FHXY @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 | 7 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/FHXYDB0 |
Topic
Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 15:40 | 39,864 | -1,946 |
| 4 Sept 2026, 14:56 | 41,810 | -1,120 |
| 3 Sept 2026, 00:25 | 42,930 | -418 |
| 1 Sept 2026, 22:07 | 43,348 | -296 |
| 31 Aug 2026, 20:17 | 43,644 | -251 |
| 30 Aug 2026, 22:46 | 43,895 | -147 |
| 30 Aug 2026, 02:05 | 44,042 | -128 |
| 29 Aug 2026, 03:47 | 44,170 | -131 |
| 28 Aug 2026, 02:05 | 44,301 | -52 |
| 26 Aug 2026, 23:27 | 44,353 | -48 |
| 25 Aug 2026, 22:13 | 44,401 | -32 |
| 24 Aug 2026, 22:15 | 44,433 | -32 |
| 23 Aug 2026, 07:36 | 44,465 | -43 |
| 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 | first reading |
Engagement
145 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 71 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.70%
- avg views ÷ 39,864 subscribers
- Avg views / post
- 1,480
- 121 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 122
- of 145 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 9 September 2026 |
|---|---|
| Posts held | 145 (2 August 2024 – 9 September 2026) |
| Views total | 178,633 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 00:35 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 10 September 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
浩: @a555t db3000u
堕落: @duoluo 申请退押
小谦:@labi 存在交易纠纷暂停担保
失联:@FHXY_SL 申请退押 不再担保
丢失 现用户名@bunaole
紫蝶:@xingL88 取消退押 正常担保
贪财:@FHXYTC 变心db3000u
一可 @YK55533 迪担保《3000u》
龙少 @hw008880退压 不再担保
紫蝶:@xingL88 申请退押不再担保
何程 @heidan 担保暂停 在进不认
Showing the 12 most recent of 145 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 4 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
- 6 September 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“风花雪月担保频道” (@FHXYDB0), 39,864 subscribers as measured 7 September 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.