Telegram RegisterThe public register of Telegram
Telegram profile photo for AGI公益

Channel

AGI公益

@AGI7891

2 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

59,518subscribers

+17,517 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002550303193
TypeChannel
Usernames@AGI7891 @iUiPD
DescriptionAGI 追求极致的动画美学与性能 细节拉满、高度用户自定化 --基于imgui的拓展窗口绘图 开发者不会主动联系你 本项目也没有任何收费及内部 本人也不会诋毁任何人及项目 网络上任何流言也要注意甄别 本项目仅供逆向UI灵感分享与学习研究 体验者的任何行为和造成的任何损失都与作者无关 若有侵权违法行为,请联系我删除内容 请在24小时内删除本应用[下载代表同意本协议]
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/AGI7891

Topic

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 the other topics.

Growth

959,87529,9427 August 2026 — 42,001 subscribers8 August 2026 — 42,269 subscribers9 August 2026 — 42,606 subscribers10 August 2026 — 42,937 subscribers11 August 2026 — 43,168 subscribers12 August 2026 — 43,460 subscribers13 August 2026 — 43,643 subscribers14 August 2026 — 43,995 subscribers15 August 2026 — 44,402 subscribers17 August 2026 — 44,911 subscribers18 August 2026 — 45,151 subscribers19 August 2026 — 45,458 subscribers20 August 2026 — 45,737 subscribers21 August 2026 — 46,068 subscribers22 August 2026 — 46,492 subscribers24 August 2026 — 47,041 subscribers25 August 2026 — 47,343 subscribers26 August 2026 — 47,603 subscribers27 August 2026 — 48,085 subscribers28 August 2026 — 48,510 subscribers29 August 2026 — 48,777 subscribers30 August 2026 — 49,048 subscribers31 August 2026 — 49,218 subscribers1 September 2026 — 49,349 subscribers2 September 2026 — 49,607 subscribers3 September 2026 — 50,020 subscribers5 September 2026 — 50,341 subscribers8 September 2026 — 50,759 subscribers11 September 2026 — 51,010 subscribers13 September 2026 — 51,446 subscribers14 September 2026 — 51,732 subscribers16 September 2026 — 51,968 subscribers18 September 2026 — 52,448 subscribers25 September 2026 — 53,723 subscribers4 October 2026 — 55,812 subscribers8 October 2026 — 56,630 subscribers12 October 2026 — 57,139 subscribers14 October 2026 — 57,293 subscribers15 October 2026 — 57,397 subscribers16 October 2026 — 57,602 subscribers17 October 2026 — 57,903 subscribers18 October 2026 — 58,204 subscribers19 October 2026 — 58,400 subscribers20 October 2026 — 58,524 subscribers21 October 2026 — 58,564 subscribers22 October 2026 — 58,677 subscribers23 October 2026 — 58,807 subscribers24 October 2026 — 59,160 subscribers25 October 2026 — 59,366 subscribers26 October 2026 — 59,533 subscribers27 October 2026 — 59,691 subscribers29 October 2026 — 59,875 subscribers30 October 2026 — 9 subscribers3 November 2026 — 59,541 subscribers4 November 2026 — 59,521 subscribers5 November 2026 — 59,518 subscribers59,5187 August 20265 November 2026
56 measurements spanning 90 days, net +17,517. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
5 Nov 2026, 06:2659,518-3
4 Nov 2026, 08:4959,521-20
3 Nov 2026, 14:2259,541+59,532
30 Oct 2026, 08:169-59,866
29 Oct 2026, 04:5059,875+184
27 Oct 2026, 23:3759,691+158
26 Oct 2026, 21:4959,533+167
25 Oct 2026, 18:4059,366+206
24 Oct 2026, 20:3159,160+353
23 Oct 2026, 18:3958,807+130
22 Oct 2026, 18:4758,677+113
21 Oct 2026, 17:1758,564+40
20 Oct 2026, 15:5658,524+124
19 Oct 2026, 15:3758,400+196
18 Oct 2026, 12:3758,204+301
17 Oct 2026, 15:0657,903+301
16 Oct 2026, 13:2657,602+205
15 Oct 2026, 13:1157,397+104
14 Oct 2026, 11:4557,293+154
12 Oct 2026, 20:3757,139first reading

Engagement

228 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 177 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
27.3%
avg views ÷ 59,518 subscribers
Avg views / post
16,200
59 posts measured
Reaction rate
0.867%
reactions ÷ views · ER floor
Posts in window
62
of 228 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 November 2026
Posts held228 (17 June 2026 – 3 November 2026)
Views total957,767
Reactions total8,300
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 14:26 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.

What this channel posts

Links
53

Lifetime counters from Telegram’s own channel header, read 5 November 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.

Video runtime
3m 48s
Average length
12s

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.

Reaction mix

36,144 reactions across 223 posts, in 58 distinct kinds. The most used accounts for 61.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍22,35361.8%
❤4,71113.0%
🤬1,3953.86%
💩1,3253.67%
👎1,1293.12%
🤔1,0192.82%
🤣5091.41%
🖕4611.28%
😡3781.05%
🤡3300.913%
🍌3180.88%
🤮2510.694%
😭2480.686%
🥰1760.487%
🤓1670.462%
🔥1590.44%
😁1520.421%
💯1110.307%
🌚1010.279%
😱770.213%
38 further kinds7742.14%

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 223 of the 228 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 36,144 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 228 most recent posts we hold, published 17 June 2026 to 3 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.

Recent posts

Telegram’s own ‘edited’ marker: 11 of 62 posts held from the last 30 days (17.7%) 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).

3 Nov 2026, 18:00 UTC≈7,680 views104 reactionsread 5 November 2026

重点讲一下跟枪力度: 他就是在你们瞄准速度慢、跟不上预判位置的时候添加的敌人移动方向附加速度,但是这个附加的速度是慢慢加上去的,数值越高加的速度越快。 1.0时附加的速度就很快,很快就瞄到预判位置,所以很准,但是这个时候就会感觉比较锁,因为附加速度的影响。 0.7时就比较适中,既要准又要软 0.5时就比较软了,跟到预判位置也比较吃力 低于0.5就会越来越软,同理 跟踪也越来越弱 瞄准速度就是你们理解的 腰射速度=瞄准速度×腰射倍数

👍84❤19🤯1

3 Nov 2026, 11:18 UTC≈9,380 views139 reactionsread 5 November 2026

然后隐藏进程建议不要开,因为好多驱动的隐藏很是鸡肋,本来游戏很难检测出来的,你一隐藏直接暴露了小心思。 比如:pidfd仍存活 但/proc/pid不存在

👍129😨8❤2

3 Nov 2026, 11:16 UTC≈9,300 views127 reactionsread 5 November 2026

我发现还有原始人用网盘内老版的“iUi启动器”,幸好服务器没变,我已经适配老版本的启动器了,最好还是下载最新版的AGI启动器

👍113❤5😨5😡4

1 Nov 2026, 18:28 UTC≈12,400 views75 reactionsread 5 November 2026

你们看一下窗口调节大小以后触控还会不会有问题,就是不好点击或者偏移的现象。 双击窗口右下角以后长按拖动就可以调节了

👍69❤6

1 Nov 2026, 18:26 UTC≈12,300 views79 reactionsread 5 November 2026

AGI[1.0.3]版本已上传至葫芦资源网盘 点我跳转网盘下载 1.解决和优化窗口的一些问题 2.优化读取和算法闪框解密之间的互补 3.新增添加人机显示标识开关 4.新增骨骼头部圆大小调节 5.一些优化

👍71❤8

1 Nov 2026, 18:23 UTC≈12,000 views81 reactionsread 5 November 2026

iUi正常更新 无广频道 @iuianb 主频道 @HLWNB

👍65🤯9❤7

31 Oct 2026, 16:58 UTC≈15,500 views167 reactionsread 5 November 2026

网盘加上了新的字体,更全面也有了之前的字体

👍165❤2

31 Oct 2026, 16:57 UTC≈15,300 views173 reactionsread 5 November 2026

AGI[1.0.2]版本已上传至葫芦资源网盘 点我跳转网盘下载 1.优化一些细节 2.修复窗口的一些问题 3.对接适配最新RT驱动 4.只支持硬件断点的驱动不默认启用,创建对应文件才可使用 防止误触

👍159❤13🔥1

30 Oct 2026, 20:34 UTC≈18,300 views114 reactionsread 5 November 2026
File

开源imgui窗口触摸穿透解决,和imgui创建窗口渲染的原理差不多

👍102❤11🔥1

30 Oct 2026, 16:10 UTC≈17,900 views209 reactionsread 5 November 2026

AGI[1.0.1]版本已上传至葫芦资源网盘 点我跳转网盘下载 1.添加自瞄跟踪强度调节(准度可调) 2.修复仅辅助拉枪无效 3.解决一些问题

👍195❤14

29 Oct 2026, 18:59 UTC≈21,100 views209 reactionsread 5 November 2026

1.自瞄又软又准天,可以随便拉开 2.自动压枪一个点,垂直水平全适配 3.淘汰王、击杀数、信号值显示 4.爆炸弓全面适配高细节 5.迫击炮雷达显示可不可以被炸到(不是单纯的爆炸距离判断) 6.手雷抛物线精准预测,且可捏瞬爆看爆炸点,爆炸点与敌人的距离显示,红色代表可炸到。 7.主题超体特殊模型骨骼适配 还有很多记不太清了,打磨了很久,刚玩AGI肯定不适应,适应了就爽了 参数可以两种来回切换。窗口大小可以双击窗口右下角调节 不要觉得自瞄锁得死,只是在特训岛感觉这样,实战基本很少有特训岛的自瞄情况。不是“锁”,是“准”。但是我是针对的是高端局写的,你容易高风险没有较高的“身法”操作的话确实不太合适,但是只要你够干净就不会有什么高风险,把把30个都不会出事,不要单纯只看环境检测软件,要考虑的方向有很多,也不要相信什么和平不吃环境,想要不频繁几天几天的封就要吃环境

👍135❤65💘7🔥2

Showing the 12 most recent of 228 posts we hold for @AGI7891. 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.

Posts edited after publishing

@AGI7891 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.

First edit seen
11 September 2026
Most recent edit
11 September 2026

Posts recorded as deleted after publishing

We recorded 10 posts on @AGI7891 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.

First seen missing
8 August 2026
Most recent seen missing
25 October 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
6

Forward network

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.

Mentions

Named by 5 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.

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.

Cite this entry

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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“AGI公益” (@AGI7891), 59,518 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/AGI7891.

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.