Telegram RegisterThe public register of Telegram
Telegram profile photo for 六花频道

Channel

六花频道

@liuhuayyds6666

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry

57,059subscribers

+6,038 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001999624004
TypeChannel
Username@liuhuayyds6666
Description唯一交流群: @liuhuayyds666
CreatedBetween 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/liuhuayyds6666

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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

51,02157,05954,0407 August 20269 November 2026
63 measurements spanning 94 days, net +6,038. 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 50,115–57,965 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
9 Nov 2026, 10:5557,059+96
8 Nov 2026, 01:2056,963+70
6 Nov 2026, 20:2456,893+63
5 Nov 2026, 20:5156,830+36
4 Nov 2026, 22:0656,794+54
3 Nov 2026, 18:5856,740+25
2 Nov 2026, 21:2656,715+78
1 Nov 2026, 21:4456,637+65
31 Oct 2026, 22:2856,572+128
31 Oct 2026, 01:3956,444+96
29 Oct 2026, 22:5756,348+74
28 Oct 2026, 21:2756,274+96
27 Oct 2026, 18:4756,178+129
26 Oct 2026, 17:1656,049+91
25 Oct 2026, 13:4055,958+145
24 Oct 2026, 11:0955,813+116
23 Oct 2026, 09:1955,697+48
22 Oct 2026, 06:1455,649+58
21 Oct 2026, 00:0855,591+30
20 Oct 2026, 00:3655,561first reading

Engagement

116 posts held, back to 16 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 195 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
27.6%
avg views ÷ 57,059 subscribers
Avg views / post
15,700
18 posts measured
Reaction rate
1.53%
reactions ÷ views · ER floor
Posts in window
21
of 116 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 November 2026
Posts held116 (16 July 2026 – 8 November 2026)
Views total283,420
Reactions total4,323
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 02:16 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
434
Videos
33
Links
135

Lifetime counters from Telegram’s own channel header, read 10 November 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.

Video runtime
2m 19s
Average length
23s

Measured directly from 6 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

10,561 reactions across 102 posts, in 36 distinct kinds. The most used accounts for 54.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5,70654.0%
❤3,25730.8%
💩5004.73%
👎1841.74%
🖕1631.54%
🍌1000.947%
🤣950.9%
🤔850.805%
🤡780.739%
😍460.436%
🤬460.436%
🥰440.417%
🌭340.322%
👏320.303%
🔥310.294%
🤮270.256%
🤩200.189%
😁180.17%
😱180.17%
🌚100.095%
16 further kinds670.634%

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 102 of the 116 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 10,561 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 116 most recent posts we hold, published 16 July 2026 to 8 November 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

Telegram’s own ‘edited’ marker: 8 of 21 posts held from the last 30 days (38.1%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

8 Nov 2026, 04:42 UTC≈3,610 views140 reactionsread 10 November 2026

六花CFM内核98 适配断点:TWT/RThook/dit_ok/dit_kpm硬件断点 修复追踪骨骼高矮不准问题 修复林羽追踪掉帧严重问题 适配:dit_ok/dit_kpm138 适配其他驱动内核隐藏功能 追踪比较推荐pte断点比较稳 硬件断点追踪容易七天 追踪部位就是调节部位即可 淋雨追踪掉帧发烫建议用其他驱动 如果林羽追踪开启玩会失效,重新打开追踪即可 有问题反馈 @liuhuayydsnb 更新地址:https://drive.uc.cn/s/e71a3502092d4

👍117❤9👎7🌚2💩2🤬2🔥1

4 Nov 2026, 07:47 UTC≈9,010 views121 reactionsread 10 November 2026

下个版本将适配其他驱动的硬件断点追

👍109💩8❤4

31 Oct 2026, 11:54 UTC≈13,600 views1,410 reactionsread 10 November 2026

爱玩CFM给我扣爱心表情包❤️

❤1,180👍123💩64🍌13🖕9🌭5💔4🤬4

29 Oct 2026, 05:08 UTC≈16,700 views134 reactionsread 10 November 2026

淋雨驱动断点追踪掉帧的,建议换其他驱动的pte断点,其他驱动断点追踪不掉帧

👍106💩14❤11🫡2🤡1

27 Oct 2026, 13:53 UTC≈18,600 views146 reactionsread 10 November 2026

硬件断点:天堂驱动 PTE断点:淋雨/RThook全新V1.0/天堂/GT1.1 使用:先进入靶场后开启断点追踪追踪参数全部先默认,然后测试一下追踪效果,没问题后再进入实战,用瞄准骨骼百分百准 吃鸡模式:追踪需要重新调整那个追踪落点补偿才能打得准人 提示:退出游戏之前,记得关闭断点追踪,不然下次打开游戏会出现白屏,出现白屏后重启手机解决

👍108❤25💩11🔥2

26 Oct 2026, 06:41 UTCviews —

六花频道 pinned «👿六花CFM断点追踪97 1️⃣新增硬件断点/pte断点追 2️⃣适配天堂670/淋雨7.8/GT1.1 3️⃣新增关于手机品牌内核CPU占用温度之类的信息 4️⃣追踪:可调节概率/可调节追踪落点位置 5️⃣硬件断点:天堂驱动 6️⃣PTE断点:淋雨/RThook全新1.0/天堂/GT1.1 7️⃣追踪支持:爆破/团战/生化/荒岛吃鸡 8️⃣重要提示:退出游戏之前记得关闭断点追踪,否则下次进入游戏会出现白屏,如果出现白屏重启手机即可 👀通用卡密:liuhuayyds6666 📱有问题请反馈 @liuhuayydsnb…»

26 Oct 2026, 06:35 UTC≈16,800 views210 reactionsread 10 November 2026

👿六花CFM断点追踪97 1️⃣新增硬件断点/pte断点追 2️⃣适配天堂670/淋雨7.8/GT1.1 3️⃣新增关于手机品牌内核CPU占用温度之类的信息 4️⃣追踪:可调节概率/可调节追踪落点位置 5️⃣硬件断点:天堂驱动 6️⃣PTE断点:淋雨/RThook全新1.0/天堂/GT1.1 7️⃣追踪支持:爆破/团战/生化/荒岛吃鸡 8️⃣重要提示:退出游戏之前记得关闭断点追踪,否则下次进入游戏会出现白屏,如果出现白屏重启手机即可 👀通用卡密:liuhuayyds6666 📱有问题请反馈 @liuhuayydsnb 这么努力给你们更新想玩的功能,大家多多转存一下 还有多多推广一下我的辅助 📱下载地址:https://drive.uc.cn/s/05b7f575079b4

👍123❤39💩37🥰5👏4🔥2

26 Oct 2026, 04:14 UTC≈14,400 views121 reactionsread 10 November 2026
Photo

预计今天发布断点追踪版😁

👍87💩13❤11💯5🤔3🍾2

25 Oct 2026, 07:01 UTC≈13,800 views210 reactionsread 10 November 2026
Video

断点追踪打生化太爽了,嘎嘎乱杀😍 内核断点追踪正在完善,等待我更新

👍175❤10💩10🍾5👎5🤔5

24 Oct 2026, 07:43 UTC≈14,200 views291 reactionsread 10 November 2026
Video

👿CFM内核断点追踪演示视频❤️

👍236😍27💩11❤10😱6👏1

19 Oct 2026, 06:58 UTCviews —

六花频道 pinned «👿六花CFM内核96 1️⃣绘制/手持/雷达/加密判断 2️⃣普通触摸/内核触摸/无模块陀螺仪/内核陀螺仪 3️⃣隐藏进程/隐藏节点/隐藏路径 4️⃣驱动管理:实时切换多种驱动 5️⃣自定义绘制:人物颜色/文字大小 6️⃣切换窗口主题:白色主题/深色主题 7️⃣防录屏/无后台/录制截图/高端UI 🔒通用卡密:liuhuayyds6666 📱有问题请反馈 @liuhuayydsnb 📱下载地址:https://drive.uc.cn/s/9be858fa69de4»

Showing the 12 most recent of 116 posts we hold for @liuhuayyds6666. 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.

Posts edited after publishing

@liuhuayyds6666 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
23 September 2026
Most recent edit
23 September 2026

Posts recorded as deleted after publishing

We recorded 5 posts on @liuhuayyds6666 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
11 August 2026
Most recent seen missing
14 October 2026
Median time before seen missing
28 hours
Seen missing in the last 30 days
1

Polls

The 6 most recent of 10 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

11 Oct 2026, 06:20 UTCAnonymous Poll1,510 voters approx.

喜欢哪一个UI版本

  1. 旧版UI24%
  2. 全新架构UI76%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

1 Oct 2026, 07:35 UTCAnonymous Poll3,590 voters approx.

想玩CFM断点追踪?

  1. 不想玩26%
  2. 非常想玩74%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

23 Sept 2026, 03:12 UTCAnonymous Poll1,440 voters approx.

要不要去除连点器

  1. 去除不好用不稳65%
  2. 保留好用又稳定35%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

21 Sept 2026, 10:17 UTCAnonymous Poll1,680 voters approx.

连点好用稳定吗?

  1. 不好用拉65%
  2. 好用,稳定35%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

20 Sept 2026, 14:40 UTCAnonymous Poll1,710 voters approx.

👿CPU渲染好不好用?

  1. 非常不好用,发烫67%
  2. 非常好用,不发烫33%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

16 Sept 2026, 03:34 UTCAnonymous Poll940 voters

CFM内核哪个版本稳又好用

  1. 87版本31%
  2. 88版本69%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 116 most recent posts we hold, published 16 July 2026 to 8 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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 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.

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.

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

“六花频道” (@liuhuayyds6666), 57,059 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/liuhuayyds6666.

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.