Channel
@xianyuczk6
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
61subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001482401825 |
|---|---|
| Type | Channel |
| Username | @xianyuczk6 |
| Created | Between 1 April 2019 and 16 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 5 times, most recently 15 September 2026 |
| On Telegram | t.me/xianyuczk6 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 08:12 | 61 | -1 |
| 10 Aug 2026, 03:46 | 62 | no change |
| 7 Aug 2026, 01:06 | 62 | first reading |
18 posts held, back to 16 August 2021 — 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 page of 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 18 posts for this entry, the most recent from 8 March 2023. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The channel will remain accessible for all users.
！
这一阵子没有新客户，也没法信誉截图，过几天再发，先凑合看上边的！
闲鱼🦇充值卡🐟话费卡⚠️洗钱 跑分 pinned «今日晚有优惠，一批9张移动面值一百的要处理，仅需5XX 抢的预订了赶紧！ @GNMYYDW»
今日晚有优惠，一批9张移动面值一百的要处理，仅需5XX 抢的预订了赶紧！ @GNMYYDW
闲鱼 充值卡 搞钱 回血 上岸 唯一客服💁🏼 @GNMYYDW 支持单张测试哦～ 点击“频道”进入频道了解详情～ 长话短说，懂的来滴滴
购卡滴滴 @GNMYYDW
用户名已更换 @GNMYYDW
快来上车搞钱了！
单张测试以此类推
第一张85
第二张90
Showing the 12 most recent of 18 posts we hold for @xianyuczk6. 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.
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.
@xianyuczk6 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.
References a handle that is not a live channel — we have no record it ever was one.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“闲鱼🦇充值卡🐟话费卡⚠️洗钱 跑分” (@xianyuczk6), 61 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/xianyuczk6.
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.