Telegram RegisterThe public register of Telegram
Telegram profile photo for 水蛇破解主频道(和平精英无畏契约三角洲王牌战争CFM王者荣耀暗区突围使命召唤辅助)

Channel

水蛇破解主频道(和平精英无畏契约三角洲王牌战争CFM王者荣耀暗区突围使命召唤辅助)

@so66666

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry

115,783subscribers

+914 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1002075647024
TypeChannel
Username@so66666
Description公益内核破解频道 投稿破解 @ssxtha 交流群组:https://t.me/LV520A6 禁止搬运,二改,倒卖,此频道破解的所有辅助 免责声明 本频道中的所有内容均来源于网络,仅供个人学习和研究使用,请在24小时之内删除,请勿用于任何商业用途或非法用途。如果您喜欢该资源,请支持正版,购买正版资源。如有任何内容侵犯了您的权益,请及时联系我们,我们将立即予以删除.
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/so66666

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 82% 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.

Growth

114,031115,896114,963.57 August 2026 — 114,869 subscribers7 August 2026 — 114,874 subscribers8 August 2026 — 114,766 subscribers9 August 2026 — 114,633 subscribers10 August 2026 — 114,557 subscribers11 August 2026 — 114,433 subscribers12 August 2026 — 114,279 subscribers13 August 2026 — 114,222 subscribers14 August 2026 — 114,031 subscribers16 August 2026 — 114,772 subscribers18 August 2026 — 114,886 subscribers19 August 2026 — 114,890 subscribers20 August 2026 — 114,942 subscribers22 August 2026 — 115,015 subscribers24 August 2026 — 114,896 subscribers25 August 2026 — 114,901 subscribers26 August 2026 — 115,043 subscribers27 August 2026 — 115,182 subscribers28 August 2026 — 115,321 subscribers29 August 2026 — 115,452 subscribers30 August 2026 — 115,537 subscribers31 August 2026 — 115,599 subscribers1 September 2026 — 115,618 subscribers2 September 2026 — 115,574 subscribers3 September 2026 — 115,665 subscribers5 September 2026 — 115,727 subscribers8 September 2026 — 115,892 subscribers11 September 2026 — 115,869 subscribers13 September 2026 — 115,896 subscribers14 September 2026 — 115,852 subscribers16 September 2026 — 115,880 subscribers18 September 2026 — 115,783 subscribers115,7837 August 202618 September 2026
32 measurements spanning 42 days, net +914. 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 113,751–116,176 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
18 Sept 2026, 20:15115,783-97
16 Sept 2026, 14:59115,880+28
14 Sept 2026, 18:59115,852-44
13 Sept 2026, 03:57115,896+27
11 Sept 2026, 07:18115,869-23
8 Sept 2026, 13:17115,892+165
5 Sept 2026, 10:38115,727+62
3 Sept 2026, 15:59115,665+91
2 Sept 2026, 09:56115,574-44
1 Sept 2026, 11:04115,618+19
31 Aug 2026, 08:05115,599+62
30 Aug 2026, 09:44115,537+85
29 Aug 2026, 06:35115,452+131
28 Aug 2026, 05:36115,321+139
27 Aug 2026, 05:32115,182+139
26 Aug 2026, 06:26115,043+142
25 Aug 2026, 04:05114,901+5
24 Aug 2026, 00:59114,896-119
22 Aug 2026, 05:56115,015+73
20 Aug 2026, 23:14114,942first reading

Engagement

725 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 108 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.588%
avg views ÷ 115,783 subscribers
Avg views / post
681
388 posts measured
Reaction rate
3.13%
reactions ÷ views · ER floor
Posts in window
392
of 725 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 21 September 2026
Posts held725 (4 August 202621 September 2026)
Views total264,324
Reactions total8,269
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Sept 2026, 02:55 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,520
Videos
109
Links
621

Lifetime counters from Telegram’s own channel header, read 22 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
7m 21s
Average length
25s

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

12,400 reactions across 708 posts, in 20 distinct kinds. The most used accounts for 95.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍11,80295.2%
2922.35%
🤓710.573%
🤔630.508%
🤣310.25%
🥰220.177%
😘210.169%
😱200.161%
❤‍🔥140.113%
😭120.097%
🥱120.097%
🤝110.089%
😇90.073%
🔥60.048%
😍40.032%
😡30.024%
🤨30.024%
🙏20.016%
👏10.008%
😁10.008%

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 715 of the 725 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 12,400 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 725 most recent posts we hold, published 4 August 2026 to 21 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.

Recent posts

21 Sept 2026, 23:42 UTC103 views7 reactionsread 22 September 2026

落叶三角洲公益频道马上更新 可以加频道蹲一下 https://t.me/luoyenb521

👍7

Signed 陪我久一点 云寄售luoye.yjsfk.cn

21 Sept 2026, 22:26 UTC154 views9 reactionsread 22 September 2026

#频道互推 #相似推荐 ------------------------------ 📢 大魔王的小窝(破解分享) 📢 小雾和平精英公益改文件分享官方频道🇨🇳 📢 小熊猫公益直装和平直装王者直装三角洲直装 📢 纯净和平改文件主频道 📢 落幕和平文件资源分享🇨🇳 📢 爱蜜莉雅官方频道🇨🇳 📢 三角洲行动/游戏辅助 📢 保护伞直装(umbrella) 📢 德州扑克外挂 德扑之星外挂 AAPoker外挂 WePo 📢 小月和平改文件美化PUBG三角洲 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励

👍9

Signed SOSO搜搜

21 Sept 2026, 22:20 UTC153 views9 reactionsread 22 September 2026
Photo

新群变化快,手动找很容易漏。 SOSO 会展示最近同步的新群入口,适合快速补充新的群组来源。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1002075647024_6825758924_newgroups_605417c5

👍9

Signed SOSO搜搜

21 Sept 2026, 18:36 UTC124 views6 reactionsread 22 September 2026

😁 章鱼哥公益解密内核 😀 主流游戏已适配:三角洲、和平、失控进化、王者、无畏契约 获取三角洲公益内核点我 获取和平公益内核点我 获取失控进化公益内核点我 获取王者公益内核点我 获取瓦手公益内核点我 获取全游戏上号器点我 想要适配什么游戏在评论区留言,你留言我适配. 争做26年的慈善家🤩 lol、暗区、codm、数据号上号器、同步开发中 ❤️ 频道 @ij666666

👍6

21 Sept 2026, 18:34 UTC165 views6 reactionsread 22 September 2026

https://t.me/luoyenb521 这个频道马上更新三角洲公益解密

👍6

Signed 陪我久一点 云寄售luoye.yjsfk.cn

21 Sept 2026, 16:18 UTC56 views23 reactionsread 22 September 2026

✅频道主推荐✅ 今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 LV公益内核频道 落叶公益内核频道 爱玩多内核公益频道 enen内核频道 林羽内核频道 小雪内核频道 吴迪公益破解频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进500+用户 参加联系 @qxnbg686 (频道主联系) 参加互推要求:频道10k+日浏览800 ❤️已加入超多百K大频道共享流量 ------------------------------------- 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️

👍211😍1

21 Sept 2026, 14:40 UTC22 views15 reactionsread 21 September 2026

❤️三角洲Relink公益最新udp解密内核 已解决udp特征问题放心使用 目前公益公益公益公益公益公益解密 频道 @Relink52 频道 @Relink52

👍15

Signed 陪我久一点 云寄售luoye.yjsfk.cn

21 Sept 2026, 14:30 UTC8 views21 reactionsread 21 September 2026

😃😀😃😀😃😀 2026最新项目零风险无门槛只要你有微信你就可以来干一个小时200 https://t.me/adggku888 https://t.me/adggku888 https://t.me/adggku888 https://t.me/adggku888 只开放两个小时两个小时后关闭

👍21

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

21 Sept 2026, 14:27 UTC393 views28 reactionsread 22 September 2026
Photo

✅和平精英ceo引擎破解 ✅绕过卡密验证 🔗点我下载🔗 #和平精英 #引擎

👍28

Signed 水蛇

21 Sept 2026, 14:23 UTC375 views29 reactionsread 22 September 2026
Photo

✅和平精英自然人脸拦截破解 ✅绕过卡密验证 🔗点我下载🔗 #和平精英 #拦截

👍29

Signed 水蛇

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

@so66666 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
31 August 2026
Most recent edit
31 August 2026

Polls

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.

16 Sept 2026, 10:32 UTCAnonymous Poll661 voters

接下来适配三角洲还是和平精英?

  1. 和平43%
  2. 三角洲64%

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

12 Sept 2026, 17:25 UTCAnonymous Poll431 voters

接下来适配三角洲还是和平精英?

  1. 和平40%
  2. 三角洲67%

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

12 Sept 2026, 12:11 UTCAnonymous Poll72 voters

接下来适配三角洲还是和平精英?

  1. 和平44%
  2. 三角洲64%

The shares total 108%, 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 725 most recent posts we hold, published 4 August 2026 to 21 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.

Forward network

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

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

“水蛇破解主频道(和平精英无畏契约三角洲王牌战争CFM王者荣耀暗区突围使命召唤辅助)” (@so66666), 115,783 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/so66666.

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.