Telegram RegisterThe public register of Telegram
Telegram profile photo for 好旺担保@zhuanqun专群频道

Channel

好旺担保@zhuanqun专群频道

@zhunaqun

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

202subscribers

-2 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-1002235452924
TypeChannel
Username@zhunaqun
Created8 June 2024measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/zhunaqun

Growth

2022042037 August 2026 — 204 subscribers8 August 2026 — 204 subscribers16 August 2026 — 202 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, net -2. 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 202–204 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 17:04202-2
8 Aug 2026, 11:18204no change
7 Aug 2026, 10:30204first reading

Engagement

7 posts held, back to 8 June 2024the 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 7 posts for this entry, the most recent from 8 June 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Jun 2024, 00:36 UTC≈37,700 viewsread 8 August 2026

五、专群的退押流程: 1、上押方提出提押 2、交易方负责人确认双方账目结清,无纠纷 3、上押方负责人确认退押地址 4、结清担保佣金后退押 5、退押流程一般1个小时内完成

8 Jun 2024, 00:35 UTC≈37,700 viewsread 8 August 2026

好旺担保佣金收费标准: 1、美金买卖USDT和换汇:佣金为成交价0.2%(最低20美金/20U起),付佣方由买卖双方商议决定; 2、代付代收交易:佣金为交易量的0.1%,每日停车结算(有交易就10u/天起,一个上下押周期最低20u),付佣方由买卖双方商议决定;上押800u起; 3、普通商品交易:佣金为成交价3%(最低20美金/20U起),付佣方由买卖双方商议决定; 4、大公群不收取开群费,推广费200u,以后每月续费500u,上押15000u起,下押关群。 5、VIP群门票200U/位,供求信息300U/条。 [收费标准]已于2024年9月22日更新

8 Jun 2024, 00:35 UTC≈37,400 viewsread 8 August 2026

三、专群注意事项: 1、我们拉群的对接人是 好旺担保 @hwdb ,如果是其他人联系你要给你拉群,都是骗子。 2、如何确定是真群,不是骗子拉的假群?点开我们机器人 @he444bot 发送群编号,可以查看该编号有没有真群,如果有真群,再点开群内成员,看看和你有没有共同群是这个群,如果有证明是真群 3、好旺担保上押TRC20地址: 上押地址 1.专群1、2组 前五位TX36x中五位XUSBC后五位VVter 2.专群3、4组 前五位TVf2N中五位DD2cL后五位r68NH 3.专群5、6组 前五位TYQLm中五位Usfpx后五位qZfNe 4.公群组 前五位TKBiA中五位HYrgo后五位J2ugZ 5.游戏公群、客服组(发供需、买门票) 前五位TL8TP中五位aAhXL后五位9SwEf 6.海外直通车公群、海外代收代付专群 前五位TV8FY中五位Bceyn后五位ZY4Go 请在上押付款时联系本群交易员或客服

8 Jun 2024, 00:35 UTC≈36,800 viewsread 8 August 2026

二、专群的交易步骤: 1、交易双方谈好交易内容 2、联系我们拉群,拉群联系 @hwdb 3、交易双方进群谈好交易规则 (交易内容、费率、汇率等等) 4、打押金 5、我们整理好交易规则并置顶 6、开始交易 7、双方账目结算清楚 8、扣除佣金后下押

8 Jun 2024, 00:34 UTC≈36,700 viewsread 8 August 2026

一、什么是专群? 专群是一对一交易群,里面只能一个卖家一个买家。专群也叫私群,是相对于公群而言的,公群参看 @hwgq 。 由于专群是一对一交易群,如果拉多个交易方在一个专群交易会被罚款。 为什么专群不允许多个交易方呢? 拿跑分类专群来说:如果1个车队多个料方,第一容易打超,第2容易回错款,比如:需要给a回款的时候,b发个地址,结果回给b了。

Showing the 7 most recent of 7 posts we hold for @zhunaqun. 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 — 1,196,157 of 1,481,306entries 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 1 registered channel — 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.

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

“好旺担保@zhuanqun专群频道” (@zhunaqun), 202 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/zhunaqun.

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.