Telegram RegisterThe public register of Telegram
Telegram profile photo for 天神公益自瞄内核

Channel

天神公益自瞄内核

@kewuaa

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

10,828subscribers

+1,120 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003064472657
TypeChannel
Username@kewuaa
Description天神客服 @sakuyatut 自愿赞助解密链接 最新卡网 (费率低) https://fklil.cn/shop/kewuaa 备用卡网 https://911.x9ynb.cn/shop/kewuaa 优惠券用备用卡网 https://t.me/kewuaachat 公益交流群 致力于成为ui最简洁实用的内核项目 接内核二创修改 定制ui添加功能对接驱动 定制局内绘图 对接验证 预算是几块钱投喂流浪汉那种就别来找骂
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live5 November 2026
Measurements held37
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/kewuaa

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

9,70710,88510,29610 August 2026 — 9,708 subscribers10 August 2026 — 9,707 subscribers13 August 2026 — 9,714 subscribers17 August 2026 — 9,745 subscribers20 August 2026 — 9,765 subscribers23 August 2026 — 9,793 subscribers27 August 2026 — 9,810 subscribers30 August 2026 — 9,806 subscribers2 September 2026 — 9,795 subscribers7 September 2026 — 9,850 subscribers12 September 2026 — 9,845 subscribers16 September 2026 — 9,884 subscribers30 September 2026 — 10,459 subscribers6 October 2026 — 10,703 subscribers10 October 2026 — 10,741 subscribers13 October 2026 — 10,779 subscribers15 October 2026 — 10,771 subscribers16 October 2026 — 10,783 subscribers17 October 2026 — 10,793 subscribers18 October 2026 — 10,804 subscribers19 October 2026 — 10,792 subscribers19 October 2026 — 10,804 subscribers21 October 2026 — 10,814 subscribers22 October 2026 — 10,805 subscribers23 October 2026 — 10,822 subscribers24 October 2026 — 10,832 subscribers25 October 2026 — 10,876 subscribers26 October 2026 — 10,867 subscribers27 October 2026 — 10,878 subscribers28 October 2026 — 10,884 subscribers29 October 2026 — 10,885 subscribers31 October 2026 — 10,878 subscribers1 November 2026 — 10,864 subscribers2 November 2026 — 10,857 subscribers3 November 2026 — 10,852 subscribers4 November 2026 — 10,843 subscribers5 November 2026 — 10,828 subscribers10,82810 August 20265 November 2026
37 measurements spanning 87 days, net +1,120. 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 9,530–11,062 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 37
Measured (UTC)SubscribersChange
5 Nov 2026, 12:1710,828-15
4 Nov 2026, 08:5510,843-9
3 Nov 2026, 07:5610,852-5
2 Nov 2026, 10:2910,857-7
1 Nov 2026, 12:1910,864-14
31 Oct 2026, 13:4810,878-7
29 Oct 2026, 08:0710,885+1
28 Oct 2026, 08:3010,884+6
27 Oct 2026, 04:5710,878+11
26 Oct 2026, 03:1510,867-9
25 Oct 2026, 06:1510,876+44
24 Oct 2026, 06:4810,832+10
23 Oct 2026, 03:4710,822+17
22 Oct 2026, 06:3610,805-9
21 Oct 2026, 01:1010,814+10
19 Oct 2026, 23:1510,804+12
19 Oct 2026, 01:0610,792-12
18 Oct 2026, 01:1010,804+11
17 Oct 2026, 03:0110,793+10
16 Oct 2026, 01:2910,783first reading

Engagement

165 posts held, back to 8 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 29 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.0%
avg views ÷ 10,828 subscribers
Avg views / post
1,200
15 posts measured
Reaction rate
1.70%
reactions ÷ views · ER floor
Posts in window
15
of 165 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 4 November 2026
Posts held165 (8 August 2026 – 4 November 2026)
Views total17,941
Reactions total305
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 20:20 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
1
Videos
3
Links
3

Lifetime counters from Telegram’s own channel header, read 5 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
56s
Average length
7s

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

928 reactions across 161 posts, in 7 distinct kinds. The most used accounts for 94.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍87794.5%
❤404.31%
🤡40.431%
👎20.216%
😭20.216%
🤩20.216%
🥰10.108%

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 161 of the 165 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 928 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 165 most recent posts we hold, published 8 August 2026 to 4 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: 6 of 15 posts held from the last 30 days (40.0%) 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).

4 Nov 2026, 02:26 UTC146 views14 reactionsread 4 November 2026
Photo

王者荣耀是不是关检测了啊 点我进频道 ✈️ 千汐内核

👍14

Signed 千汐

2 Nov 2026, 15:45 UTC690 views24 reactionsread 5 November 2026

无解密更新32.0版本 修复自瞄反向问题 更新33版本,修复了点bug 马上更新34版本。。。 这次真解决

👍23❤1

1 Nov 2026, 15:53 UTC879 views22 reactionsread 5 November 2026

新版本自瞄 打开一个自瞄开关就行 还有触摸功能 现在的触摸点自动识别 小学生改不明白有福了 里面也有后羿大招路径 还有啥功能要加评论区打出来 bp跟美化后面再说 其他实用的都可以加进去

👍22

1 Nov 2026, 15:51 UTC516 views19 reactionsread 5 November 2026
Video

🔗点我进入uc链接更新 🔗点我进入夸克链接更新 天神无解密30.0更新内容 1.优化小地图血圈显示 不漏视野为暗红色 贴近内透的效果 2.更新后羿鲁班女娲飞行物的路径显示 3.更新自动斩杀 识别名刀不斩杀 4.解决独家驱动掉帧 (部分设备可能还会) 5.减少占用 减少发烫 6. 更新王维大招灵体 7.移除linyu驱动 他不给外面对接了我没办法 8.更新人机识别功能 9.剩下其他的我忘了 v31.0 1.更新自瞄算法 更准 2.更新自动斩杀/惩戒速度 3.优化占用 减少发烫 4.优化独家驱动掉帧问题 (少部分机型可能还会有点) 5.其他的我忘记了 内核基本能加的都加了 致力成为ui最简洁实用的项目 好不好用自己去对比其他的 玩腻了其他项目的 去上面下载体验一下 一定给你不一样的感觉🌈

👍19

1 Nov 2026, 14:49 UTC775 views25 reactionsread 5 November 2026

31.0准备优化了自瞄 以及自动惩戒/斩杀速度 减少发烫

👍25

1 Nov 2026, 10:09 UTC831 views17 reactionsread 5 November 2026

无解密要更新什么东西吗 想要啥合理的都可以加上 评论区打出来

👍17

1 Nov 2026, 05:50 UTC909 views27 reactionsread 5 November 2026

内部算法快好了 非外面的泛滥模拟解密 敬请期待吧🌈🌈🌈

👍26❤1

1 Nov 2026, 04:17 UTC878 views21 reactionsread 5 November 2026

30.0有没有闪退的用户 私信我一下 @sakuyatut

👍21

30 Oct 2026, 16:59 UTC904 views24 reactionsread 5 November 2026

千汐王者美化1.5.7.zip 😀全网最强王者美化,全皮肤不掉线不僵尸,独家解锁全皮肤。无需繁杂配置英雄皮肤id。 ✅更新内容 😁适配抢先服/体验服/正式服 😁更换脚本核心驱动逻辑,解决被检测 😁添加自定义天幕特效,写入直接生效,无需自带 😁兼容性增强 😁增强脚本安全性 😁浮窗支持自定义背景/mp4,jpg等等 😁下载链接:https://wwbxi.lanzn.com/b0188jywmb 密码:3r9a 卡网:点我获取赞助链接 千汐开通TG交流群啦 点击链接加入群聊【千汐王者美化交流群】

👍24

Signed 千汐

29 Oct 2026, 09:57 UTC≈1,260 views19 reactionsread 5 November 2026
Sticker

Sticker, posted without a caption

👍19

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

@kewuaa 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
3 November 2026
Most recent edit
3 November 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“天神公益自瞄内核” (@kewuaa), 10,828 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/kewuaa.

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.