29 Jun 2023, 20:43 UTC≈10,700 viewsread 12 August 2026
待写入
Channel
汇币公告频道@huibigg
@huibigg
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
9subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001915874339 |
|---|---|
| Type | Channel |
| Username | @huibigg |
| Description | 为了防止失联，请大家一定要关注本频道 官方大群 @huibidb 公群频道 @huibigq 供需频道 @huibigx 公告频道 @huibigg 曝光频道 @huibibg |
| Created | 8 June 2023 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/huibigg |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 13:02 | 9 | no change |
| 8 Aug 2026, 06:49 | 9 | first reading |
Engagement
12 posts held, back to 8 June 2023 — 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 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 12 posts for this entry, the most recent from 29 June 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 12 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
28 Jun 2023, 20:04 UTC≈10,700 viewsread 12 August 2026
郑重声明：汇币担保是一家有原则底线的担保。涉及人口买卖类，毒品类，军火类业务一律不接，凡是涉及此类业务都是假群！
28 Jun 2023, 13:38 UTC≈10,500 viewsread 12 August 2026
官方频道/人员 专群业务公告 专群收费标准 公群业务公告 公群收费标准 纠纷处理原则 一键收藏汇币担保
27 Jun 2023, 14:58 UTC≈12,000 viewsread 12 August 2026
纠纷处理原则： 1.交易过程中供需双方一切沟通、协商、交易记录必须在官方交易群中进行，一切私聊内容均视为无效 2.交易过程中供需双方所有结算必须由汇币担保人员结算，如交易过程中供需双方私下结算则一律视为无效，并罚款3倍佣金，最低罚款500u，押金不够就补押金 3.交易过程中如出现货款被冻结、账户被冻结、货物被扣押等意外情况，平台会向供需双方提供货款冻结、账户冻结、货物扣押等相关证明，明确意外造成方后将由意外造成方承担全部损失 4.交易过程中如双方出现纠纷，首先以交易群中双方负责人协商一致的交易详情为准，如无法协商处理，超出交易规则内容范围可联系 @huibiaa 申请仲裁，不接受任何单方面说辞，双方商议一致的结果大于交易规则，平台最终仲裁结果交易双方必须无条件执行 5.交易过程中如双方出现分歧并协商一致同意中止交易，则退款清算过程中产生的手续费、货币折损、产品曝光、信息泄露、虚拟资产折损等所有损失由供需双方各自承担 6.交易过程…
27 Jun 2023, 13:20 UTC≈12,100 viewsread 12 August 2026
报备模版 （xxx公群编号）公群交易报备 交易双方：@xxx（客户） 交易金额：xxx（以U为单位） 交易日期：xx.xx 交易内容：xxxxx 交易要求：（需方和供方自行商） 单 击 自 动 复 制 注意：此报备模板适应任何行业，可以根据行业不同适当修改调整，对接的管理员，需要该管理员回复才算，证明此交易真实有效如到期没有报备产生纠纷不予受理，请交易双方注意
27 Jun 2023, 07:32 UTC≈12,000 viewsread 12 August 2026
公群收费标准 @huibigq 查档类、能量兑换、美工、烟酒类公群 押金1500U以上，担保费每月200U 号商、短信、zm、收粉、拉手、引流类公群 押金1500U以上，担保费每月400U 手机口、电销、三网卡、卡片、插卡公群 押金1500U以上，担保费每月500U 招车类 公群 押金1500U，担保费每月500U 人头同台、出国等类别公群 押金10000U以上，担保费每月500U 一二道支付类、承兑、代付类公群 担保费收取总量额的千分之一，最低收费100U起（五天结算一次) 承兑白资公群 押金15000U以上，担保费收取总量额的千分之一 ，最低收费20U起 其他类型业务 任意担保项目一事一议，通常普通商品担保费为总交易流水量或押金的百分之三（佣金最低20U起） 汇币公群担保负责人 @huibiaa 以上所有行业公群押金为最低标准，超过押金， @huibiaa 会提示补充押金或者暂停新增交易。 如发现…
26 Jun 2023, 15:35 UTC≈10,600 viewsread 12 August 2026
公群业务公告 私下交易担保方无法查看交易内容以及交易金额项目等各种原因，公群的意义也就不存在，私下交易的后果私下交易担保方无法查看消息准确性，出现争议问题无法辨别对错 只能自负 1.公群老板把规则发在群里[规则置顶]不能存在已编辑的交易规则，更新时要重新发布置顶，并且通知汇币公群管理审核。未置顶规则时交易公群老板全责 2.特殊行业，隐私东西可以私下发，如：账户、个人信息、数据、群码等不可避免的隐私内容可以允许私下，但交流必须在群，结算必须走群内，禁止私下交易出现问题概不负责 3.需方或者供方正在与公群老板交易时必须在群内报备金额避免后来者持续不断的交易，这种情况下导致超押金让公群老板跑路的，没有报备的一律不赔付 4.全部都有报备，导致多人累计超押金造成公群老板跑路，扣出压金的 20%为管理处理手续费再按照报备的先后顺序赔付群内报备正在交易金额 5.凡是有公群老板刻意要求私下交易，隐瞒交易无法让后来者在群内查看的可以…
25 Jun 2023, 08:37 UTC≈10,600 viewsread 12 August 2026
专群收费标准 1.支付类：币价7.7或者点位10个点以内佣金抽取千1 ，币价7.7或者点位10个点以上佣金抽取千2，每日停车结算（有交易就10u/天起，一个上下押周期最低20u）,付佣方由买卖双方商议决定 2.其他类型业务：0.3%费率，最低收取10USDT，收作为费用，退押金需要双方同意才能退
24 Jun 2023, 21:22 UTC≈10,600 viewsread 12 August 2026
专群业务公告 专群交易步骤 1.交易双方明确交易内容、业务和价格，自行协商 2.联系担保方汇币担保员 @huibiaa 拉群对接（其他人给你拉群都是骗子） 3.由担保方给供需双方拉群沟通（交易内容，规则等） 4.双方入群后,明确好交易规则并置顶 5.协商好后交押金到担保方 6.担保方确认收押后即可交易 专群注意事项 一、押金方式 押金只收USDT上押，不收RMB。关于USDT若遇到赔付或退还（清退）情况，不对币价市场汇率涨跌补偿，以实际到账USDT数量为准。 二、对接群介绍 1.交易过程中双方一切沟通、协商、交易记录必须在官方交易群中进行，私聊沟通没上押金就作业的，在第三方平台进行交易的出问题一律不负责。 2.有收了业务押金的对接群，就是一对一担保，出问题会使用群名上以及押金明细上备注的押金来赔付或退还。 3.群名上未写押金份额的，就是合作中且不担保或者终止合作且不担保的。 4.专群只认供需各一个负责人，请不要拉无关人员进…
12 Jun 2023, 18:59 UTCviews —
汇币公告频道@huibigg pinned «官方名单更新于 2023.10.14 汇币担保群组/频道 官方社群 @huibidb 公群频道 @huibigq 供需频道 @huibigx 公告频道 @huibigg 曝光频道 @huibibg 汇币担保工作人员 担保人员 @huibiaa （负责：拉专群.公群、验群、丢失群恢复、纠纷仲裁） 客服人员 @huibibb （负责：咨询、广告、会员、解封、投诉、资源对接） （汇币全拼音huibi➕编号aa、bb，为了更好…»
8 Jun 2023, 16:29 UTC≈10,600 viewsread 12 August 2026
官方名单更新于 2023.10.14 汇币担保群组/频道 官方社群 @huibidb 公群频道 @huibigq 供需频道 @huibigx 公告频道 @huibigg 曝光频道 @huibibg 汇币担保工作人员 担保人员 @huibiaa （负责：拉专群.公群、验群、丢失群恢复、纠纷仲裁） 客服人员 @huibibb （负责：咨询、广告、会员、解封、投诉、资源对接） （汇币全拼音huibi➕编号aa、bb，为了更好辨认官方工作人员只设定两位工作人员） 【认准以上官方人员/社群/频道ID】 1.认准汇币担保ID 2.担保员从来不会主动私聊 3.提前备注好担保用户名后后面加注（真） 4.担保只收USDT，不收人民币或其他货币 5.只要群管理是汇币担保认证用户名即为真 只需要核实群管理 要认真汇币担保号 分清楚个人简介与用户名的区别 核实清楚
8 Jun 2023, 16:17 UTCviews —
Channel created
Showing the 12 most recent of 12 posts we hold for @huibigg. 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 — 358,176 of 1,480,688entries 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@huibigg named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@huibiaa
named in 5 posts, 13 August 2026 – 13 August 2026
named in 5 posts, 13 August 2026 – 13 August 2026
@huibibb
named in 2 posts, 13 August 2026 – 13 August 2026
named in 2 posts, 13 August 2026 – 13 August 2026
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“汇币公告频道@huibigg” (@huibigg), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/huibigg.
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.