🎁 邀请永久奖励: 该用户(💰ANT Coin收益*15%) = 888u 点击下方按钮签到免费领取 🧧 23.89 USDT 🧧 @zhipay 👇快来领取你的专属红包!
👍1
Signed 五菱 浮沉 朴实

Channel
@wo117wo
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
44,785subscribers
+11,209 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002851503872 |
|---|---|
| Type | Channel |
| Username | @wo117wo |
| Description | 公益交流群: @BB117WO 无广频道 @WW117WW 广告联系 @didb431 您好,Telegram,本频道不违反服务条款,并承诺不违反您的服务条款。请保护本频道免受破坏。 #117#三角洲公益#三角洲#公益辅助 |
| Created | Between 1 June 2025 and 30 September 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/wo117wo |
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 80% 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, 10:40 | 44,785 | +402 |
| 19 Sept 2026, 02:39 | 44,383 | +300 |
| 16 Sept 2026, 19:40 | 44,083 | +247 |
| 15 Sept 2026, 00:57 | 43,836 | +300 |
| 13 Sept 2026, 13:18 | 43,536 | +291 |
| 11 Sept 2026, 14:19 | 43,245 | +429 |
| 9 Sept 2026, 00:22 | 42,816 | +727 |
| 5 Sept 2026, 19:37 | 42,089 | +426 |
| 3 Sept 2026, 18:42 | 41,663 | +122 |
| 2 Sept 2026, 14:08 | 41,541 | +227 |
| 1 Sept 2026, 10:18 | 41,314 | +330 |
| 31 Aug 2026, 10:19 | 40,984 | +253 |
| 30 Aug 2026, 12:15 | 40,731 | +167 |
| 29 Aug 2026, 12:15 | 40,564 | +334 |
| 28 Aug 2026, 09:22 | 40,230 | +107 |
| 27 Aug 2026, 11:54 | 40,123 | +75 |
| 26 Aug 2026, 13:42 | 40,048 | +135 |
| 25 Aug 2026, 13:55 | 39,913 | +94 |
| 24 Aug 2026, 14:44 | 39,819 | +338 |
| 22 Aug 2026, 19:34 | 39,481 | first reading |
278 posts held, back to 3 February 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 105 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 29 September 2026 |
|---|---|
| Posts held | 278 (3 February 2026 – 29 September 2026) |
| Views total | 18,117 |
| Reactions total | 1,078 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 23:16 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 29 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 13 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.
3,368 reactions across 274 posts, in 12 distinct kinds. The most used accounts for 81.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,750 | 81.7% | |
| ❤ | 452 | 13.4% | |
| 🤬 | 46 | 1.37% | |
| 😱 | 33 | 0.98% | |
| 🔥 | 30 | 0.891% | |
| 😍 | 17 | 0.505% | |
| 🥰 | 10 | 0.297% | |
| 😢 | 9 | 0.267% | |
| 👏 | 7 | 0.208% | |
| 💔 | 7 | 0.208% | |
| 😭 | 4 | 0.119% | |
| ☃ | 3 | 0.089% |
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 275 of the 278 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 3,368 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 278 most recent posts we hold, published 3 February 2026 to 29 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.
🎁 邀请永久奖励: 该用户(💰ANT Coin收益*15%) = 888u 点击下方按钮签到免费领取 🧧 23.89 USDT 🧧 @zhipay 👇快来领取你的专属红包!
👍1
Signed 五菱 浮沉 朴实
✅不会小学生还没有ROOT米八吧? 今晚一共送出8️⃣台ROOT米八🌟 😒而且全是配置8+128一点都不卡 (点击下面蓝色字体进入频道) 点我进入频道获取ROOT米八 点我进入频道获取ROOT米八 点我进入频道获取ROOT米八
👍2
Signed 阿呆 (全网收管理) @adggku
117公益三角洲/暗区通知频道 pinned a file
BIGFATFISH三角洲公益算法解密 解密可能会漏人 介意勿玩 ✅方框-射线-距离-名字 ✅干员-骨骼-血量-手持 ✅适配全部干员显示 ✅护甲-物资-盒子-预警 公益解密卡密点我查看 🌟🙃🌟➡️ @BIGFATFISH6
👍17
🎮8点30锁定库洛米官方频道,发放5张天卡跟1张周卡 (福利姬) 官方频道 @kuluomi886 官方频道 @kuluomi886 官方频道 @kuluomi886 不要错过时间了!每个人都有机会白嫖卡密!
👍15
BIGFATFISH三角洲公益算法解密 解密可能会漏人 介意勿玩 ✅方框-射线-距离-名字 ✅干员-骨骼-血量-手持 ✅适配全部干员显示 ✅护甲-物资-盒子-预警 公益解密卡密点我查看 🌟🙃🌟➡️ @BIGFATFISH6
👍20
✔️绿色暴利稳赚撸口子1000~5000 项目优势:纯绿色,无风险,不用押金! ✅此项目新人都是包赚 😀最稳项目 🟢每天🉑1️⃣0️⃣0️⃣0️⃣~5️⃣0️⃣0️⃣0️⃣ 🟢不违法 不按头 不擦边❗️ 🟢最稳项目 有手就行 ✅ 🟢先赚钱后分钱👍 👍 👍😀 🔴想挣钱进群看教程⬇️⬇️ https://t.me/+S46CyXoEyF5iYWU1 不会做的联系: @saimin 双向私信不了的联系 @xxjdjqrbot 也可以看群置顶🔝详细教程
Signed 五菱 浮沉 朴实
✅不会小学生还没有ROOT米八吧? 今晚一共送出8️⃣台ROOT米八🌟 😒而且全是配置8+128一点都不卡 (点击下面蓝色字体进入频道) 点我进入频道获取ROOT米八 点我进入频道获取ROOT米八 点我进入频道获取ROOT米八
👍14
Signed 阿呆 (全网收管理) @adggku
BIGFATFISH三角洲公益独家解密 ✅方框-射线-距离-名字 ✅干员-骨骼-血量-手持 ✅适配全部干员显示 ✅护甲-物资-盒子-预警 公益解密卡密点我查看 🌟🙃🌟➡️ @BIGFATFISH6
👍11😱1
😀今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 库洛米公益频道 enen内核频道 林羽内核频道 小雪内核频道 狗头公益破解频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 ------------------------------------- 点我一键加入全部频道 点我一键加入全部频道 点我一键加入全部频道
👍15
点我助理一下频道
👍12
❤️库洛米 V32.0 更新内容: 1.尝试修复 A1 接口和谐问题 2.尝试修复 A2 接口和谐问题 3.优化 A4 接口部分人漏人闪烁问题,降低占用,修复提,部分人提示内侧关 4.修复漏人刷新按钮☑️ 5.修复乱码问题 6.修复 APP 显示问题 7.修复悬浮窗初始化等显示问题 8.修复若干问题和 bug 库洛米内置 4 种不同纯算法解密,一条和谐永远有另外一条兜底能玩,A3 接口、A4 接口,理论全部设备都有效果,不易和谐 下单地址🔗 https://luoye.yjsfk.cn/shop/kuluomi886 ❗️❗️➡️点我加入官方频道 ❗️❗️➡️点我加入官方群聊 🤘新手小白教程不懂的点我查看
👍5
Showing the 12 most recent of 278 posts we hold for @wo117wo. 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.
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 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.
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.
@wo117wo named 6 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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.
“117公益三角洲/暗区通知频道” (@wo117wo), 44,785 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/wo117wo.
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.