暂时先不看私信哈 正在攻克三角洲中
👍34❤4

Channel
@EO66789
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
55,078subscribers
+19,571 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002688585044 |
|---|---|
| Type | Channel |
| Username | @EO66789 |
| Description | 交流群 @EO66669 解密没效果的联系我反馈问题 @eo667 |
| Created | Between 1 April 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/EO66789 |
Software piracy — 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 98% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 07:00 | 55,078 | +4,040 |
| 17 Sept 2026, 09:56 | 51,038 | +305 |
| 15 Sept 2026, 09:41 | 50,733 | +333 |
| 13 Sept 2026, 15:56 | 50,400 | +215 |
| 11 Sept 2026, 18:56 | 50,185 | +512 |
| 9 Sept 2026, 06:56 | 49,673 | +1,669 |
| 5 Sept 2026, 23:39 | 48,004 | +410 |
| 3 Sept 2026, 19:18 | 47,594 | +183 |
| 2 Sept 2026, 09:34 | 47,411 | +170 |
| 1 Sept 2026, 07:47 | 47,241 | +320 |
| 31 Aug 2026, 06:15 | 46,921 | +248 |
| 30 Aug 2026, 05:42 | 46,673 | +188 |
| 29 Aug 2026, 05:15 | 46,485 | +228 |
| 28 Aug 2026, 06:26 | 46,257 | +115 |
| 27 Aug 2026, 03:53 | 46,142 | +140 |
| 26 Aug 2026, 00:47 | 46,002 | +128 |
| 24 Aug 2026, 22:42 | 45,874 | +325 |
| 23 Aug 2026, 10:46 | 45,549 | +401 |
| 21 Aug 2026, 21:38 | 45,148 | +352 |
| 20 Aug 2026, 15:53 | 44,796 | first reading |
328 posts held, back to 7 August 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 112 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 26 September 2026 |
|---|---|
| Posts held | 328 (7 August 2026 – 26 September 2026) |
| Views total | 666,858 |
| Reactions total | 5,668 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 10:31 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 27 September 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 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.
10,442 reactions across 324 posts, in 15 distinct kinds. The most used accounts for 75.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 7,862 | 75.3% | |
| ❤ | 861 | 8.25% | |
| 😁 | 536 | 5.13% | |
| 🤔 | 230 | 2.20% | |
| 😭 | 228 | 2.18% | |
| 😍 | 178 | 1.70% | |
| 🤩 | 117 | 1.12% | |
| 🔥 | 95 | 0.91% | |
| 👏 | 87 | 0.833% | |
| 🥰 | 69 | 0.661% | |
| 🙈 | 56 | 0.536% | |
| 👌 | 47 | 0.45% | |
| ⚡ | 39 | 0.373% | |
| 🤝 | 21 | 0.201% | |
| 🎉 | 16 | 0.153% |
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 324 of the 328 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,442 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 328 most recent posts we hold, published 7 August 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.
暂时先不看私信哈 正在攻克三角洲中
👍34❤4
目前三角洲加密已经在发力 他的新加密导致我13版本的2000多条算法指令失效了 所以你们才会掉绘制 目前正在攻克中 不过11版本和12版本的算法还可以玩没有问题
👍52❤12😭9
大号高等级皮肤号
👍58❤5🥰3
反馈把把暴力自瞄
👍60❤8👏3
13版本又出bug了 你们先去玩12版本
👍64😍5❤3
解密局内开 进入对局内等敌人全部遁地之后再开解密 解密不要保存配置 红薯窝解密没有效果 红薯窝解密没有效果
👍62❤5😍4
驱动点我下载 使用教程点我查看 公益解密卡密: 点我查看 解密漏人等问题点我查看 自瞄配置教程点我查看
👍55😍5❤4
三角洲EO公益算法解密13.0版本 9.26最新更新 全新算法解密思路 解密已适配95%的设备 驱动对接:par驱动-时间驱动 功能:解密-绘制-模型-自喵-容器-雷达 必须先执行驱动再执行辅助 更新内容: 增加模型 增加漏打 增加掩体判断 增加小地图大地图雷法 更换自喵算法 修复锁60针 增加容器绘制 增加盒子盒子 增加物资高价值列表 修复人机盒子显示成真人盒子 更换为apk启动 使用教程点我查看 公益解密卡密: 点我查看 💯必须加入本频道才能使用此项目 💯必须加入本频道才能使用此项目 💯必须加入本频道才能使用此项目 ❗️❗️➡️ @EO66789 ❗️❗️➡️ @EO66669 💬有问题/反馈联系作者 @eo667
👍56❤9😍3🤔1🤩1🥰1
睡醒了半小时内更新13版本
👍49
先睡觉了 有事情睡醒再说吧 解密100%没有和谐 没有效果的自己看清楚使用教程先
👍21❤4🤔2
自己看app里面的使用教程 我不希望有人不看教程就使用
👍21❤4
自喵配置你们自己参考 然后游戏设置里面的陀螺仪灵敏度默认
👍15❤6
Showing the 12 most recent of 328 posts we hold for @EO66789. 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.
@EO66789 edited 8 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
eo支持公益解密吗
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 328 most recent posts we hold, published 7 August 2026 to 26 September 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.
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.
Named by 41 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“EO三角洲官方频道” (@EO66789), 55,078 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/EO66789.
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.