😢NFT @caokong 操控

Channel
@caokong 操控
@caokong6
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
3subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002156636489 |
|---|---|
| Type | Channel |
| Usernames | @caokong @caokong6 |
| Description | 更多🆔用户名 @tg8tg 干将4 @vip3780 |
| Created | 25 July 2024 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/caokong6 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 18:03 | 3 | no change |
| 12 Aug 2026, 04:32 | 3 | first reading |
Engagement
8 posts held, back to 25 July 2024 — 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 8 posts for this entry, the most recent from 10 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 2
- Links
- 2
Lifetime counters from Telegram’s own channel header, read 13 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
NFT 官网一口价,喜欢的直接拍。🧧 更多nft用户名 @tg8tg 🇸🇰 NFT列表: 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- 16- 17- 18- 19- 20- usdt 购买联系 @ganjiang 干将 @NFT899 已上链用户名1000个。 😢NFT @zouyan 走烟(走私烟) @tg8tg @tgtg8 @tgtgQ @o66666 @j66666 @p66666
Channel photo updated
https://fragment.com/username/@caokong 操控
用户名nft出售列表(4) 😢NFT @zhaodie 找爹 赵蝶 😢NFT @duichang 对唱 😢NFT @zhaofen 找粉 😢NFT @zanfen 赞粉 😢NFT @shangliao 上料 😢NFT @kuojun 扩军 😢NFT @yingzhan 影展 迎战 😢NFT @lazhan 蜡展 拉战 😢NFT @guochuang 国创 😢NFT @guozuan 国钻 😢NFT @xianguan 县官 现管 😢NFT @xunguan 迅冠 勋官 😢NFT @paoguan 炮管 跑官 😢NFT @paobang 炮榜 炮棒 😢NFT @weiluo 微裸 微络 😢NFT @panshe 盘蛇 盘社 😢NFT @panzheng 盘整 潘正 😢NFT…
@yansun 验损 @mianshen 免审 @souguan 搜官 @xinnv 新女 @junnv 俊女 @zuyou 租友 @jiezhu 借助 @qikuan 期款 @liangpian 靓片 @cailong 彩龙🐉 @dinghang 鼎航 @niubie 牛瘪 @xiangui 显贵 @caokong 操控 @youjing 悠静 @goudang 勾当 @jianian 嘉年 @tunbao 臀宝 @tunwang 臀王 @linxilei 林熙蕾
@caokong 操控
Channel created
Showing the 8 most recent of 8 posts we hold for @caokong6. 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 — 600,034 of 1,340,412entries 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 32 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@ganjiang88888 · 42 posts@goudang 勾当
@goudang8 · 22 postso签+o风(有钱又顺丰)o钱
@oqian · 32 posts挑美 频道
@qiankou1 · 102 posts刷贴带贴 飞机微信用户名
@shuatiebot · 62 posts索达id全拼@suoda出售。老频道 带贴+用户名+微信ws+飞机号 代开会员
@suoda · 42 posts老白干🍷🍷 @laobaigan 频道
@tgtto · 382 posts@zhaofen 找粉
@zhaofen1 · 42 postsNFT @bindao 滨岛 宾道
@bindao8 · 21 postNFT @chengtai 𫍯泰
@chengtai · 31 postNFT @dangyong 当勇
@dangyong1 · 31 postNFT @diaoyang 屌样
@diaoyang1 · 21 post@fj4444
@FJ4444 · 21 post干将(出货 频道)
@ganjiangmy · 101 post@guochuang 国创
@guochuang1 · 31 post@kangjuan 康娟
@kangjuan · 31 post@kouban 扣板
@koubanbot · 31 post@panshe 盘蛇🐍 盘社
@panshebot · 31 post@qiongshang 琼商
@qiongshang · 21 post@qunshi 群狮
@qunshi1 · 31 post屈晴 趣情
@quqing_bot · 21 post@tuoling 驼铃
@tuoling1 · 21 post@xinleng 心冷 新冷
@xinleng8 · 21 post@zuyou 足友 租友
@zuyou1 · 51 post
Names
Channels on the register whose handles appear in this channel's posts.
@goudang8 · 22 postsNFT @bindao 滨岛 宾道
@bindao8 · 21 post@congzheng 从政
@congzheng1 · 21 postNFT @dangyong 当勇
@dangyong1 · 31 postNFT @diaoyang 屌样
@diaoyang1 · 21 post@fj4444
@FJ4444 · 21 postNFT @hongkuo 宏阔
@hongkuobot · 21 postNFT @kangxun 康讯
@kangxunbot · 31 postNFT @kuojun 扩军
@kuojun1 · 41 post@liangpian 靓片
@liangpian1 · 81 postNFT @mianshen 缅神 免审
@mianshen1 · 21 post@panshe 盘蛇🐍 盘社
@panshebot · 31 postNFT @panzheng 盘整 潘正
@panzheng1 · 31 postNFT @paobang 炮榜 炮棒
@paobang1 · 21 post屈晴 趣情
@quqing_bot · 21 post@souguan 搜官
@souguanbot · 21 post@tunbao 屯宝
@tunbao1 · 21 post@tunwang 臀王
@tunwang · 21 post@tuoling 驼铃
@tuoling1 · 21 postNFT @xianguan 县官 现管
@xianguan1 · 21 post@xinleng 心冷 新冷
@xinleng8 · 21 post@zhaofen 找粉
@zhaofen1 · 41 post@zhuailongbot
@zhuailongbot · 41 postNFT @zhuangdi 庄帝
@zhuangdi1 · 31 post
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
- 1
- 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
- 1
- vacant every time we have ever looked
@caokong6 named 1 handle 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.
named in 1 post, 14 August 2026 – 14 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“@caokong 操控” (@caokong6), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/caokong6.
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.