Channel
@HUiDUGuarantee
On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry
18,801subscribers
-1,717 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001519653528 |
|---|---|
| Type | Channel |
| Username | @HUiDUGuarantee |
| Created | 12 October 2021 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/HUiDUGuarantee |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 19 Sept 2026, 17:40 | 18,801 | -31 |
| 17 Sept 2026, 08:41 | 18,832 | -35 |
| 15 Sept 2026, 10:58 | 18,867 | -41 |
| 13 Sept 2026, 16:58 | 18,908 | -62 |
| 11 Sept 2026, 20:17 | 18,970 | -72 |
| 9 Sept 2026, 11:37 | 19,042 | -161 |
| 6 Sept 2026, 00:57 | 19,203 | -56 |
| 3 Sept 2026, 20:38 | 19,259 | -47 |
| 2 Sept 2026, 15:25 | 19,306 | -65 |
| 1 Sept 2026, 12:54 | 19,371 | -124 |
| 31 Aug 2026, 10:05 | 19,495 | -63 |
| 30 Aug 2026, 13:13 | 19,558 | -81 |
| 29 Aug 2026, 09:48 | 19,639 | -73 |
| 28 Aug 2026, 11:52 | 19,712 | -31 |
| 27 Aug 2026, 10:55 | 19,743 | -7 |
| 26 Aug 2026, 07:34 | 19,750 | -36 |
| 25 Aug 2026, 07:08 | 19,786 | -43 |
| 24 Aug 2026, 04:16 | 19,829 | -44 |
| 22 Aug 2026, 15:26 | 19,873 | -11 |
| 21 Aug 2026, 08:35 | 19,884 | first reading |
8 posts held, back to 12 October 2021 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 56 pages 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 8 posts for this entry, the most recent from 30 June 2026. An engagement rate over an empty window would be a number about nothing.
Important Notice: Update of Huidu Official Payment Address Dear Valued Partners and Clients： To provide a more secure and reliable service, Huidu Escrow has officially updated its payment address with immediate effect. Previous Payment Address Valid until: July 31, 2026, 23:59 ·The previous address will remain available until the above deadline. However, we strongly recommend updating your records and using the…
Huidu.io Escrow Service - Terms & Rules pinned a photo
HUIDU Official Contact & Payment Address For escrow services or to place a deposit for a HUIDU Verified Group, please contact our verified official account: @huiducn HUIDU Escrow Payment Address USDT–TRC20: TXSDVmoRsk6LyB6Weysj6nupGGKuubbbim Tap the address above to copy it. Before making any transfer, please confirm the wallet address directly with an official HUIDU escrow representative. If the wallet address or…
[Huidu.io Escrow - Transaction Rules & Guidelines] 1. Pinned Rules Are Final: All escrow group chats must have the transaction rules and details pinned as the first message, and these must not be edited. Any rule changes must be mutually agreed upon and re-pinned. If a dispute arises due to unconfirmed changes, the escrow service will be suspended until both parties resolve it. 2. Disputes & Lost Funds: If disagree…
【Huidu.io Escrow - Fee Details] 1. Standard One-Time Escrow Fee: • 4% commission for regular users. • 2% commission for Huidu Prime Members. 2. Payment & Currency Exchange Escrow Fee: • 0.2% of the transaction amount for regular users. • 0.1% of the transaction amount for Huidu Prime Members. • Fees are settled daily (minimum fee: 10 USDT/day if there’s an active transaction; each escrow cycle requires a minimum of…
[Huiud.io Escrow - Transaction Details Example] Supplier: [@ Telegram ID] Transaction Address: [Supplier’s Wallet Address] Buyer: [@ Telegram ID] Transaction Address: [Buyer’s Wallet Address] Service/Product: [e.g. Advertising, Payment Gateway, Database, iGaming Site Setup, etc.] Unit Price: XXX USDT Total Price: XXX USDT Escrow Deposit: XXX USDT (Transaction amount + Escrow Fee) Escrow Fee Paid By: [Specify whic…
[Huidu.io Escrow Services - One-Time Transaction & Payment Escrow Process] 1. Initiate Escrow Group Contact the official Huidu escrow representative (@HuiduEscrow) to create a Telegram transaction group. ⚠️ Only groups created by this official account are valid. Any groups created by others will not be recognized as official escrow groups. 2. Post Transaction Details The Huidu escrow representative (@HuiduEscrow) w…
Channel created
Showing the 8 most recent of 8 posts we hold for @HUiDUGuarantee. 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.
@HUiDUGuarantee 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Huidu.io Escrow Service - Terms & Rules” (@HUiDUGuarantee), 18,801 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/HUiDUGuarantee.
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.