🎮 三角洲阿联酋用户集体下线 稍后准备推送11.19新版本安装包 .
👍2

Channel
@IOSNanu
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
35,891subscribers
+1,076 since we began measuring on 4 October 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002175417202 |
|---|---|
| Type | Channel |
| Username | @IOSNanu |
| Description | 提卡链接:https://wqfk.cn/shop/3CLACYEM 外挂交流:https://t.me/SJZQBZ 唯一客服:@MazYuaa 双向联系:@Lss26bot |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/IOSNanu |
Other / unclassifiable — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 19 October 2026 and assigned it the closest of 31 fixed categories, at 58% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @IOSNanu/14856 · this entry26 Oct 2026, 10:45 UTC | @hack886/2970326 Oct 2026, 10:46 UTC | 1.00 | under a minute |
| @IOSNanu/15195 · this entry8 Nov 2026, 09:20 UTC | @hack886/297738 Nov 2026, 09:20 UTC | 1.00 | under a minute |
| @IOSNanu/15239 · this entry9 Nov 2026, 04:50 UTC | @hack886/297899 Nov 2026, 05:06 UTC | 1.00 | 16 minutes |
| @IOSNanu/15249 · this entry9 Nov 2026, 06:17 UTC | @hack886/297999 Nov 2026, 22:43 UTC | 1.00 | 16 hours |
| @IOSNanu/15273 · this entry9 Nov 2026, 22:43 UTC | @hack886/298169 Nov 2026, 22:43 UTC | 1.00 | under a minute |
| @IOSNanu/15340 · this entry11 Nov 2026, 14:28 UTC | @hack886/2984211 Nov 2026, 17:41 UTC | 1.00 | 3.2 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @hack886 | 8 (7/8 hand-verifiable sample passed) | 1.00 | 1.8 hours | this entry (8–0) |
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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 86 comparable posts for this entry, running 4 October 2026 to 17 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.
Of the group of 3 channels, the one whose matching posts we hold earliest is @bdkxnek. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 18 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.
This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 19:39 | 35,891 | +118 |
| 14 Nov 2026, 15:59 | 35,773 | +110 |
| 11 Nov 2026, 16:01 | 35,663 | +78 |
| 9 Nov 2026, 21:48 | 35,585 | -16 |
| 8 Nov 2026, 10:08 | 35,601 | +36 |
| 7 Nov 2026, 02:58 | 35,565 | +17 |
| 6 Nov 2026, 03:25 | 35,548 | +74 |
| 5 Nov 2026, 02:29 | 35,474 | +28 |
| 3 Nov 2026, 22:45 | 35,446 | -61 |
| 1 Nov 2026, 22:36 | 35,507 | +11 |
| 31 Oct 2026, 21:56 | 35,496 | +52 |
| 30 Oct 2026, 22:20 | 35,444 | -38 |
| 29 Oct 2026, 21:28 | 35,482 | -17 |
| 28 Oct 2026, 21:01 | 35,499 | +34 |
| 27 Oct 2026, 18:09 | 35,465 | +52 |
| 26 Oct 2026, 18:11 | 35,413 | +51 |
| 25 Oct 2026, 16:00 | 35,362 | +21 |
| 24 Oct 2026, 14:14 | 35,341 | -9 |
| 23 Oct 2026, 15:59 | 35,350 | -4 |
| 22 Oct 2026, 15:19 | 35,354 | first reading |
281 posts held, back to 3 October 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 92 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. It is computed over the 182 of 188 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 November 2026 |
|---|---|
| Posts held | 281 (3 October 2026 – 18 November 2026) |
| Views total | 617,295 |
| Reactions total | 1,005 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 18:18 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 18 November 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.
Measured directly from 39 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.
1,325 reactions across 266 posts, in 14 distinct kinds. The most used accounts for 80.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,067 | 80.5% | |
| ❤ | 204 | 15.4% | |
| 🤣 | 18 | 1.36% | |
| 😍 | 8 | 0.604% | |
| 💩 | 7 | 0.528% | |
| 🖕 | 6 | 0.453% | |
| 🤡 | 3 | 0.226% | |
| 🤩 | 3 | 0.226% | |
| 🤬 | 3 | 0.226% | |
| 🔥 | 2 | 0.151% | |
| 🍌 | 1 | 0.075% | |
| 🎉 | 1 | 0.075% | |
| 😱 | 1 | 0.075% | |
| 🤯 | 1 | 0.075% |
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 268 of the 281 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 1,325 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 281 most recent posts we hold, published 3 October 2026 to 18 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: 26 of 188 posts held from the last 30 days (13.8%) 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.19新版本安装包 .
👍2
🎮 三角洲黑刃雷达更新完成 1. 关于未到期套餐的退回,截至11号出问题前所有未到期的套餐,都会按照原本的时间原样退回. 2. 关于当前可用设备,目前已全面保证 PC 端和软路由可以正常游玩. 3. 关于移动端(iOS / 安卓)限制 由于手机端 VPN 检测目前无法通过,将不再出售新卡,现阶段仅优先恢复并补偿相应时长. 4. 针对无电脑/软路由用户的处理方案如果您购买的是周卡,但目前身边没有电脑或软路由设备,可以把账号发给对应的代理,以便为您暂停计时.
👍6❤2
🎮 王者荣耀自瞄项目哪家强? TG频道南木卡网买虎牙就对了,唯一稳定天卡带自瞄的直装皇帝,无视高风险设备. ═════ 🛒 自助发卡 ═════ ❗️❗️❗️❗️❗️❗️❗️ 【购买虎牙】:点击购买 【加入群组】:点击加入 【企鹅群聊】:点击加入
👍6❤1
🎮 王者荣耀11月18日飞鼠/Momonga版本更新公告 请及时更新至最新版本!本次版本进行了多项核心功能重构与优化,具体更新内容如下: 🟢 一、ESP机制全面重构 全面重构旧版ESP机制,经过多轮严格测试与优化,彻底修复连续对局时第三局出现的ESP异常问题,进一步提升ESP运行稳定性,避免连续对局过程中出现异常. 🟢二、自瞄(Aimbot)全面升级 全面升级自瞄机制及自定义设置,现已支持自由选择任意英雄及对应技能进行自瞄,满足不同英雄、不同技能的个性化使用需求. 🟢三、新增BP阶段敌方英雄信息 新增敌方常用英雄信息显示功能,在BP禁选英雄阶段即可查看敌方最近使用的 3名英雄,方便提前了解敌方英雄选择情况. 🟢四、新增李信光信自动连招 新增李信光信形态自动连招及取消后摇功能,实现技能自动衔接与动作后摇取消,让连招操作更加流畅. ⚠️李信自动连招使用要求: · 需要开启 Aimbot 功能. ·建议搭配高冷…
❤3👍1
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5269797458
👍2
🎮 和平精英鲨鱼雷达已更新 全体加时2天,关于大厅道具和服饰消失的问题,明天会修复,对局中一切正常能看到,目前能正常使用.
👍2
File, posted without a caption
👍5
🎮 三角洲Annox最后一天出卡,今日过后退市只支持老顾客续费. 📱卡密授权:@MazYuaa
👍7❤1😍1
🎮 三角洲顶级直装GY/原JK 📱频道|📱QQ群|📱代理对接 ✅完美拿捏ACE检测,掩体变色漏打配合仿真人自瞄,效果丝滑. ✅自带直播防截图检测,单人单特征安全拉满,支持同号连打,猛踹护航必备. � 购买同款:全系统GY
👍6❤1
🎮 三角洲11.17安装包已推送 用户代理联系上级索要最新版. 新版本增加功能: 雷达显示/敌方武器子弹实时显示/敌方头甲耐久刷新/敌方胸挂显示,增强稳定性.
👍3
🎮 三角洲行动 ·【NB】专业护航 摸金撤离讲究的就是极致效率与团队配合带你体验横扫全图的爽快节奏. 顶尖意识精准预判对手动向,全图熟知高价值物资点位;搭配职业级枪法与身法细节,刚枪抢点快人一步. 全网纯手工绿色代肝,安全可靠零风险,支持通宵高效冲榜与高难任务代清,稳扎稳打,助你把把高额撤离、仓库爆满.
❤3👍2
⭐三角洲行动Zalo正版 15/16系统已修复协议7问题 等待推送.
👍2😍1
Showing the 12 most recent of 281 posts we hold for @IOSNanu. 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.
@IOSNanu 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.
We recorded 1 post on @IOSNanu 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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“南木游戏外挂/三角洲/王者荣耀/和平精英/无畏契约iOS” (@IOSNanu), 35,891 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/IOSNanu.
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.