交流群 @kuluomi777 没进的兄弟进一下
👍52❤6😱4😭1

Channel
@kuluomi886
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Cite this entry
52,828subscribers
+43,044 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1003011374781 |
|---|---|
| Type | Channel |
| Username | @kuluomi886 |
| Description | 三角洲算法解密大王频道 库洛米交流群: https://t.me/kuluomi777 转图群 https://t.me/kuluomi9999 多种纯算法解密,已完成全部机型解密,实时同步游戏更新,多条链路兜底,多种高端功能,掩体漏打 AI 压枪,网页雷达等等 欢迎体验 #三角洲内核 |
| Created | 21 September 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/kuluomi886 |
Gaming — 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 84% 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.
@kuluomi886 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 02:19 | 52,828 | +2,084 |
| 15 Sept 2026, 18:56 | 50,744 | +2,159 |
| 14 Sept 2026, 02:19 | 48,585 | +1,193 |
| 12 Sept 2026, 05:57 | 47,392 | +2,734 |
| 10 Sept 2026, 01:58 | 44,658 | +2,054 |
| 6 Sept 2026, 19:55 | 42,604 | +2,480 |
| 4 Sept 2026, 04:40 | 40,124 | +1,026 |
| 2 Sept 2026, 19:08 | 39,098 | +697 |
| 1 Sept 2026, 19:45 | 38,401 | +680 |
| 31 Aug 2026, 19:07 | 37,721 | +671 |
| 30 Aug 2026, 19:05 | 37,050 | +780 |
| 29 Aug 2026, 18:39 | 36,270 | +689 |
| 28 Aug 2026, 21:34 | 35,581 | +907 |
| 27 Aug 2026, 23:13 | 34,674 | +1,283 |
| 26 Aug 2026, 20:02 | 33,391 | +1,471 |
| 25 Aug 2026, 18:38 | 31,920 | +1,012 |
| 24 Aug 2026, 20:37 | 30,908 | +1,223 |
| 23 Aug 2026, 07:56 | 29,685 | +1,198 |
| 21 Aug 2026, 21:26 | 28,487 | +1,432 |
| 20 Aug 2026, 16:22 | 27,055 | first reading |
327 posts held, back to 21 September 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 101 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 27 September 2026 |
|---|---|
| Posts held | 327 (21 September 2025 – 27 September 2026) |
| Views total | 1,885,613 |
| Reactions total | 13,167 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 05:46 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 10 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.
28,735 reactions across 325 posts, in 60 distinct kinds. The most used accounts for 60.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 17,400 | 60.6% | |
| ❤ | 4,068 | 14.2% | |
| 🤬 | 1,113 | 3.87% | |
| 🖕 | 959 | 3.34% | |
| 🤡 | 802 | 2.79% | |
| 👏 | 587 | 2.04% | |
| 😭 | 498 | 1.73% | |
| 🤔 | 432 | 1.50% | |
| 🥰 | 429 | 1.49% | |
| 🔥 | 405 | 1.41% | |
| 💩 | 330 | 1.15% | |
| 🤩 | 227 | 0.79% | |
| 😍 | 197 | 0.686% | |
| 👎 | 171 | 0.595% | |
| 🤣 | 158 | 0.55% | |
| 🎉 | 141 | 0.491% | |
| 😡 | 116 | 0.404% | |
| 🍌 | 114 | 0.397% | |
| 🕊 | 96 | 0.334% | |
| 😱 | 60 | 0.209% | |
| 40 further kinds | 432 | 1.50% |
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 325 of the 327 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 28,735 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 327 most recent posts we hold, published 21 September 2025 to 27 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.
交流群 @kuluomi777 没进的兄弟进一下
👍52❤6😱4😭1
很多人羡慕我会写解密,我也曾羡慕会写的人。现在我会了,却不快乐。获得神密力量的代价是对一切失去兴趣
👍83🤬20❤11🦄6🍌1
twt 驱动,目前新版本,这个驱动对接可能有问题,会导致重启或者 A4 没效果
👍42❤14🥰5
Signed 小洛姐姐💓
❤️库洛米三角洲 V30.0.0 更新内容: 以拷打三角洲千人千面加密,适配最新版本加密 1.新增算法解密 a3 接口(偶尔偏框,但一定时间校正) 2.新增算法解密 a4 接口(仅支持驱动一和 TWT 驱动) 3.新增漏人刷新按钮☑️ 4.新增天玑脱框问题修复按钮 5.修复部分物资不显示问题 6.修复部分设备不能刷驱动问题 7.所有解密接口以及无解密下适配大小地图雷达和辅助投影 8.修复若干问题和 bug 9.优化驱动和 app 可提升稳定性 A1 接口和 A2 接口在内测中,不久也会同步更新 如遇到 A3 接口、A4 接口的问题,以及发现漏物资,请点击悬浮窗上面的诊断日志,在文件管理器找到/data/local/tmp/kuromi_interface_diagnostic.txt,发给 @xiaoluo004 发文件说具体问题以及内核版本,不然不会回 公益解密卡密:@kuluomi886 (进频道才能使用)
👍49❤33🤬4
近期玩过其他科技的,要么你继续玩其他科技别玩库洛米,要么你刷机换号再玩库洛米,最近内存和断点特别多,都是隔天或一定时间追十 自己注意吧
👍39🤔7👏4❤3
交流群 @kuluomi777 没进的兄弟进一下
👍88😭8🤔6❤3👏1
📊 新算法进度: 1️⃣ 算法解密:90%(兼容性差,易受热更新影响) 2️⃣ 动态解密:100%(初始化慢,定位准,不漏人) 3️⃣ 坐标解密:100%(分批处理,速度中等,偶有偏框但定时校正,不易和谐,已内测半月) 4️⃣ 模拟解密:100%(兼容4-6系,速度快,不易和谐,部分目标可能概率闪烁) 🚀 明日新版本将上线以上功能,可根据需求自行搭配使用。
👍120❤30🕊22🤬7👏5🤔2
算了算了,先更新吧,先让你们有的玩,更新 4 个解密,前两个解密可能部分人没有效果,需要你们把日志发给我,后两个解密有点小问题,需要你们总结问题,然后给我,我今天晚上熬夜给你们全部修复好,等会发布的版本是调试版,肯定有一些问题没有修复好,集思广益,大家一起解决吧
👍37😍2❤1😭1
三角洲,你们玩其他项目又和谐了吗?😂今天都更新两次加密了
👍105❤9👏4💔1
Actor → CharacterMesh0 → Mesh + 0xE8 得到 Owner → Owner + 0x3970 得到 Capsule → Capsule + 0x330 得到 FBodyInstance → Body + 0xD8 得到 PxActor → PxActor 虚表 + 0xA8 调用 getGlobalPose → 读取 PxTransform 的旋转和位置 → 写入 ptr.Pos → WorldToScreen 后绘制 库洛米之前的解密思路,不懂的可以问问 Deepseek 和豆包,懂的人可以复活一下
👍74🤔16❤13👾3
三角洲明天可能会给你们更新一下 上 4 个解密,压箱底有 6 种解密方法,先给你们上 4 种,新上的其中两种,除非游戏更新版本,不然不会每天和谐
👍165❤44🕊31😭27🤬9🤔7👏6💅3
这评论区怎么都让更新暗区,暗区玩家这么多了?
👍164🤬21😐8❤7🤪6🥰3
Showing the 12 most recent of 327 posts we hold for @kuluomi886. 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.
@kuluomi886 edited 29 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 6 most recent of 8 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.
暗区是否适配 4 系
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.
需不需要开放无解密版本(睡醒看哪个投票多)
Shares as published. No per-option vote count is published by Telegram, so none is shown.
推荐参考价格
Shares as published. No per-option vote count is published by Telegram, so none is shown.
是否取消对四系的支持?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
解密和谐了吗
Shares as published. No per-option vote count is published by Telegram, so none is shown.
下一个更新什么游戏?
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 327 most recent posts we hold, published 21 September 2025 to 27 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 65 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.
@kuluomi886 named 2 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“库洛米官方频道” (@kuluomi886), 52,828 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/kuluomi886.
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.