Channel
@KK_010314
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
14subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002704607473 |
|---|---|
| Type | Channel |
| Username | @KK_010314 |
| Created | 17 June 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/KK_010314 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 01:30 | 14 | no change |
| 7 Aug 2026, 18:09 | 14 | first reading |
2 posts held, back to 17 June 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 2 posts for this entry, the most recent from 13 July 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
在 2025 年 7 月 1 日 13:00 @KK_010314 账号以及群组都被盗取， 导致损失资料，可恶的骗子竟让我拿 888 美金买自己的账号真的无比可恨可耻 2025 年 7 月 13 已成功把kk号注销掉 重新拿回用户用 @KK_010314 但是群组还拿不回来了，但避免更多人被骗 ：@KK_010314 ，这个账号用于频道， 旧频道和群组的账号被注销拿不回来了 旧一对一聊天群：@KK1V1c 旧推特网红视频：@KK_0103140 ———————————————————— 已更换群组和频道为初恋 初恋一对一客服账号：@a1v1aa 初恋双向机器人：@a1v1bot 全新裸聊价格表：@ll1v11 全新一对一选妃频道：@ll1v10 全新粉丝群组：@ll1v101
Channel created
Showing the 2 most recent of 2 posts we hold for @KK_010314. 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.
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.
@KK_010314 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“kk号被注销新号在频道” (@KK_010314), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/KK_010314.
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.