Telegram RegisterThe public register of Telegram
Telegram profile photo for CK代发

Channel

CK代发

@CK6223

On this record: Topic · Growth · Engagement · Posts · Cite this entry

1subscribers

-1 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-1003729496193
TypeChannel
Username@CK6223
Created28 January 2026 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live6 October 2026
Measurements held3
Confirmed unchanged5 times, most recently 6 October 2026
On Telegramt.me/CK6223

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 3 October 2026 and assigned it the closest of 31 fixed categories, at 40% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

121.57 August 2026 — 2 subscribers14 August 2026 — 2 subscribers28 August 2026 — 1 subscribers7 August 202628 August 2026
3 measurements spanning 21 days, net -1. 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 1–2 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 12:161-1
14 Aug 2026, 02:332no change
7 Aug 2026, 18:252first reading

Engagement

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

Recent posts

28 Jan 2026, 12:36 UTC35 viewsread 14 August 2026

🛜过年期间不放假.捞票子的来🛜 🔥上浮0.36高价收U.🔥 搬砖日赚 5000 U➕ 搬砖日赚 5000 U➕ 搬砖日赚 5000 U➕ ✅量小可微信支付宝口令 给你 ✅量大可柜台存现,可线下送现 ✅先款给你后回我U,安全无风险 ✅另外招:每日搬砖人员赚汇率差 ✅📲日赚5000U+项目稳定 (无套路:不发链接不扫码,无需上押,小白可带) 🔥流程: 1️⃣-先准备好U 2️⃣-财务先打钱 3️⃣-你再回我U 👆承若纯白资金👆 🉑先转钱给你 —- 🉑先转钱给你 🉑先转钱给你 —- 🉑先转钱给你 💰支持全国送现金,送现金💰 🚘量大可安排 现存或送现🚘 🏧量大可安排 现存或送现🏧 联系收U客服: @wh6868 U搬砖赚差价: @wh6868 双向联系客服: @lide3838bot ✅注意:骗子,P图,假U,黑U口嗨墨迹勿扰

28 Jan 2026, 12:29 UTC30 viewsread 14 August 2026

🚀B5U|币无忧 -hk信托旗下国际承兑,U兑换支付宝微信自助直兑平台(保永久司法)自助操作,绑定下级无风险拿佣金🎯助力U商 服务U商,自助换汇平台,u换人民币平台,100%白资 @grace19888

Showing the 3 most recent of 3 posts we hold for @CK6223. 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.

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

“CK代发” (@CK6223), 1 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/CK6223.

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.