Telegram RegisterThe public register of Telegram
Telegram profile photo for FuckCheat

Channel

FuckCheat

@FChsnb

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

109subscribers

+68 since we began measuring on 26 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003879755207
TypeChannel
Username@FChsnb
Created12 September 2026 — measured — dated from the channel’s first post
First recorded26 September 2026
Last confirmed live13 November 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/FChsnb

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 47% 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

411117626 September 2026 — 41 subscribers26 September 2026 — 41 subscribers4 October 2026 — 97 subscribers14 October 2026 — 98 subscribers22 October 2026 — 95 subscribers28 October 2026 — 111 subscribers4 November 2026 — 110 subscribers13 November 2026 — 109 subscribers10926 September 202613 November 2026
8 measurements spanning 48 days, net +68. 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 31–122 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 18:10109-1
4 Nov 2026, 03:38110-1
28 Oct 2026, 23:31111+16
22 Oct 2026, 07:4195-3
14 Oct 2026, 01:5198+1
4 Oct 2026, 12:5697+56
26 Sept 2026, 20:2241no change
26 Sept 2026, 19:4741first reading

Engagement

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

Reaction mix

3 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3100.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 2 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 3 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 12 September 2026 to 26 September 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

25 Sept 2026, 15:49 UTC590 viewsread 26 September 2026

买点卡吧😭😭😭 卡网:https://shop.368fk.cn/shop/1uuu

24 Sept 2026, 11:41 UTC287 viewsread 26 September 2026

FuckCheatAPK更新通知 [+]更换数据库 [+]增加CFG云上传 [+]增加新协议 FuckCheat和平精英&&PUBGM更新通知 [+]增加同步用户信息功能 [+]增加加载CFG功能 Tips:必须登录才有上传CFG功能 注册必须使用有效时间卡密作为凭证 一个人只能上传50份配置 有内容检测 非配置自动拒绝上传 具有危险命令检测 拒绝上传一切linux命令 绑定配置流程: 打开APK绑定人登录完成->被绑定人登录完成-> 被绑定人发送用户名->绑定人上传云配置输入被绑定人用户名-> 上传->被绑人打开UI点开主页的账号->加载配置

20 Sept 2026, 15:09 UTC134 viewsread 26 September 2026

FuckCheatPUBGM更新通知 [+]修复防录屏在直播时的问题 [+]修复广角一把一开问题 [+]补录手持/对象信息栏枪械图片 FuckCheat和平更新通知 [+]更新数组/坐标解密 [+]优化陀螺仪自瞄压枪逻辑 [+]更改陀螺仪自瞄输出为自选翻转 [+]修复过强制防录屏 Tips:密钥绘制任然可用 PUBGM后续的图片物资绘制会慢慢增加 但不会更新辅助版本 图片改为下发模式 延续几个版本前更新的下发资源包形式无需更新辅助

19 Sept 2026, 07:00 UTC132 viewsread 26 September 2026
File

FuckCheatPUBGM更新通知 [+]增加陀螺仪霰弹枪自瞄 [+]增加霰弹枪开火自瞄 [+]增加霰弹枪吸附自瞄 [+]修复守护进程导致的UI卡住

12 Sept 2026, 04:57 UTC≈1,130 views1 reactionsread 26 September 2026
Photo

FuckCheatPUBGM更新通知 [+]更新闪框解密 [+]重构引导页 [+]重构全局人数 [+]重构动态圈 [+]增加霰弹枪追踪概率调节 [+]修复骨骼混乱 [+]增加自瞄追踪提示 [+]优化控件排版解决混乱 [+]修复主驱动无法读写 - English - [+]Update Coordinates [+]Refactor guide page [+]Refactor global count [+]Refactor dynamic zone [+]Add shotgun tracking prob.adj [+]Fix bone disorder [+]Add aimbot tracking hint [+]Optimize UI layout [+]Fix Driver Not Work FuckCheat和平精英更新通知 [+]重构引导页 [+]重构通知栏 [+]优化控件排版 [+]重构动态追踪/自瞄…

❤1

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

Forward network

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.

Mentions

Named by 2 registered channels — 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.

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.

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

“FuckCheat” (@FChsnb), 109 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/FChsnb.

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.