Telegram RegisterThe public register of Telegram
Telegram profile photo for Wow俱乐部

Channel

Wow俱乐部

@ACEJF

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

1,178subscribers

+27 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003455002880
TypeChannel
Username@ACEJF
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live3 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/ACEJF

Growth

1,1511,2361,193.57 August 2026 — 1,151 subscribers7 August 2026 — 1,151 subscribers7 August 2026 — 1,161 subscribers10 August 2026 — 1,175 subscribers14 August 2026 — 1,236 subscribers17 August 2026 — 1,192 subscribers21 August 2026 — 1,183 subscribers24 August 2026 — 1,181 subscribers28 August 2026 — 1,178 subscribers30 August 2026 — 1,179 subscribers3 September 2026 — 1,178 subscribers1,1787 August 20263 September 2026
11 measurements spanning 27 days, net +27. 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 1,138–1,249 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 10:121,178-1
30 Aug 2026, 23:151,179+1
28 Aug 2026, 07:131,178-3
24 Aug 2026, 22:331,181-2
21 Aug 2026, 04:041,183-9
17 Aug 2026, 19:051,192-44
14 Aug 2026, 08:071,236+61
10 Aug 2026, 20:111,175+14
7 Aug 2026, 20:111,161+10
7 Aug 2026, 10:161,151no change
7 Aug 2026, 10:031,151first reading

Engagement

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

Reaction mix

86 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 43.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3743.0%
👍2630.2%
💩1214.0%
🤓44.65%
🤔44.65%
😱22.33%
🔥11.16%

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

Measured over the 19 most recent posts we hold, published 12 June 2026 to 7 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

7 Aug 2026, 09:25 UTC62 views4 reactionsread 7 August 2026
File

MK里面调用 SDK/Wow_无畏契约_Basic.cpp SDK/Wow_无畏契约_CoreUObject_functions.cpp SDK/Wow_无畏契约_Engine_functions.cpp SDK/Wow_无畏契约_Gameplay_functions.cpp SDK/Wow_无畏契约_SGAS_functions.cpp SDK/Wow_无畏契约_Client_functions.cpp 源码里面放 FNamePool* GetGNames() { return *(FNamePool**)(UE4 + 0xb0c1d68); } // 线程里 UObject::GUObjectArray = reinterpret_cast<FUObjectArray*>(UE4 + 0xb2534c0); while (!FName::GNames) { FName::GNames = GetGNames

2👍1🔥1

Signed 寒冰

7 Aug 2026, 06:24 UTC108 views2 reactionsread 7 August 2026

我发的那个无畏契约 Sdk还是有点问题 工具里面有个东西我忘改了 然后有些人又不会用 我写个详细的教程

👍2

Signed 寒冰

6 Aug 2026, 02:54 UTC249 views7 reactionsread 7 August 2026
File

官方原版未魔改 1.92.9b

👍4💩3

Signed 寒冰

4 Aug 2026, 06:01 UTC470 views6 reactionsread 7 August 2026
File

和平鸡精 1.37.10 来自 @AceJF

3👍3

Signed 寒冰

1 Aug 2026, 10:44 UTC552 views3 reactionsread 7 August 2026
Photo

我的用户名就只有 @Xpryn @xhbnb 这两个 别被其他的骗了 这个傻子一直在那儿冒充我 别被骗了😭

👍3

Signed 寒冰

31 Jul 2026, 13:05 UTC635 views3 reactionsread 7 August 2026
File

抓引擎数据[和平]

3

Signed 寒冰 @Xpryn

28 Jul 2026, 13:17 UTC≈1,030 views7 reactionsread 7 August 2026
File

一键配置环境 自动打包装载机 食用方法: 找到你装载机源码的路径 然后复制路径 执行脚本 然后输入装载机源码的路径 自动开始打包生成Apk 报错的话会给你提示 生成的apk在源码路径的WowBuild 需要Root 来自 @AceJF 效果图 https://t.me/AceJF/1940

5👍2

Signed 寒冰

18 Jul 2026, 13:15 UTC≈1,650 views7 reactionsread 7 August 2026
File

放在 /data/local/tmp/ 我前几个月的 现在应该没问题 还是支持每个赛季

🤓4🤔2👍1

Signed 寒冰

14 Jul 2026, 05:38 UTC≈1,600 views3 reactionsread 7 August 2026
File

AImGui-live2d开源.zip

2👍1

Signed 寒冰

8 Jul 2026, 06:42 UTC≈1,980 views8 reactionsread 7 August 2026
File

#define GNames_Offset 0xb512c4c #define GUObject_Offset 0x167EEF38 #define CanvasMap_Offset 0x16aeb360 #define UpdateVolley_Offset 0x8dd2268 #define ShootBulletInner_Offset 0x8d6fc28 #define ProcessEvent_Offset 0xb725fb8 #define GEngine_Offset 0x16b19578 //UEngine #define Postrender: 0xd57da88 #define GNativeAndroidApp 0x16024828 SDK By @AceJF 购买工具联系 @Xpryn 有问题的人用这个 没问题的人就不用换

4👍4

Signed 寒冰

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

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.

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

“Wow俱乐部” (@ACEJF), 1,178 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/ACEJF.

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.