Telegram RegisterThe public register of Telegram

Channel

NEX Announcement

@NEX_Annc

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

119subscribers

+0 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002346464935
TypeChannel
Username@NEX_Annc
DescriptionNEX Network|官方公告频道 官方客户端 · 一键连接 免费 & 付费订阅支持 永久入口:nex.re 🔰(收藏防失联) 群组:t.me/NEX_GRP 频道:t.me/NEX_Annc 客服:t.me/NEX_Support_bot
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/NEX_Annc

Growth

1198 Aug 2026, 05:35 — 119 subscribers9 Aug 2026, 04:31 — 119 subscribers8 Aug 2026, 05:359 Aug 2026, 04:31
2 measurements taken within a single day. 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 118–120 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 04:31119no change
8 Aug 2026, 05:35119first reading

Engagement

12 posts held, back to 2 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
68.1%
avg views ÷ 119 subscribers
Avg views / post
81.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 12 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 1 August 2026
Posts held12 (2 February 20261 August 2026)
Views total81
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 04:31 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

Photos
4
Links
3

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

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.0%

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 1 of the 12 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 2 February 2026 to 1 August 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

1 Aug 2026, 05:18 UTC81 viewsread 9 August 2026

部分地区出现 DNS 污染,导致我们的订阅及官方客户端接口域名解析异常。 我们已完成域名切换,请前往官网获取新的订阅链接。官方客户端无需任何操作,将自动适配新的服务地址。

29 Jun 2026, 14:00 UTC159 viewsread 9 August 2026

主入口现已恢复正常,感谢大家的耐心等待。 目前主入口运行稳定,可正常连接使用。C 入口节点仍保持可用,如遇主入口偶发异常,可随时切换作为备用线路。 📱 iOS 用户使用提醒 我们注意到,部分 iOS 用户仍在使用较旧版本的 Shadowrocket,旧版本不支持我们当前使用的最新协议,可能导致节点无法连接或显示异常。请尽快将 Shadowrocket 更新至最新版本。 如果您当前没有可用的 App Store 账号来完成更新,可以联系我们付费购买 Shadowrocket 成品号。由于近期 Apple 对共享账号的管控力度明显加强,我们已无法继续向大家提供免费共享账号,还请理解。 请及时更新订阅,以确保获取最新可用节点信息。如有任何连接问题,建议优先检查客户端版本是否为最新。

29 Jun 2026, 06:33 UTC126 viewsread 9 August 2026

近期使用须知 近期主入口遭到较严重的封锁,我们正在积极寻找更稳定的解决方案。如遇主入口连接异常,可临时切换至 Relay-C 0.2x 入口节点使用,该入口稳定性较高、基本不会离线,可作为应急备用线路。 请注意:若您使用的客户端版本过低或不支持我们当前使用的最新协议,可能出现部分节点不可见,或仅能测出延迟却无法正常连接的情况。目前 Relay-C 0.2x 入口运行完全正常,如遇连接问题建议先检查客户端版本。 由于近期节点变动较为频繁,请及时更新订阅,以确保获取最新可用节点信息。

26 Jun 2026, 11:06 UTC74 viewsread 9 August 2026

各位在群内投下票,我们会根据大家的需求调整入口 https://t.me/NEX_GRP/3386

26 May 2026, 15:18 UTC229 viewsread 9 August 2026
File

📢 NEX 客户端 4.1.11 正式发布 本次更新完成了上一版公告中提到的协议适配工作,官方客户端现已支持全部节点获取。 升级后无需再借助第三方客户端,即可订阅并使用所有中继入口节点。 ⚠️ 特别说明 此版本为首个支持全协议的新版本,初期可能存在未知问题,如遇到任何 bug 请及时向我们反馈,我们会尽快跟进修复。

27 Apr 2026, 03:31 UTC301 viewsread 9 August 2026
File

📢 新增中继入口 & 客户端协议支持 为应对近期特殊网络情况,我们在原有主入口 IEPL 线路的基础上,新增了多个中继入口,以进一步提升服务的稳定性与可用性。 ⚠️ 重要提示 当前 NEX 官方客户端暂时仅支持获取 IEPL 线路节点。如需获取全部节点,请使用 Clash 等第三方客户端最新版本进行订阅。 使用第三方客户端前,请确认您的客户端支持以下协议,否则部分节点将无法正常获取: ✅ XHTTP ✅ AnyTLS 我们正在积极推进 NEX 官方客户端的适配更新,敬请期待后续版本发布。感谢您的理解与耐心等待 🙏

24 Apr 2026, 08:10 UTC253 viewsread 9 August 2026

我们将开始对所有节点进行升级维护,预计3小时内完成。在此期间,部分节点可能会出现短暂的断流现象。同时,我们也将增加更多接入点,以提升服务稳定性和覆盖范围。

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

Citation-graph rank — 1,069,823 of 1,345,403entries 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.

Mentions

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.

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

“NEX Announcement” (@NEX_Annc), 119 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/NEX_Annc.

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.