Telegram RegisterThe public register of Telegram

Channel

AgentNEO

@AgentNEO_HQ

On this record: Growth · Engagement · Posts · Citations · Cite this entry

4,130subscribers

+8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001387585345
TypeChannel
Username@AgentNEO_HQ
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/AgentNEO_HQ

Growth

4,1214,1304,125.57 August 2026 — 4,122 subscribers7 August 2026 — 4,122 subscribers8 August 2026 — 4,121 subscribers11 August 2026 — 4,130 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net +8. 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”. The vertical axis spans 4,120–4,131 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 18:524,130+9
8 Aug 2026, 09:564,121-1
7 Aug 2026, 20:154,122no change
7 Aug 2026, 20:064,122first reading

Engagement

20 posts held, back to 6 April 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
35.6%
avg views ÷ 4,130 subscribers
Avg views / post
1,470
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 20 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 28 July 2026
Posts held20 (6 April 202528 July 2026)
Views total2,940
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12: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.

Recent posts

28 Jul 2026, 13:33 UTC≈1,500 viewsread 8 August 2026

紧急维护通知: 部分中转线路由于扩容需求临时维护,维护窗口为 7 月 28 日 晚上 10 点至 10 点半。在此期间还请使用其他不受影响的线路。

19 Mar 2026, 16:53 UTC≈5,780 viewsread 8 August 2026

部分线路断线,我们在努力回复中。请暂时切换其他可用线路使用。 另外请优先使用有更大带宽的美西直连线路以获得暂时更优的体验。无法看到直连线路的用户请升级你们的客户端,确保新客户端支持 ss2022 + ShadowTLS。

18 Nov 2025, 15:26 UTC≈8,530 viewsread 8 August 2026
Forwarded from @Cloudflare_CNPhoto

11.18 Cloudflare 全球网络故障 故障起点 北京时间11月18日19:48 受影响的服务 Access、Bot Management、CDN/Cache、Dashboard、Firewall、Network、WARP、Workers等全线服务 事件进度 23:23 持续监控中,确保服务稳定运行 22:57 部分客户仍可能遇到登录或使用Cloudflare仪表板的问题,团队正在实施修复并持续监控 22:42 修复方案已部署,事件基本解决,团队继续监控确保所有服务恢复正常 22:34 仪表板服务已恢复,应用服务影响仍在修复中 21:13 Access和WARP服务已恢复正常,错误率降至事故前水平,伦敦地区WARP访问重新启用,其他服务修复持续进行 21:09 问题根源已确定,修复方案正在实施 21:04 修复期间临时禁用伦敦地区WARP访问,该地区用户暂时无法通过WARP连接互联网 20:21

18 Nov 2025, 11:47 UTC≈4,850 viewsread 8 August 2026

目测 cloudflare 发生大面积故障,影响 AgentNEO 官网访问、订阅。节点使用不受影响 。

10 Nov 2025, 03:49 UTC≈5,270 viewsread 8 August 2026

https://fxtwitter.com/AgentNEO_ss/status/1987725954765160664?s=20

9 Oct 2025, 00:57 UTC≈5,220 viewsread 8 August 2026

https://fxtwitter.com/AgentNEO_ss/status/1976089508828545129

29 Aug 2025, 02:06 UTC≈5,870 viewsread 8 August 2026

https://fxtwitter.com/AgentNEO_ss/status/1961248896472289530

25 Jul 2025, 14:33 UTC≈5,120 viewsread 8 August 2026

部分香港需要紧急维护,预计在未来 30 分钟内断联不超过 5 分钟,更换后需要等待本地 DNS 缓存刷新即可恢复。 期间还请用户临时更换其他节点使用。

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

Forward network

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

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.

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

“AgentNEO” (@AgentNEO_HQ), 4,130 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/AgentNEO_HQ.

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.