iUi[4.6.3]版本已上传至葫芦资源网盘 https://drive.uc.cn/s/7ea09a7579324?public=1 1.修复近点跳伞预警把50米高度也算上的问题 2.添加神秘小图标 3.一些改动
👍114👎14💩13🤡6❤5💘2

Channel
@iUiPD
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
53,723subscribers
+11,722 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002550303193 |
|---|---|
| Type | Channel |
| Username | @iUiPD |
| Description | i-UI 追求极致的动画美学与性能 细节拉满、高度用户自定化 --基于imgui的拓展窗口绘图 开发者不会主动联系你 本项目也没有任何收费及内部 本人也不会诋毁任何人及项目 网络上任何流言也要注意甄别 本项目仅供逆向UI灵感分享与学习研究 体验者的任何行为和造成的任何损失都与作者无关 若有侵权违法行为,请联系我删除内容 请在24小时内删除本应用[下载代表同意本协议] |
| 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 | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/iUiPD |
Other / unclassifiable — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 32% 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, 06:18 | 53,723 | +1,275 |
| 18 Sept 2026, 23:21 | 52,448 | +480 |
| 16 Sept 2026, 13:39 | 51,968 | +236 |
| 14 Sept 2026, 19:58 | 51,732 | +286 |
| 13 Sept 2026, 06:17 | 51,446 | +436 |
| 11 Sept 2026, 09:18 | 51,010 | +251 |
| 8 Sept 2026, 14:20 | 50,759 | +418 |
| 5 Sept 2026, 10:19 | 50,341 | +321 |
| 3 Sept 2026, 14:36 | 50,020 | +413 |
| 2 Sept 2026, 07:34 | 49,607 | +258 |
| 1 Sept 2026, 07:46 | 49,349 | +131 |
| 31 Aug 2026, 06:32 | 49,218 | +170 |
| 30 Aug 2026, 08:26 | 49,048 | +271 |
| 29 Aug 2026, 05:42 | 48,777 | +267 |
| 28 Aug 2026, 04:37 | 48,510 | +425 |
| 27 Aug 2026, 02:46 | 48,085 | +482 |
| 26 Aug 2026, 03:01 | 47,603 | +260 |
| 25 Aug 2026, 05:37 | 47,343 | +302 |
| 24 Aug 2026, 07:07 | 47,041 | +549 |
| 22 Aug 2026, 14:12 | 46,492 | first reading |
143 posts held, back to 17 June 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 106 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 26 September 2026 |
|---|---|
| Posts held | 143 (17 June 2026 – 26 September 2026) |
| Views total | 1,148,660 |
| Reactions total | 6,582 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 05:27 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 19 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.
25,286 reactions across 141 posts, in 55 distinct kinds. The most used accounts for 54.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 13,803 | 54.6% | |
| ❤ | 3,936 | 15.6% | |
| 🤬 | 1,182 | 4.67% | |
| 💩 | 1,085 | 4.29% | |
| 👎 | 1,017 | 4.02% | |
| 🤔 | 1,008 | 3.99% | |
| 🖕 | 430 | 1.70% | |
| 🤣 | 335 | 1.32% | |
| 🍌 | 316 | 1.25% | |
| 🤡 | 247 | 0.977% | |
| 😭 | 194 | 0.767% | |
| 🤮 | 167 | 0.66% | |
| 🤓 | 164 | 0.649% | |
| 🥰 | 163 | 0.645% | |
| 😡 | 139 | 0.55% | |
| 🔥 | 129 | 0.51% | |
| 😁 | 120 | 0.475% | |
| 💯 | 107 | 0.423% | |
| 🌚 | 101 | 0.399% | |
| 😱 | 77 | 0.305% | |
| 35 further kinds | 566 | 2.24% |
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 141 of the 143 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 25,286 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 143 most recent posts we hold, published 17 June 2026 to 26 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.
iUi[4.6.3]版本已上传至葫芦资源网盘 https://drive.uc.cn/s/7ea09a7579324?public=1 1.修复近点跳伞预警把50米高度也算上的问题 2.添加神秘小图标 3.一些改动
👍114👎14💩13🤡6❤5💘2
iUi[4.6.2]版本已上传至葫芦资源网盘 https://drive.uc.cn/s/7ea09a7579324?public=1 1.完善闪框解密 2.修复近点跳伞预警绘制位置问题 3.修复手雷读秒还是小概率重置问题 4.一些改动
👍112👎36❤10🌚9🤬6💩2
🎮三角洲落叶公益算法解密 已更新三角洲最新算法解密 不闪框 不漏人 不遁地 不协议 落叶自研队列明文MRA算法解密 动态解密算法 防止对局内二次加密 ✨点我验证落叶算法解密真实性 😀官方频道:@luoyenb521
👍41❤13🤡5👎3
iUi[4.6.1]版本已上传至葫芦资源网盘 https://drive.uc.cn/s/7ea09a7579324?public=1 1.修复手雷读瞄重置和一些问题 2.闪框解密我上了一千个方案,我没闪框号筛选不了,你们闪框的帮我筛选吧,没问题或者问题不大的说出来我收录一下,问题不大的说一下具体什么情况
👍121🤬61❤18😡14
推荐一款朋友的和平落叶🎮三角洲🎮公益项目 三角洲拥有最先进的解密 大家可以去支持一下 https://t.me/luoyenb521
👍22❤2🔥1
iUi[4.6.0]版本已上传至葫芦资源网盘 https://drive.uc.cn/s/7ea09a7579324?public=1 1.指哪打哪 2.狙击默认瞄头 3.狙击瞄准生效方式添加开镜生效和混合生效选择
👍69❤21💩11👎9🍌2
iUi[4.5.2]版本已上传至葫芦资源网盘 https://drive.uc.cn/s/7ea09a7579324?public=1 修复部分驱动读取失败导致的没效果
👍51👎22❤9🤬8💯7🔥2
推荐一款朋友的和平落叶🎮三角洲🎮公益项目 三角洲拥有最先进的解密 大家可以去支持一下 https://t.me/luoyenb521
👍32❤5👎1
iUi[4.5.1]版本已上传至葫芦资源网盘 https://drive.uc.cn/s/7ea09a7579324?public=1 1.修复喷子准星对准人才连点有时失效的问题 2.修复预判问题 准度更上一层楼 3.修复绘制漏人问题 4.喷子添加取消闪镜开关 5.喷子闪镜机制改成只有站着移动时才生效 6.修复Kairos驱动横屏启动时触摸位置有bug的问题 7.对接最新TWT驱动 8.一些改动和优化
👍52💩11❤10🤬5
iUi[4.5.0]版本已上传至葫芦资源网盘 https://drive.uc.cn/s/7ea09a7579324?public=1 1.整体优化UI 2.将掉后台的可能扼杀在摇篮中 3.添加被轰炸预警 优化轰炸预警绘制 4.添加近点50米内有人落伞的预警 5.一些优化和修复
👍84🤮53👎23❤11🖕5
推荐一款朋友的和平落叶🎮三角洲🎮公益项目 三角洲拥有最先进的解密 大家可以去支持一下 https://t.me/luoyenb521
👍25❤7
iUi[4.4.7]版本已上传至葫芦资源网盘 https://drive.uc.cn/s/7ea09a7579324?public=1 整体对一些地方进行了优化和一些问题的修复和改动。有点对忘记有哪些了,有些功能参数可能要重新调,记得看一下
👍46👎22❤6🤡2😁1
Showing the 12 most recent of 143 posts we hold for @iUiPD. 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.
@iUiPD 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
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.
“iUi公益” (@iUiPD), 53,723 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/iUiPD.
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.