这个问题服务器厂商那边已经正在维修了,耐心等待一下,现在已经到家了,正在研究迷雾和解密,因为咱们的解密有五种,我要把每一个解密都更新了,工作量是别人的五倍,所以说需要的时间有一一点久,应该是今天半夜完成更新,耐心等待即可
👍167❤9🕊6🍌3💯2😈2😘2

Channel
@ApexZPD
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
29,840subscribers
+29,002 since we began measuring on 11 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003856557615 |
|---|---|
| Type | Channel |
| Username | @ApexZPD |
| Description | Apex三角洲公益算法解密 不禁言交流群: https://t.me/Apex3a 如误封私信机器人解封 @yx_codexbot 频道所有者 @ApexFZR |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/ApexZPD |
Gaming — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 12:01 | 29,840 | +1,635 |
| 4 Nov 2026, 14:39 | 28,205 | -7 |
| 3 Nov 2026, 14:56 | 28,212 | +20 |
| 2 Nov 2026, 15:49 | 28,192 | +13 |
| 1 Nov 2026, 12:15 | 28,179 | +23 |
| 31 Oct 2026, 13:17 | 28,156 | +6 |
| 30 Oct 2026, 12:31 | 28,150 | -54 |
| 29 Oct 2026, 11:31 | 28,204 | +6 |
| 28 Oct 2026, 09:31 | 28,198 | +43 |
| 27 Oct 2026, 06:09 | 28,155 | -1 |
| 26 Oct 2026, 05:48 | 28,156 | -101 |
| 25 Oct 2026, 06:47 | 28,257 | +72 |
| 24 Oct 2026, 04:11 | 28,185 | +3 |
| 23 Oct 2026, 01:41 | 28,182 | +353 |
| 22 Oct 2026, 02:26 | 27,829 | +140 |
| 20 Oct 2026, 18:01 | 27,689 | +281 |
| 19 Oct 2026, 14:56 | 27,408 | +365 |
| 18 Oct 2026, 12:57 | 27,043 | +528 |
| 17 Oct 2026, 14:49 | 26,515 | +785 |
| 16 Oct 2026, 13:54 | 25,730 | first reading |
195 posts held, back to 6 September 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 74 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 195 (6 September 2026 – 5 November 2026) |
| Views total | 526,866 |
| Reactions total | 8,876 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 16:21 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.
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.
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.
24,474 reactions across 193 posts, in 49 distinct kinds. The most used accounts for 72.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 17,779 | 72.6% | |
| 🖕 | 2,415 | 9.87% | |
| ❤ | 1,412 | 5.77% | |
| 🤬 | 583 | 2.38% | |
| 🤓 | 410 | 1.68% | |
| 🍌 | 369 | 1.51% | |
| 😭 | 346 | 1.41% | |
| 🕊 | 211 | 0.862% | |
| 🥰 | 126 | 0.515% | |
| 🤔 | 82 | 0.335% | |
| 🫡 | 76 | 0.311% | |
| 💩 | 65 | 0.266% | |
| 💔 | 64 | 0.262% | |
| 🤣 | 45 | 0.184% | |
| 😡 | 39 | 0.159% | |
| 😍 | 38 | 0.155% | |
| 👌 | 29 | 0.118% | |
| 👏 | 26 | 0.106% | |
| 🌭 | 24 | 0.098% | |
| 🤪 | 22 | 0.09% | |
| 29 further kinds | 313 | 1.28% |
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 194 of the 195 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 24,474 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 195 most recent posts we hold, published 6 September 2026 to 5 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.
Telegram’s own ‘edited’ marker: 65 of 130 posts held from the last 30 days (50.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).
这个问题服务器厂商那边已经正在维修了,耐心等待一下,现在已经到家了,正在研究迷雾和解密,因为咱们的解密有五种,我要把每一个解密都更新了,工作量是别人的五倍,所以说需要的时间有一一点久,应该是今天半夜完成更新,耐心等待即可
👍167❤9🕊6🍌3💯2😈2😘2
出现这种情况的别急,等我回家解决
👍116❤13🤬7
等我回家给你们更新迷雾和解密,这些都是小问题,不要制造恐慌,几行代码的事。现在没有电脑没法看,不过根据我猜测这个应该和和暗区的那个一样,远端敌人有新的绑定,还是挺好解决的,等我下午/晚上到家吧😁
👍112❤14😡12🤬6🤔2
udp解密的key终于改了,这赛季市场上会少很多垃圾udp解密,这是件好事,因为对我没影响,哈哈哈🤣
👍105❤6🤓4
赛季初还没上检测,辅助里面的追踪功能我已经更新了,想要爽的赶紧上号爽一爽,一个赛季就这一回😀
👍65❤10
Apex_11.05[三角洲]更新通知 更新模式:自动云下发更新 更新内容: - 适配最新赛季 公益卡密 @ApexZPD 网页雷达官网 http://140.210.8.34 Apex智能AI助手:@ApexZPDBot [点我查看智能AI助手相关功能] 官方频道:@ApexZPD 交流群组: @Apex3A 频道所有者 @ApexFZR
👍37❤31😢1
所有已激活用户,已集体加时8天,作为此次公益七天的补偿
👍28❤7🤓1
【🎮Apex|限时公益 7 天】 😭原价:15/天|60/周|180/月 ✅现开启限时免费体验,收费版本全功能开放使用,仅此一次!!! 为了让更多用户体验新赛季以来的更新内容,也为了感谢一直以来支持Apex的用户,我们决定开启一次为期 7 天的限时公益活动! 过去一段时间,项目经历了从公益开放到正式运营的转变。进入新赛季后,我们也持续投入了大量时间与精力,对项目进行了多轮更新与优化,新增了不少功能与体验内容。 但我们也知道,仍有一部分用户在此前公益期间没能体验到这些更新。 因此,我们决定: 即日起,Apex限时开放公益体验 7 天! 活动说明 • 活动时间:连续 7 天 • 活动期间:11月5日-11月12日 • 活动内容:免费开放当前版本所有功能 • 活动结束:恢复正常运营模式 最后想说 这次公益并不是项目停止运营,也不是一次简单的宣传活动。 我们希望通过这 7 天,让更多人了解Apex在新赛季所做出的改…
👍30❤10🔥1
明天凌晨3:00新赛季,Apex会以最快的速度更新,并且第一周会有很多福利。😘
👍75❤8
🎮『Apex_Kernel_11.4』 启动器已内置云更新,无需重复下载 ❗ 云更新内容: - 更新a1解密 - 更新无视加密解密 🏪购买链接: https://luoye.oopb.cn/shop/110 ✨网页雷达官网 http://140.210.8.34/ 不禁言交流群: https://t.me/Apex3a 作者/频道所有者 @ApexFZR 😂日期:2026年11月4日 🌐 Apex Kernel运营团队
👍13❤12
Apex的6款解密均已云更新,全部适配最新解密😘
👍50❤4
🎮『Apex_Kernel_11.3』 启动器已内置云更新,无需重复下载 ❗ 云更新内容: - 更新a1和a4解密 - 更新无视加密解密 🏪购买链接: https://luoye.oopb.cn/shop/110 ✨网页雷达官网 http://140.210.8.34/ 不禁言交流群: https://t.me/Apex3a 作者/频道所有者 @ApexFZR 😂日期:2026年11月3日 🌐 Apex Kernel运营团队
👍33❤11
Showing the 12 most recent of 195 posts we hold for @ApexZPD. 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.
@ApexZPD edited 9 posts 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.
We recorded 7 posts on @ApexZPD 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.
The 3 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.
对此次运营调整是否满意?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
你们都是开单透还是自瞄?
The shares total 106%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
✨内核版本统计
The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 195 most recent posts we hold, published 6 September 2026 to 5 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.
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 26 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
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.
“Apex(限时公益7天)” (@ApexZPD), 29,840 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ApexZPD.
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.