三角洲库洛米公益🌟🙃🌟@kuluomi886 没进的速度进👍 公益界排前五 解密市场收费界前三
👍5

Channel
@xyyds6
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
38,785subscribers
+6,574 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002515868665 |
|---|---|
| Type | Channel |
| Username | @xyyds6 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/xyyds6 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 21:23 | 38,785 | +164 |
| 1 Sept 2026, 00:16 | 38,621 | +242 |
| 30 Aug 2026, 22:27 | 38,379 | +230 |
| 30 Aug 2026, 01:07 | 38,149 | +151 |
| 29 Aug 2026, 03:02 | 37,998 | +225 |
| 28 Aug 2026, 01:05 | 37,773 | +57 |
| 27 Aug 2026, 03:56 | 37,716 | +126 |
| 26 Aug 2026, 04:13 | 37,590 | +31 |
| 25 Aug 2026, 07:02 | 37,559 | +61 |
| 24 Aug 2026, 09:33 | 37,498 | +325 |
| 22 Aug 2026, 16:16 | 37,173 | +131 |
| 21 Aug 2026, 08:28 | 37,042 | +294 |
| 20 Aug 2026, 11:13 | 36,748 | +193 |
| 19 Aug 2026, 09:45 | 36,555 | +220 |
| 18 Aug 2026, 12:04 | 36,335 | +358 |
| 17 Aug 2026, 10:48 | 35,977 | +683 |
| 15 Aug 2026, 18:04 | 35,294 | +1,091 |
| 14 Aug 2026, 06:05 | 34,203 | +1,143 |
| 13 Aug 2026, 01:07 | 33,060 | +1,077 |
| 11 Aug 2026, 23:34 | 31,983 | first reading |
191 posts held, back to 9 January 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 55 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 184 of 186 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 191 (9 January 2026 – 2 September 2026) |
| Views total | 34,050 |
| Reactions total | 1,822 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 06:51 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 2 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 22 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.
2,231 reactions across 186 posts, in 10 distinct kinds. The most used accounts for 76.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,705 | 76.4% | |
| ❤ | 398 | 17.8% | |
| 🤩 | 41 | 1.84% | |
| 🥰 | 28 | 1.26% | |
| 🔥 | 19 | 0.852% | |
| 😍 | 17 | 0.762% | |
| 👏 | 10 | 0.448% | |
| 😭 | 8 | 0.359% | |
| 🎉 | 4 | 0.179% | |
| 🤝 | 1 | 0.045% |
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 186 of the 191 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 2,231 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 191 most recent posts we hold, published 9 January 2026 to 2 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.
三角洲库洛米公益🌟🙃🌟@kuluomi886 没进的速度进👍 公益界排前五 解密市场收费界前三
👍5
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍7
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍3
😀今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 库洛米公益频道 enen内核频道 林羽内核频道 小雪内核频道 狗头公益破解频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进500+参与联系负责人 @didb431 全网收广告位出的直接私信我 ------------------------------------- 点我一键加入全部频道 点我一键加入全部频道 点我一键加入全部频道
👍5
❗️❗️❗️❗️❗️❗️❗️❗️❗️❗️ 解密版本题卡链接: https://luoye.yjsfk.cn/shop/kuluomi886 交流群反馈加时活动 客服看到会随机挑选私信赠送加时5h 工艺版本网盘下载最新版本: https://drive.uc.cn/s/a17ea05433874?public=1 库洛米工艺无解密v1.0.0版本 库洛米收费解密v15.0.0版本 库洛米三角洲本地模型sh 工艺版本卡密 @kuluomi886
👍9
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍14
库洛米公益 V1.0.0 除了没有解密,其余功能应有尽有,AI 压枪,本地模型,漏打,掩体变色 卡密:@kuluomi886
👍6❤1
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍16
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍9
库洛米 V15 更新内容如下(展开查看): 1.修复本地模型以及漏打没有效果,已适配加载全部模型 2.修复自瞄不准,优化自瞄以及压枪算法,ai 自适应所有枪械倍镜配件,无需自己调节 3.优化漏打算法、优化自瞄算法 4.优化 CPU 占用,优化模型占用,开了和没开一样,特别流畅 5.修复物资所有问题 6.修复部分用户登录不上问题 7.修复部分设备三方问题 8.修复部分安卓 17 无法打开悬浮窗 9.修复解密 3 部分人时有时无 10.修复陀螺仪存在的问题 库洛米 V15 版本是发布以来最强大的版本,是最流畅、最稳定、自瞄漏打最好用的版本 解密算法以及驱动接口全部重构,比公益稳几个版本,防止特征 🤩点我查看v15版本自瞄丝滑操作 提卡链接🔗: https://luoye.yjsfk.cn/shop/kuluomi886 🌟🙃🌟➡️ @kuluomi886 ✅卡密点我解绑 ✅代理批卡点我
👍13❤1
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍5
没有风险🎆非黑灰产💝绿色项目 合法合规,只需要一个手机!✨ 不打电话,只发短信,不封卡 无任何风险,无需本金,无需押金,合法合规 发财链接 https://t.me/u321o 赚钱联系 @paidaxingnb 无发私信就私信 @paidaxingsxbot
👍6
Showing the 12 most recent of 191 posts we hold for @xyyds6. 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.
Citation-graph rank — 1,200,402 of 1,629,403 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
@xyyds6 named 1 handle 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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“X-kerenl 主频道” (@xyyds6), 38,785 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/xyyds6.
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.