3 Jun 2023, 12:56 UTCviews —
久运担保-公群导航 @c_8888 pinned «✅久运资源担保集团✅ 💸人头卡商中介公群 💸 💸一道二道承兑公群 💸 💸资源软件担保公群 💸 💸 人头卡VIP小公群 💸 💸 一道二道小公群 💸 💸 久运娱乐频道公群 💸 正在对外招商，可提供客户流量， 资源扶持的帮助，招商合作联系：@JYDB ✅【担保业务办理请联系】✅ @JYDB_111 @JYDB_222 👏久运担保集团欢迎您的加入！»
Channel
久运担保-公群导航 @c_8888
@jiuyungong
2 usernames
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
87subscribers
-4 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 | -1001900662575 |
|---|---|
| Type | Channel |
| Usernames | @c_8888 @jiuyungong |
| Created | 11 May 2023 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/jiuyungong |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 20:36 | 87 | -1 |
| 15 Aug 2026, 20:42 | 88 | -2 |
| 9 Aug 2026, 14:31 | 90 | no change |
| 8 Aug 2026, 05:30 | 90 | -1 |
| 7 Aug 2026, 14:45 | 91 | first reading |
Engagement
13 posts held, back to 11 May 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 2 pagesof 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 13 posts for this entry, the most recent from 3 June 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
3 Jun 2023, 12:48 UTC≈38,300 viewsread 9 August 2026
✅久运资源担保集团✅ 💸人头卡商中介公群 💸 💸一道二道承兑公群 💸 💸资源软件担保公群 💸 💸 人头卡VIP小公群 💸 💸 一道二道小公群 💸 💸 久运娱乐频道公群 💸 正在对外招商，可提供客户流量， 资源扶持的帮助，招商合作联系：@JYDB ✅【担保业务办理请联系】✅ @JYDB_111 @JYDB_222 👏久运担保集团欢迎您的加入！
27 May 2023, 12:36 UTC≈78,400 viewsread 9 August 2026
💸 久运娱乐-百家乐 💸 💸 久运娱乐-红包扫雷 💸 💸 久运娱乐-骰子投注 💸 💸 久运娱乐-加拿大PC28 💸 💸 久运担保-裸播娱乐 💸 💸 久运担保-久运影视 💸 💸 久运担保-Chat GPT 💸 💸 久运娱乐-AG转转 💸
27 May 2023, 12:26 UTC≈76,300 viewsread 9 August 2026
一道二道（VIP小公群不公开，需要联系后面的群老板号进群，群老板如果更换用户名，需第一时间联系交易员修改联系用户名，用户名变更造成客户被拉假群的，群老板全责。） 进群后联系官方人员验证，走公群里交易，私聊交易或其他地方交易，无保障，所有后果自负 0018-风云精聊二道上押8888U，群老板联系方式：@fengyun688 6666- 星光二道公群上押15000U,群老板联系方式：@gg88011 8888-金开二道公群上押58888U,群老板联系方式：@fengxi9 0077无忧支付小额二道专群上押5000U，群老板联系方式： @wycyoyo 0166 Apple供久运小额二道专群上押5000U，群老板联系方式： @Apple_0529 0112 大G供久运精聊二道专群上押3000U，群老板联系方式：@GGGGG5868
27 May 2023, 12:20 UTCviews —
久运担保-公群导航 @c_8888 pinned «✅久运官方直营-久运娱乐红包扫雷✅ 由玩家发送发包指令在群内，红包机器人在群内按指令发包并扣除相应金额 举例：指令为 发100-5（机器人发送金额为100U的红包，抢包者抢到金额的尾数是5，即中雷） （用户中雷后需赔付发包者金额1.8倍即180U） （雷值可设置1-9 的任意一个数） https://t.me/+FgAfBCfwnZc4MmJh»
27 May 2023, 07:33 UTC≈46,000 viewsread 9 August 2026
人头卡：（VIP小公群不公开，需要联系后面的群老板号进群，群老板如果更换用户名，需第一时间联系交易员修改联系用户名，用户名变更造成客户被拉假群的，群老板全责。） 进群后联系官方人员验证，走公群里交易，私聊交易或其他地方交易，无保障，所有后果自负 久运1组 1888收常规pos一道卡上押58888U，群老板联系方式：@FUCK_BB 久运2组 0071久运专供谦儿 上押15000U，群老板联系方式： @qianer8 久运2组0056 久运专供起源 上押7000U，群老板联系方式：@yinuo0005
25 May 2023, 10:02 UTC≈42,400 viewsread 9 August 2026
✅久运资源担保集团✅ ✅资源担保✅ 💸 久运直营-口令票务 💸 💸 久运担保--USDT换TRX业务群 💸 018嗯嗯天眼TRX能量业务上押10000U 039资深美工视频P图证件急速上押3000U 019 花旗票务口令天眼公群上押15000U 0011人生赢家小额白资代付上押2000U 090小飞机票务会员开通上押3000U 017 AI换脸建模 | 搭建开发维护|上押10000U
25 May 2023, 06:49 UTC≈43,600 viewsread 9 August 2026
✅久运资源担保集团✅ ✅一道二道公群✅ 6666- 星光二道公群供押15000U 8888-金开二道公群供押58888U 9999-天成二道公群供押15000U 066- 东南亚收付通道回U供押30000U
19 May 2023, 11:51 UTC≈57,400 viewsread 9 August 2026
✅久运资源担保集团✅ ✅人头卡商中介公群✅ 💸 久运人头卡-交易俱乐部 💸 1888 收常规pos一道卡 上押58888U 369 三六九人头公群上押15000U 999长乐集团人头公群上押39999U 030 东阳人头公群 上押15000U 015无敌人头卡商公群上押15000U 888 后八轮人头公群 上押38888U 020汇丰人头公群上押30000U
17 May 2023, 11:00 UTC≈48,700 viewsread 9 August 2026
✅久运官方直营-久运娱乐红包扫雷✅ 由玩家发送发包指令在群内，红包机器人在群内按指令发包并扣除相应金额 举例：指令为 发100-5（机器人发送金额为100U的红包，抢包者抢到金额的尾数是5，即中雷） （用户中雷后需赔付发包者金额1.8倍即180U） （雷值可设置1-9 的任意一个数） https://t.me/+FgAfBCfwnZc4MmJh
14 May 2023, 03:01 UTCviews —
久运担保-公群导航 @c_8888 pinned «✅【久运担保】【正式起航】✅ 🔥久运官方群 @o_8888 🔥 🔥久运资源群 @e_8888 🔥 🔥人头卡交易 @t_8888 🔥 ——————————— 🔥 供需频道 @p_8888 🔥 🔥 仲裁频道 @f_8888 🔥 🔥 公群频道 @c_8888 🔥 🔥 曝光频道 @n_8888 🔥 🔥 公告频道 @m_8888 🔥 ——————————— ✅担保业务咨询联系: 💸久运1组：@JYDB_111 1组号码：+95 9691368666 💸久运2组：@JYDB_222…»
14 May 2023, 03:01 UTC≈47,600 viewsread 9 August 2026
✅【久运担保】【正式起航】✅ 🔥久运官方群 @o_8888 🔥 🔥久运资源群 @e_8888 🔥 🔥人头卡交易 @t_8888 🔥 ——————————— 🔥 供需频道 @p_8888 🔥 🔥 仲裁频道 @f_8888 🔥 🔥 公群频道 @c_8888 🔥 🔥 曝光频道 @n_8888 🔥 🔥 公告频道 @m_8888 🔥 ——————————— ✅担保业务咨询联系: 💸久运1组：@JYDB_111 1组号码：+95 9691368666 💸久运2组：@JYDB_222 2组号码：+95 9691369666 💸久运仲裁1：@jiuyunzhongcai1 仲裁1号码：+95 9670618121 💸久运仲裁2：@jiuyunzhongcai2 仲裁2号码：+95 9756285918 💸久运财务专用：@jiuyunfc888 财务号码： +95 9696077829 💸记账机器人：@…
Showing the 12 most recent of 13 posts we hold for @jiuyungong. 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,260,332 of 1,480,975entries 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
- 11
- 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
- 11
- vacant every time we have ever looked
@jiuyungong named 11 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.
@e_8888
named in 2 posts, 10 August 2026 – 10 August 2026
named in 2 posts, 10 August 2026 – 10 August 2026
@fengxi9
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
@jiuyunfc888
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
@jiuyunzhongcai1
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
@jiuyunzhongcai2
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
@jydbjsjbot
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
@jyrgznjqr
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
@jyybzsbot
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
@wycyoyo
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
@apple_0529
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
@yinuo0005
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“久运担保-公群导航 @c_8888” (@jiuyungong), 87 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/jiuyungong.
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.