Telegram RegisterThe public register of Telegram

Channel

灰度担保规则频道

@HDDB_GZ

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

407subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001881411257
TypeChannel
Username@HDDB_GZ
Description担保大群 @HDDB_DQ 担保一群 @HDDB_YQ 担保二群 @HDDB_EQ 担保规则 @HDDB_GZ 仲裁曝光 @HDDB_BG 公群频道 @HDDB_GQ 供应资源 @hdgongying 需求资源 @hdxuqiu 国际支付 @hdgjzf 社群汇总 @huiduchuhai8 官方频道 @huidugf 灰度出海 @huiduchuhai 📣运营联系: @huiduTom @HDDanny 🤖灰度担保: @HDDB_OFFICIAL 🌐灰度官网:www.huidu.io
Created17 July 2023measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/HDDB_GZ

Growth

4077 Aug 2026, 06:51 — 407 subscribers7 Aug 2026, 07:02 — 407 subscribers7 Aug 2026, 06:517 Aug 2026, 07:02
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 406–408 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 07:02407no change
7 Aug 2026, 06:51407first reading

Engagement

10 posts held, back to 17 July 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 10 posts for this entry, the most recent from 22 August 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
7
Links
3

Lifetime counters from Telegram’s own channel header, read 7 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.0%

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 3 of the 10 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 17 July 2023 to 22 August 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

22 Aug 2023, 06:45 UTC≈21,100 views0 reactionsread 7 August 2026
Photo

灰度官方人员及地址 担保及公群上押请认证账号 @HDDB_OFFICIAL trc-20押金地址: TUhARHNvGiYMvzHZ6ssPb8vXw7mNbswuSc 以上地址点击可复制,转账前请与灰度官方公群担保人员进行地址确认,若地址或账号有勿,请勿转账!

4 Aug 2023, 08:10 UTC≈20,600 views1 reactionsread 7 August 2026
Photo

灰度担保 - 担保交易规则【担保交易须知及担保规则】 (1)所有担保交易群内,双方交易规则及双方交易详情内容均不可编辑,且必须为置顶第一条,若需要修改规则,需要双方同意并重新置顶,若因规则产生纠纷,则暂停担保交易并等待双方处理。 (2)如果供需双方在合作过程中发生分歧或资金损失,需要双方协商解决方案,不接受单方面的方案。结算金额需要经过双方确认并执行,若供需双方其中一方失联或出现问题,等待72小时后仍未未解决,72小时后资金退还或赔付。 (3)收款只接受usdt转账,地址请提前确认,转错概不负责!usdt交易以实际到账usdt数量为准,usdt转出手续费及其他费用默认由转出方承担。 (4)交易过程中双方的一切沟通及交易需要在灰度官方担保人员创建的交易群中进行,出现纠纷后有群记录为凭证,一切私聊内容均不作为担保交易证据。 (5)交易过程中双方结算都必须由灰度担保进行结算,交易过程中一切私下结算都视为无效,并处罚10倍担保

👍1

4 Aug 2023, 08:10 UTC≈20,500 viewsread 7 August 2026
Photo

灰度担保 - 担保费用详情 (1)普通单笔类担保业务佣金抽取 4%,灰度嘉宾席会员普通单笔类担保业务佣金抽取2% (2)支付类、承兑换汇类担保业务佣金抽取0.2%,灰度嘉宾席会员支付类、承兑换汇类担保业务佣金抽取0.1% (3)担保在线时间为新加坡时间10-22时间段,上押时间24h,退押时间在10-22时间段 (4)最低担保佣金收取10u (5)佣金支付方需交易双方商议决定

4 Aug 2023, 08:09 UTC≈20,500 viewsread 7 August 2026
Photo

【交易详情内容】 供应方:名称 飞机id 交易地址: 需求方:名称 飞机id 交易地址: 商品: 单价: 总价: 担保押金: 担保佣金支付方: 放款标准: 其他: 注: 1、务必填写好每项担保内容,出现纠纷以担保内容为准 2、若有回复率、进粉率、退群率等等要求,请详细写在放款标准项目中,若没有其他要求,其他可不填 3、放款标准作为后期仲裁纠纷的唯一依据,尽量提供详细标准 4、所有担保群内的所有聊天记录均已储存在云端

4 Aug 2023, 08:09 UTC≈20,400 views0 reactionsread 7 August 2026
Photo

灰度担保 - 承兑换汇担保交易流程 (1)联系灰度官方担保人员(@HDDB_OFFICIAL),建立telegram交易群组,担保群组必须由此号建立,非此号建群交易一律无效。 (2)建群拉人后,由担保方置顶交易规则,双方必须按照规则进行交易,如果需要变更规则,由双方及灰度官方担保人员确定后重新发布规则并置顶,首条置顶必须是规则,规则不能编辑,若发现担保方修改规则,立刻暂停担保交易,并等待双方协商或灰度官方担保人员介入处理。 (3)在交易过程过若发生单方面违反规则并中止交易情况发生,属于恶意破坏交易,立即扣除全部货款或押金,灰度抽取担保佣金后进行赔付处理。 (4)交易过程中双方的一切沟通及交易需要在灰度官方担保人员创建的交易群中进行,出现纠纷后有群记录为凭证,一切私聊内容均不作为担保交易证据。 (5)交易过程中双方结算都必须由灰度担保进行结算,交易过程中一切私下结算都视为无效,并处罚10倍担保佣金,若押金不够则暂停作业直

4 Aug 2023, 08:09 UTC≈20,600 viewsread 7 August 2026
Photo

灰度担保 - 单笔交易及支付担保交易流程 (1)联系灰度官方担保人员(@HDDB_OFFICIAL),建立telegram交易群组,担保群组必须由此号建立,非此号建群交易一律无效。 (2)灰度官方担保人员(@HDDB_OFFICIAL)将供需双方交易详情汇总发布至建立好的telegram交易群组并置顶,交易双方确认无误后正式开始担保交易。 【交易详情内容】 (3)甲方(需方)将交易金额+担保金额转入灰度官方担保账户并提供转账成功凭证,灰度财务人员确认收款后通知交易双方进行交易。【担保费用】 (4)交易双方如要中止本次担保交易,联系灰度官方担保人员申请退押申请,经过灰度官方担保人员审核后,结算本次交易佣金,确定最后金额,灰度财务人员经本次交易双方确认后放款,并提供转账成功凭证,甲方(需方)确认收款后,结束本次担保服务。 提示: 一、明确供需双方关系 二、确认交易规则及地址 三、打款前确认地址,非灰度方错误,灰度概不

3 Aug 2023, 08:43 UTC≈20,600 viewsread 7 August 2026
Photo

灰度担保将于7月24日正式上线! 会员担保费率低至2%,支付担保费率低至0.1% 担保规则 灰度官方担保人员

Showing the 10 most recent of 10 posts we hold for @HDDB_GZ. 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.

Citation-graph rank

Citation-graph rank — 306,112 of 1,169,250entries 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 2 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.

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 August 2026 — this entry's latest reading, not the date you are reading this.

“灰度担保规则频道” (@HDDB_GZ), 407 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/HDDB_GZ.

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.