Channel
@ganjiang88888
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002329834456 |
|---|---|
| Type | Channel |
| Usernames | @chongshi @ganjiang88888 |
| Description | 干将68 @vip4280 pozhuo |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ganjiang88888 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 10:19 | 4 | no change |
| 13 Aug 2026, 10:03 | 4 | first reading |
15 posts held, back to 25 April 2025 — 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 15 posts for this entry, the most recent from 12 June 2025. An engagement rate over an empty window would be a number about nothing.
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.
😢NFT @trxjy 交易trx 😢NFT @kefumm 客服 😢NFT @trx50 😢NFT @trx50bot 😢NFT @pjtrx 😢NFT @vip415 😢NFT @vip764 😢NFT @vip1188 😢NFT @vip3111 😢NFT @vip0333 😢NFT @vip8969 😢NFT @vipxiao 😢NFT @kuvip 😢NFT @lllvip 😢NFT @vipeh 😢NFT @c6000 😢NFT @p8000 😢NFT @p10000 😢NFT @gt7777 😢NFT @mm234 😢NFT @dajjj 😢NFT @xiaojj 😢NFT @xiao00 😢NFT @xiao111 😢NFT @xiaoiii 😢NFT @xiao65 😢NFT @id837 😢NFT @sbfff 😢NFT @lexxx 😢NFT @…
😢NFT @naxia 拿下 😢NFT @miaokuan 秒款 😢NFT @chongkuan 充款 😢NFT @jingbiao 竞标 😢NFT @yuangao 原告 😢NFT @dinghang 鼎航 😢NFT @zhucang 逐仓 😢NFT @daichang 代偿 😢NFT @shuatie 刷贴 😢NFT @duipiao 兑票 😢NFT @qikuan 期款 😢NFT @waima 外码 😢NFT @waishui 外税 😢NFT @shoushui 收税 😢NFT @souguan 搜官 😢NFT @yansun 验损 😢NFT @caokong 操控 😢NFT @mianshen 免审 😢NFT @qie…
😢😢😢😢😢😢 😢NFT @duisao 对骚 😢NFT @luesao 略骚 😢NFT @wensao 纹骚 😢NFT @kuangsao 狂骚 😢NFT @qingsao 情骚 😢NFT @qiaosao 巧骚 😢NFT @niangsao 娘骚 😢NFT @chasao 叉骚 😢NFT @saoming 骚名 😢NFT @saogong 骚公 😢NFT @saoguai 骚乖 😢NFT @saoceng 骚层 😢NFT @saokang 骚康 😢NFT @saozhuai 骚拽 😢NFT @saogua 骚瓜 😢NFT @saoguo 骚过 😢NFT @saohen 骚痕 😢NFT @saonai 骚奶 😢NFT @saoqiu …
1
@chongshi 充实 pinned «😢NFT @chongshi 充实»
Photo, posted without a caption
😢NFT @chongshi 充实
https://fragment.com/username/@chongshi 充实
更多用户名频道 @tg8tg
@pingkuan 平款 @dekuan 得款 @miaokuan 秒款 @chongkuan 充款 @miaokuan 秒款 @miaokuanye 秒款爷 @miaokuanzhifu 秒款支付 @miaokuanzf 秒款支付 @miaokuanbot 秒款bot @mkzf0 @mkzf1 @mkzf2 @mkzf3 @mkzf4 @mkzf5 @mkzf6 @mkzf7 @mkzf8 @mkzf9 @trx50 @trx50bot 一套 用户名 出一出 客服 @j66666 干将 @ganjiang 🙃🙃 😫😢😢💋👌👌🏳️🌈
@naxia 拿下 @jingbiao 竞标 @duobiao 夺标 @hongpo 红婆 @renxuan 任选 @tiaomei 挑妹 @tiaoniu 挑妞 @yansun 验损 @mianshen 免审 @daichang 代偿 @souguan 搜官 @tengni 疼你 @touni 偷你 @qiani 掐你 @nieni 捏你 @zhuaini 拽你 @sounv 搜女 @xinnv 新女 @junnv 俊女 @qiunv 球女 @yingnv 鹰女 @zuyou 租友 @jiezhu 借助 @qikuan 期款 @liangpian 靓片 @lielong …
@oqian + @ofeng 😿 o签+o风(有钱又顺丰)o钱 😿
Showing the 12 most recent of 15 posts we hold for @ganjiang88888. 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 — 1,470,721 of 1,480,944entries 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.
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.
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.
“@chongshi 充实” (@ganjiang88888), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ganjiang88888.
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.