File, posted without a caption
👍1

Channel
@fykj88
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
4,117subscribers
-2,034 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003716094506 |
|---|---|
| Type | Channel |
| Username | @fykj88 |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/fykj88 |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 32% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 20:59 | 4,117 | -456 |
| 12 Sept 2026, 23:01 | 4,573 | -512 |
| 8 Sept 2026, 20:39 | 5,085 | -682 |
| 3 Sept 2026, 08:36 | 5,767 | -59 |
| 31 Aug 2026, 02:27 | 5,826 | -55 |
| 28 Aug 2026, 04:48 | 5,881 | -44 |
| 25 Aug 2026, 07:28 | 5,925 | -42 |
| 22 Aug 2026, 14:35 | 5,967 | -77 |
| 18 Aug 2026, 19:28 | 6,044 | -43 |
| 15 Aug 2026, 19:27 | 6,087 | -30 |
| 12 Aug 2026, 00:12 | 6,117 | -41 |
| 9 Aug 2026, 04:11 | 6,158 | +7 |
| 8 Aug 2026, 12:45 | 6,151 | no change |
| 8 Aug 2026, 12:32 | 6,151 | first reading |
10 posts held, back to 1 August 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 5 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 10 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
5 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 60.0% | |
| 👍 | 1 | 20.0% | |
| 👎 | 1 | 20.0% |
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 3 of the 10 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 1 August 2026 to 11 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.
File, posted without a caption
👍1
1.修复部分设备执行不了程序的问题 2.改善追踪概率的算法
🙂老牌项目锦鲤 回归改名🔤🔤 密钥透视 断点追锁 无模块陀螺仪漏打 市面最丝滑流畅的绘制效果,我们稳定性全网最强 初次购买封号可售后 现在还能免费领卡玩 点我零手续费卡网下单 注意事项+介绍(必看) 成为代理 反馈/售后: @fyalice
❤1👎1
GK作者亲自反馈
❤️扶摇传媒计划-【免费卡体验】❤️ 🎞发布关于GK 内核的视频 !第一时间置顶评论:fykj88超过5分钟置顶无效 10点赞=GK KERNEL 6H卡密(仅一次) 100点赞=10¥ 1000点赞=88.8¥ 或 GK代理+周卡 5000点赞=88.8¥+GK代理位+周卡 带上截图找我审核 @fyalice
❤2
🔤🎞🔤GK内核代理位 代理有代理群,反馈图共享,有什么问题随时联系我。 🔤❤️🔤扶摇科技扶持计划 代理位下单自动发放6小时卡密 前5条作品每条作品赠送6h卡密*2 普通代理位👝 100永久代理 对接6/50/125 增周卡一张做流量,当月出售额>300赠周卡*2 金牌代理🛑 月售额>500 对接6/45/115 每个月赠月卡一张,月售额掉300以下降级为普通代理 核心代理位💎 月售额>2000 对接5/38/100 赠送永久卡,核心代理免费配置引导页(服务器,域名,网站搭建全部打包搞好给你) 卡网下单后联系我 @fyalice 卡网链接:点我成为代理 每月发两条视频以上否则删除代理位❗️ 最低售价不得低于10/65/210
扶摇-GK kernel官方 pinned «购买链接:https://shop.368fk.cn/shop/fuyao 购前看卡网介绍 下单后看注意事项 反馈/售后: @fyalice 完整介绍+注意事项(必看)»
购买链接:https://shop.368fk.cn/shop/fuyao 购前看卡网介绍 下单后看注意事项 反馈/售后: @fyalice 完整介绍+注意事项(必看)
GK战神反馈 官方卡网下单:https://shop.368fk.cn/shop/fuyao 反馈联系 @fyalice
🔤🔤 🔤🔤🔤🔤🔤 26年顶尖和平外挂 原锦鲤内核现以正式回归🎞 🔤❤️🔤扶摇科技:🙂 💎1-全网最强售前售后-root教程 提供所有可开挂的设备的保姆级教程及资源包,没玩过内核的小白请无脑选择我们,全天在线客服。保证全程耐心售后 💎2-老牌项目回归-全网最稳 🔤锦鲤内核🔤以极致流畅的绘制和优秀的自瞄手感为招牌我们采用市面最火爆的1️⃣硬件断点追锁2️⃣无模块陀螺仪自瞄 💎3-密钥透视-绘制全局自由调节 绘制全选项支持调节,密钥透视功能功能,还有信号圈预测,投掷物预判等功能,帧率支持自由调节,渲染模型功耗低到离谱,最新推出支持新老模型绘制自由切换 💎4-战斗模式-每类枪械单独调节 自瞄手感遥遥领先市面普通内核科技,每类枪械参数支持单独调节,独家战斗模式按钮,采用独家官方赛事同款血条,战斗体验拉满。 独家驱动😀局内解密😀 硬件断点😀投掷预判😀 极低功耗😀密钥透视😀 拒绝拉闸十年 拒绝垃圾二改 💸GK项目招收代理,福利拉满💸…
Showing the 10 most recent of 10 posts we hold for @fykj88. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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.
@fykj88 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“扶摇-GK kernel官方” (@fykj88), 4,117 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/fykj88.
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.