Telegram RegisterThe public register of Telegram
Telegram profile photo for EO三角洲官方频道

Channel

EO三角洲官方频道

@EO66789

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

63,721subscribers

+28,214 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-1002688585044
TypeChannel
Username@EO66789
Description驱动频道 @eo666999 交流群 @EO66669 解密没效果的联系我反馈问题 @eo667
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/EO66789

Topic

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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 3 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@EO66789/11202 · this entry21 Oct 2026, 19:28 UTC@time_pd/1699521 Oct 2026, 19:28 UTC1.00under a minute
@EO66789/11192 · this entry21 Oct 2026, 04:09 UTC@Sakurayyda/3431821 Oct 2026, 04:09 UTC1.00under a minute
@EO66789/11243 · this entry24 Oct 2026, 10:02 UTC@Sakurayyda/3437124 Oct 2026, 10:02 UTC1.00under a minute
@EO66789/11455 · this entry9 Nov 2026, 13:56 UTC@Sakurayyda/344539 Nov 2026, 13:56 UTC1.00under a minute
@EO66789/11192 · this entry21 Oct 2026, 04:09 UTC@HeiXuePD/3303421 Oct 2026, 04:09 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@time_pd10 (8/8 hand-verifiable sample passed)1.008.7 hoursthis entry (8–2)
@Sakurayyda6 (6/6 hand-verifiable sample passed)1.00under a minuteeven
@HeiXuePD11 (8/8 hand-verifiable sample passed)1.004.4 hoursthis entry (7–4)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 133 comparable posts for this entry, running 9 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

35,50763,72149,6147 August 202611 November 2026
65 measurements spanning 96 days, net +28,214. 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 31,275–67,953 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
11 Nov 2026, 13:5763,721+88
9 Nov 2026, 19:0163,633-45
8 Nov 2026, 10:5963,678+24
7 Nov 2026, 08:1763,654+74
6 Nov 2026, 10:5063,580+1,022
5 Nov 2026, 13:5962,558+1,807
4 Nov 2026, 17:2760,751+144
3 Nov 2026, 17:1660,607+115
2 Nov 2026, 19:4660,492+168
1 Nov 2026, 21:0660,324+413
31 Oct 2026, 23:4559,911+536
30 Oct 2026, 22:2959,375+187
29 Oct 2026, 23:0159,188+141
28 Oct 2026, 21:0659,047+80
27 Oct 2026, 20:3758,967+167
26 Oct 2026, 21:4658,800+306
25 Oct 2026, 20:0558,494+228
24 Oct 2026, 18:4858,266-17
23 Oct 2026, 16:0858,283-7
22 Oct 2026, 17:4458,290first reading

Engagement

684 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 220 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.52%
avg views ÷ 63,721 subscribers
Avg views / post
2,240
243 posts measured
Reaction rate
3.16%
reactions ÷ views · ER floor
Posts in window
243
of 684 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 11 November 2026
Posts held684 (7 August 2026 – 11 November 2026)
Views total544,886
Reactions total17,225
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 16:47 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
856
Videos
18
Links
84

Lifetime counters from Telegram’s own channel header, read 11 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
8m 49s
Average length
26s

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

35,598 reactions across 679 posts, in 30 distinct kinds. The most used accounts for 88.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍31,43388.3%
❤1,7384.88%
😁5461.53%
🤔2800.787%
😍2780.781%
😭2740.77%
👏1820.511%
🥰1760.494%
🔥1610.452%
🤩1490.419%
🤬810.228%
🙈590.166%
👌490.138%
⚡400.112%
🤝310.087%
🎉160.045%
😡150.042%
🤓150.042%
❤‍🔥140.039%
👎120.034%
10 further kinds490.138%

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 679 of the 684 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 35,598 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 684 most recent posts we hold, published 7 August 2026 to 11 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: 40 of 243 posts held from the last 30 days (16.5%) 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).

11 Nov 2026, 16:18 UTC14 views99 reactionsread 11 November 2026
Photo

开挂没号玩? 不敢用自己大号开挂? 害怕😨被封? 想体验皮肤? 想要游戏资产多的号? 想免费玩号? ❤️老八高质量三角洲数据号源头自营✔️ ➡️😃😃退游号😃😃高质量号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 ➡️全网最质量最低价格 最强售后😒 🥇一年诚信经营,三年售后兜底 😙😍😗😋😝🙃😜🤨😜 👍👍 ❤️主推-购买地址: https://buy.heevcmlz.cn/ ❤️备用2-购买地址 https://buy.sjhnb.com/ 上面两个卡网都可以用,哪个能打开用哪个 ❤️老八数据号官方频道:https://t.me/xcnb666 ✅客服:@djsjhnb6

👍97❤2

11 Nov 2026, 15:58 UTC37 views110 reactionsread 11 November 2026
Photo

三角洲大肥鱼国服永久公益解密内核 认准:BIG FAT FISH(大肥鱼) 已适配三角洲最新S12赛季 采用算法/udp双解密方案 正在永久公益中!正在永久公益中! ❤️ 支持设备:安卓 ROOT ❤️ 支持内核:4.x - 6.x 全系 ❤️支持天机/骁龙 处理器 ❤️支持区服:C国服 ❤️支持模式:内核/纯c 功能说明🎚 ✅方框 ✅骨骼 ✅干员 ✅血量 ✅距离 ✅手持 ✅头甲 ✅物资 🟢全图模型漏打 🟢战斗模式 🟢添加独立大小雷达 ✅自瞄配置:陀螺仪自瞄+触摸自瞄 🔗下载安装包🔗 ✅时间驱动 ✅par驱动 ✔️大肥鱼点我公益解密卡密 ✈️大肥鱼新手/老手不会使用的点我查看视频和文字教程 🌟🙃🌟➡️ @BIGFATFISH6 🎉肥鱼我呀会坚持一直一直一直工艺下去哒! 频道接广告点我查看

👍108❤2

11 Nov 2026, 15:52 UTC66 views105 reactionsread 11 November 2026
File

花海三角洲1.9版本(公益中) 😀😀😀😀😀😀😀😀😀 📣公告: 解决绘制掉帧,修复部分问题。 接入林羽➕TWT驱动。 🔹🔹🔹🔹🔹🔹🔹🔹🔹🔹 ✅纯算法解密 不动任何内存 ✅无视相机/迷雾/聚框加密 ✅解决千人千面加密的问题 ✅绘制解密已优化满帧运行 🔹🔹🔹🔹🔹🔹🔹🔹🔹🔹 驱动支持: 时间/PD/林羽/TWT 公益卡密:huahainb 掩体判断模型安装: https://t.me/huahainb/9595 🥰客服 @huahaikf 😀官方TG: https://t.me/huahainb https://t.me/huahainb https://t.me/huahainb

👍104❤1

Signed 有事直说!

11 Nov 2026, 14:59 UTC111 views113 reactionsread 11 November 2026

我操他妈的电报上骗子怎么这么多啊!!直到我遇到他 @adggnbkefu 我才知道一小时可以挣1988元 目前已经拿下苹果18了😁

👍111❤1🤬1

Signed 阿呆 (全网收管理) @adggku

11 Nov 2026, 14:34 UTC348 views102 reactionsread 11 November 2026
File

花海三角洲1.9版本(公益中) 😀😀😀😀😀😀😀😀😀 📣公告: 解决绘制掉帧,修复部分问题。 接入林羽➕TWT驱动。 🔹🔹🔹🔹🔹🔹🔹🔹🔹🔹 ✅纯算法解密 不动任何内存 ✅无视相机/迷雾/聚框加密 ✅解决千人千面加密的问题 ✅绘制解密已优化满帧运行 🔹🔹🔹🔹🔹🔹🔹🔹🔹🔹 驱动支持: 时间/PD/林羽/TWT 公益卡密:huahainb 掩体判断模型安装: https://t.me/huahainb/9595 🥰客服 @huahaikf 😀官方TG: https://t.me/huahainb https://t.me/huahainb https://t.me/huahainb

👍101❤1

Signed 有事直说!

11 Nov 2026, 12:46 UTC88 views111 reactionsread 11 November 2026
Photo

开挂没号玩? 不敢用自己大号开挂? 害怕😨被封? 想体验皮肤? 想要游戏资产多的号? 想免费玩号? ❤️老八高质量三角洲数据号源头自营✔️ ➡️😃😃退游号😃😃高质量号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 ➡️全网最质量最低价格 最强售后😒 🥇一年诚信经营,三年售后兜底 😙😍😗😋😝🙃😜🤨😜 👍👍 ❤️主推-购买地址: https://buy.heevcmlz.cn/ ❤️备用2-购买地址 https://buy.sjhnb.com/ 上面两个卡网都可以用,哪个能打开用哪个 ❤️老八数据号官方频道:https://t.me/xcnb666 ✅客服:@djsjhnb6

👍109❤2

11 Nov 2026, 12:07 UTC362 views102 reactionsread 11 November 2026
Photo

三角洲大肥鱼国服永久公益解密内核 认准:BIG FAT FISH(大肥鱼) 已适配三角洲最新S12赛季 采用算法/udp双解密方案 正在永久公益中!正在永久公益中! ❤️ 支持设备:安卓 ROOT ❤️ 支持内核:4.x - 6.x 全系 ❤️支持天机/骁龙 处理器 ❤️支持区服:C国服 ❤️支持模式:内核/纯c 功能说明🎚 ✅方框 ✅骨骼 ✅干员 ✅血量 ✅距离 ✅手持 ✅头甲 ✅物资 🟢全图模型漏打 🟢战斗模式 🟢添加独立大小雷达 ✅自瞄配置:陀螺仪自瞄+触摸自瞄 🔗下载安装包🔗 ✅时间驱动 ✅par驱动 ✔️大肥鱼点我公益解密卡密 ✈️大肥鱼新手/老手不会使用的点我查看视频和文字教程 🌟🙃🌟➡️ @BIGFATFISH6 🎉肥鱼我呀会坚持一直一直一直工艺下去哒! 频道接广告点我查看

👍100❤1🤬1

11 Nov 2026, 11:44 UTC989 views113 reactionsread 11 November 2026

1

👍113

Signed 阿呆 (全网收管理) @adggku

11 Nov 2026, 11:08 UTC115 views109 reactionsread 11 November 2026

半夜想要看片👀找不到的各种资源群里都可以搜索的到 🔍 相关游戏外挂安装包也可以搜的到 关键词:萝莉 黑丝 御姐 少萝 白丝 老师 洛丽塔 JK 等等 ⬇️⬇️⬇️⬇️⬇️⬇️⬇️ https://t.me/sos73781 https://t.me/sos73781 https://t.me/sos73781

👍103❤3🤬3

11 Nov 2026, 06:04 UTC≈1,960 views90 reactionsread 11 November 2026
Video

旋转小陀螺+第三人称+飞天🎉🎉 都可以裸奔哦 安装包频道内获取 公益卡密联系机器人 @bbblajibot https://t.me/BIGFATFISH6 https://t.me/BIGFATFISH6

👍85❤3💩1🥰1

Signed 大肥鱼

11 Nov 2026, 03:05 UTC217 views71 reactionsread 11 November 2026
File

大肥鱼飞天更新1.2版本 飞天如果只上下爬梯那就加大一下爬梯速度就行了 使用方法直接执行即可无需驱动 下个版本更新增加第三人称 可以搭配其他辅助使用 不吃举报即可 更新:注入裸奔(切勿吃举报) 如若和谐后请不要再使用 公益卡密: 联系机器人获取大肥鱼卡密 @bbblajibot 官方频道 @BIGFATFISH6 官方频道 @BIGFATFISH6 频道记得关注一下😡 😙温馨提示小号娱乐即可可搭配别的辅助一起使用

👍71

11 Nov 2026, 02:25 UTC35 views74 reactionsread 11 November 2026
Photo

开挂没号玩? 不敢用自己大号开挂? 害怕😨被封? 想体验皮肤? 想要游戏资产多的号? 想免费玩号? ❤️老八高质量三角洲数据号源头自营✔️ ➡️😃😃退游号😃😃高质量号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 ➡️全网最质量最低价格 最强售后😒 🥇一年诚信经营,三年售后兜底 😙😍😗😋😝🙃😜🤨😜 👍👍 ❤️主推-购买地址: https://buy.heevcmlz.cn/ ❤️备用2-购买地址 https://buy.sjhnb.com/ 上面两个卡网都可以用,哪个能打开用哪个 ❤️老八数据号官方频道:https://t.me/xcnb666 ✅客服:@djsjhnb6

👍74

Showing the 12 most recent of 684 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.

Posts edited after publishing

@EO66789 edited 13 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.

First edit seen
10 August 2026
Most recent edit
5 November 2026

Posts recorded as deleted after publishing

We recorded 38 posts on @EO66789 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
9 August 2026
Most recent seen missing
9 November 2026
Median time before seen missing
16 hours
Seen missing in the last 30 days
7

Polls

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

17 Oct 2026, 15:14 UTCAnonymous Poll528 voters

支持更新VM算法解密吗

  1. 快更新吧88%
  2. 不想玩三角洲12%

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

5 Oct 2026, 14:25 UTCAnonymous Poll505 voters

要不要更新15版本

  1. 要92%
  2. 不要11%

The shares total 103%, 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.

4 Oct 2026, 03:52 UTCAnonymous Poll787 voters

要不要上VM解密

  1. 要92%
  2. 不要12%

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.

7 Sept 2026, 08:37 UTCAnonymous Poll171 voters

eo支持公益解密吗

  1. 支持公益83%
  2. 不支持17%

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 684 most recent posts we hold, published 7 August 2026 to 11 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.

派大黑腾讯*网易免费加速器(2026持续更新中)
@yhtjdk · 39,452
58 posts
黑雪主频道
@HeiXuePD · 63,771
41 posts
时间辅助频道
@time_pd · 107,260
38 posts
TwT驱动更新频道(新人看置顶)
@TwT_driver · 86,632
33 posts
🌹林羽の小窝🌸
@LinYuKernel · 117,657
28 posts
X-kerenl 主频道
@xyyds6 · 41,487
25 posts
117公益三角洲/暗区通知频道
@wo117wo · 45,417
21 posts
Fireworks主频道
@fire88666 · 28,757
19 posts
晴天主频道
@qingtPD · 22,628
19 posts
Super三角洲内核频道
@SH_ESP · 47,506
18 posts
Cycle1337's Cheats (新人看置顶)
@Cycle1337 · 41,173
16 posts
山海经内核频道
@My_Name_Sheep · 44,523
16 posts
蛋蛋公益端(强势回归)
@Nbomb914 · 30,432
16 posts
啊米诺思(KX追踪)
@Sakurayyda · 56,416
15 posts
美国漏打
@USA_Sep · 44,972
14 posts
追猎杯通知频道🥤
@ZLBNB666 · 55,183
14 posts
King三角洲内核频道
@King_ESP · 45,968
10 posts
吴迪内核公益破解(和平精英无畏契约王者荣耀萤火突击CFM三角洲PUBG失控进化辅助直装内核)
@zwaaa3 · 116,163
10 posts
小夜破解内核分享(无畏契约三角洲和平精英王者cfm使命暗区突围PUBG)
@zwaaa333 · 77,319
10 posts
乐鱼体育|ATM娱乐城|众星娱乐
@WWE386 · 8
9 posts
三角洲摸金校尉
@mjxw668 · 25,090
9 posts
玄冥主频道
@JSAI866 · 28,171
6 posts
ZERO公益频道
@ZEROPD · 87,021
6 posts
Dra™
@Drabanb · 39,551
5 posts
浪漫内核分享频道[公益破解][软件分享][免费代理]
@LMGWJWD6 · 44,343
5 posts
小露分享主频道🇨🇳
@LMY1015 · 15,811
4 posts
DemonLord三角洲(DL)
@DLerend · 24,609
3 posts
狗头工艺破解频道(王者荣耀和平精英暗区突围pubg三角洲行动萤火突击CFM无畏契约)
@pj7645 · 72,955
3 posts
小呆呆范围/单解密/内透频道
@XDDNB68 · 17,148
2 posts
库洛米官方公益频道
@kuluomi886 · 78,712
2 posts
玖玖破解(全游戏PC端游无畏契约和平精英三角洲直装)
@pp8661 · 22,571
2 posts
BIG FAT FISH 公益频道(大肥鱼)
@BIGFATFISH6 · 34,411
1 post
快斗通知频道
@KDMHPD · 39,661
1 post
Like公益内核/暗区-三角洲-瓦
@Likenb667 · 41,609
1 post
芊羽の小窝
@QianYuHome · 11,798
1 post
Sakura主频道(注意置顶)
@V521a · 56,982
1 post
瓦瓦长期公益主频道
@wawanb8 · 36,041
1 post

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

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

“EO三角洲官方频道” (@EO66789), 63,721 subscribers as measured 11 November 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.