纯巨魔版本已上架卡网

Channel
IOS小T大王
@TK99KK
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
10,179subscribers
+2,755 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002322930592 |
|---|---|
| Type | Channel |
| Username | @TK99KK |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 October 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 28 October 2026 |
| On Telegram | t.me/TK99KK |
Topic
Hacking & security — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 09:54 | 10,179 | -15 |
| 27 Oct 2026, 06:34 | 10,194 | -12 |
| 26 Oct 2026, 05:08 | 10,206 | -17 |
| 25 Oct 2026, 02:28 | 10,223 | -14 |
| 24 Oct 2026, 04:11 | 10,237 | -3 |
| 23 Oct 2026, 03:21 | 10,240 | -4 |
| 22 Oct 2026, 01:47 | 10,244 | -13 |
| 20 Oct 2026, 23:19 | 10,257 | -3 |
| 19 Oct 2026, 20:40 | 10,260 | -3 |
| 18 Oct 2026, 21:59 | 10,263 | -4 |
| 18 Oct 2026, 01:06 | 10,267 | +2 |
| 16 Oct 2026, 22:39 | 10,265 | -17 |
| 14 Oct 2026, 21:19 | 10,282 | -9 |
| 13 Oct 2026, 10:46 | 10,291 | -23 |
| 9 Oct 2026, 09:40 | 10,314 | -22 |
| 5 Oct 2026, 00:39 | 10,336 | -41 |
| 27 Sept 2026, 23:42 | 10,377 | +3,049 |
| 18 Sept 2026, 04:38 | 7,328 | -22 |
| 14 Sept 2026, 01:39 | 7,350 | -13 |
| 10 Sept 2026, 18:40 | 7,363 | first reading |
Engagement
38 posts held, back to 30 July 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 15 pages 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 38 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 4m 40s
- Average length
- 35s
Measured directly from 8 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
66 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 74.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 49 | 74.2% | |
| ❤ | 9 | 13.6% | |
| 👎 | 6 | 9.09% | |
| 🤔 | 2 | 3.03% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 21 of the 38 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 66 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 30 July 2026 to 27 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
驱动是纯巨魔内核级 15-16.51,不卡屏,不重启,嘎嘎流畅 高阶仿生拟态瞄准引擎,复刻真人手动运动曲线,搭载运动轨迹预测模型,摒弃参数调节,实现全自动前置预判锁位 功能:人物绘制 射线 数量 骨骼 名字 距离 防录屏
谁白嫖了我一张周卡,四张天卡 😭 绷不住了,我刚切了支付接口就买了,钱没收到,卡密发货了赶紧来找我不然删卡了 😭
❤4
CCVIP漏打反馈微信支付正常使用
最新版本公益,打开就能用无需关闭网络
👍7
等会出纯巨魔版本仅支持 15-16.51 卡密通用,不会重启不卡屏
👍4❤1
🎁8月27日更新网盘换 优化绘制 优化自瞄更像模拟真人更稳定 优化少部分人掉绘制问题 修复15系列重启问题
👍4
漏打反馈
👍2❤1
File, posted without a caption
反馈
👍2
漏打反馈
👍1
File, posted without a caption
Showing the 12 most recent of 38 posts we hold for @TK99KK. 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 October 2026 — this entry's latest reading, not the date you are reading this.
“IOS小T大王” (@TK99KK), 10,179 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/TK99KK.
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.