Channel
@FGxuzhi
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
87subscribers
+27 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002178561971 |
|---|---|
| Type | Channel |
| Username | @FGxuzhi |
| Created | Between 1 June 2024 and 14 July 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/FGxuzhi |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 18:21 | 87 | +10 |
| 26 Sept 2026, 12:00 | 77 | +17 |
| 12 Sept 2026, 16:16 | 60 | -1 |
| 3 Sept 2026, 14:18 | 61 | +1 |
| 19 Aug 2026, 07:15 | 60 | no change |
| 19 Aug 2026, 07:00 | 60 | first reading |
4 posts held, back to 14 July 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 4 posts for this entry, the most recent from 17 August 2024. An engagement rate over an empty window would be a number about nothing.
9 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 33.3% | |
| 👎 | 3 | 33.3% | |
| 👍 | 2 | 22.2% | |
| 🤮 | 1 | 11.1% |
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 4 of the 4 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 14 July 2024 to 17 August 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
近期不少用户私聊我表示被骗，并质问小米为何不将骗子踢出群。在此，我统一给大家回复一下： 一、关于无凭证举报 若聊天记录被清空，无凭证举报某个人，小米直接将其踢出。那别人也能随意举报您为骗子，导致您也被踢出，如此一来，群里无人安全。 例如：A 举报 B 是骗子，但无任何凭证，小米若直接处理，B 可能觉得冤枉。反之，B 也能轻易举报 A，这种情况会让群内成员人人自危。 二、关于有凭证举报 提供凭证时，小米需核实。若仅看聊天记录和名字头像就踢人，不管对方辩解，可能存在恶意举报。 比如：有人因对方不给赊账或先款，就用小号改相同名字、头像，自己截图聊天记录举报，这会让群内秩序混乱。 即便提供了录屏或截图凭证，也可能存在关键或不利信息被删除的情况。 小米遇到过欠旧账未还，转 U 还债后想继续赊账，被拒后删除不利信息，录屏说对方收钱不发货来举报。 三、处理此类问题的困境 小米起初处理过这类问题，但发现能被处理的多是老实人，狡猾的人总有各…
👍1
问：怎么知道我进的是真的担保群，不是代码的？ 答：每一个群，富贵小米 @QDDDD 都在里面并且是群主，进了担保群后，点开富贵的资料，找到共同群，如果有这个担保群 ，那就是为真。而且群里都是富贵担保助机器人 @FGPDbot 接管整个担保流程，不需要人工干预，如果有纠纷才需要艾特富贵出来处理。如果一切顺利，双方自主完成交易流程即可。 ━━━━━━━━━━━━━━━━ 问：怎么知道买家有没付款？ 答：担保群里由富贵担保助手（管理员）发送信息包含字眼：🔔付款成功 xx USDT，才是真的买家有上压到这个群里。这条信息必须由富贵担保助手 @FGPDbot 发出，才为真！同时还会发送一条包含按钮【确认收货】【申请退款】，要注意你在群里的身份是不是商家。核对金额无误，才可发货，私发|发群里，都可以。 ━━━━━━━━━━━━━━━━ 问：买家放款后，商家到哪里提币？ 答：私聊富贵担保助手 @FGPDbot > 提现，第一次提现的用户，请先…
❤3👍1👎1
为何要选择富贵作为担保？ 1. 【首家自助担保模式】自主研发的飞机首家 7*24 小时自助担保机器人，买卖双方可随时自行拉取担保。充值与提现均能秒到账，满足用户在各个时间点的交易需求。操作流程简便，每个担保群富贵均在其中，出现问题可艾特富贵，能快速响应！ 2. 【富贵专注担保】本行所赚取的即为信息差价，而最为重要的也是客户信息，富贵仅从事担保业务，与大家不存在竞争关系，不会去争抢客源，不会出现今日找其担保，明日客户便被抢走的情形。 3. 【富贵不涉足业务】富贵不参与业务活动，不会因业务更新可能导致自身损失，从而不会影响担保资金的安全性。 4. 【高度重视隐私保护】用户的隐私是富贵坚守的底线，无论你是一手交易还是二手搬砖，在富贵这里信息均会保密，任何人都无法从富贵处获取你的交易情况及用户信息。担保群的聊天记录富贵不会去查看，除非有纠纷且群里有人艾特富贵！ 5. 【确保用户资金安全】富贵仅负责其生态内的交易，只要通过富贵担保，且…
👎1
一些常见的担保交易纠纷问题： 问：买家付款后多久会自动放款？若买家一直不放款，商家应如何处理？ 答：不存在自动放款的情况。但商家可要求买家放款，若买家未回应，商家可要求富贵介入处理。群内有明确约定放款时间且已超时，而买家未反馈售后问题，富贵将进行放款操作。若未约定放款时间，富贵会通知买家在 12 个小时内作出回应，若逾期未回应，则视为默许同意放款。 问：买家付款后商家不发货且失踪，应如何解决？ 答：商家应在 30 分钟内完成发货，特殊约定除外。超时后买家可在群内说明原因并申请退款。商家逾期发货，必须先征得买家同意方可发货。若商家不发货也不同意退款，买家可艾特富贵介入处理。富贵会通知商家在 12 小时内作出回应，若逾期未回应，则视为默许同意退款。若在规定时间内商家在群内有回应，则双方继续交易。商家多次爽约将被封禁，需谨慎对待！ 问：买家存在售后问题应如何处理，包括但不限于：商家延迟发货、冻结、抢线、掉保、弹手机、加人过滤、不…
👎1🤮1
Showing the 4 most recent of 4 posts we hold for @FGxuzhi. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“富贵担保常见问题” (@FGxuzhi), 87 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/FGxuzhi.
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.