Telegram RegisterThe public register of Telegram

Channel

NextTrace 公告板

@nexttrace

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

883subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001767566952
TypeChannel
Username@nexttrace
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/nexttrace

Growth

882883882.57 Aug 2026, 14:39 — 882 subscribers8 Aug 2026, 01:06 — 882 subscribers8 Aug 2026, 12:02 — 883 subscribers7 Aug 2026, 14:398 Aug 2026, 12:02
3 measurements taken within a single day, net +1. 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 882–883 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:02883+1
8 Aug 2026, 01:06882no change
7 Aug 2026, 14:39882first reading

Engagement

16 posts held, back to 13 March 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
233.1%
avg views ÷ 883 subscribers
Avg views / post
2,060
4 posts measured
Reaction rate
0.572%
reactions ÷ views · ER floor
Posts in window
4
of 16 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. It is computed over the 3 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held16 (13 March 20266 August 2026)
Views total8,233
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:06 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.

Reaction mix

47 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 78.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🥰3778.7%
😁1021.3%

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

Measured over the 16 most recent posts we hold, published 13 March 2026 to 6 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

6 Aug 2026, 13:11 UTC345 views1 reactionsread 8 August 2026

【关于 NextTrace 二次开发及官方 API 使用的说明】 近期,我们注意到部分社区项目对 NextTrace 项目来源及数据来源的说明不够清晰。为减少误解,并保障官方 API 的长期稳定运行,现对相关使用边界作统一说明。 NTrace-core 采用 GPLv3 开源,社区可以依照许可证使用、修改和分发代码。但代码的开源许可与 NextTrace 官方 API 服务是两个不同的授权范围:GPLv3 授予的代码权利,并不自动包含官方服务器、接口配额及数据服务的使用权。 面向用户提供功能的网站、App、Bot、面板等第三方产品,如需直接或间接接入 NextTrace 官方 API,请提前与项目组联系并确认授权。来源标注与接口授权是两项独立要求,均需满足。 经授权使用时,请在用户能够看到的位置注明: “IP 地理位置及线路标注数据由 NextTrace 官方 API 提供” 并附上 NextTrace 官网或 NT

🥰1

26 Jul 2026, 07:28 UTC496 views2 reactionsread 8 August 2026
Photo

OpenTrace v1.5.2 已发布 https://github.com/Archeb/opentrace/releases/tag/v1.5.2

🥰2

15 Jul 2026, 08:04 UTC≈6,660 viewsread 8 August 2026

还是有很多用户不知道怎么让AI AGENT调用NextTrace。 其实很简单,安装这个SKILL就行了: https://github.com/nxtrace/NTrace-core/blob/main/skills/nexttrace/SKILL.md npx skills add https://github.com/nxtrace/NTrace-core

15 Jul 2026, 07:29 UTC732 views6 reactionsread 8 August 2026
Photo

感谢大家的支持,NextTrace 已获得 8000+ STARS 🏆

🥰6

16 Jun 2026, 12:07 UTC970 viewsread 8 August 2026
Forwarded from @nanaselogPhoto

NextTrace TraceMap 服务已完成升级改造,使用 peer.as 提供服务。 #NextTrace

29 May 2026, 14:10 UTC979 viewsread 8 August 2026

[软件更新] NextTrace v1.7.0 已正式发布 • 新增 NextTrace API v4 HTTP GeoIP provider:当数据源为 LeoMoeAPI 且配置了 NEXTTRACE_API_V4_TOKEN 时,GeoIP 查询会改用 GET https://api.nxtrace.org/v4/ipGeo?ip=<ip>,并通过 X-NextTrace-Token 请求头传 token • 新增 -x / --setup-api-v4-token:可在当前 shell 会话中粘贴并保存 NextTrace API v4 token,后续从该 shell 启动的 nexttrace 会自动加载 • nexttrace -x 使用临时 token 文件,不写 shell profile、永久环境变量或 nt_config.yaml;同时提供 parent-PID session 文件和 same-user

20 May 2026, 14:26 UTC705 views5 reactionsread 8 August 2026
Forwarded from @nanaselogVideo

[功能预告] 受到 TraceBar 的激励,NextTrace 将很高兴地带来全新的 MTR 可视化历史图表 功能。 该 feature 可以在 TUI 中展示每个 hop 的 latency history,帮助用户更直观地检查链路波动、丢包趋势和路径质量变化。 欢迎更新测试版试用,如有问题或 further improvement 建议,欢迎提交 Issue。 #NextTrace

🥰5

12 May 2026, 03:30 UTC940 viewsread 8 August 2026

[软件更新] NextTrace v1.6.5 已正式发布 • 新增 Deploy MCP 模式:nexttrace --deploy --mcp 会在 deploy 网络服务中挂载 Streamable HTTP MCP endpoint /mcp,供 Agent / MCP Client 直接调用 NextTrace 能力 • 新增 deploy token 鉴权:支持 --deploy-token 与 NEXTTRACE_DEPLOY_TOKEN;外网监听且未手动设置 token 时会自动生成 token,WebUI / REST API / WebSocket / MCP 均受保护 • 新增浏览器登录页 /auth/login:WebUI 可通过 HttpOnly Cookie 访问受保护页面;Agent / API / MCP 支持 Authorization: Bearer <token> 与 X-NextTrace

29 Apr 2026, 13:47 UTC768 views10 reactionsread 8 August 2026
Forwarded from @nanaselogPhoto

🦞OpenClaw x NextTrace 启动! NextTrace 已接入 MCP 生态,可便捷地供各类 AGENTs 调用。 > 都什么时代了,还在古法测路由? # 最新测试版下载地址 https://github.com/nxtrace/NTrace-dev/releases/tag/v1.6.5-beta.1 # MCP 部署文档 https://github.com/nxtrace/NTrace-dev/blob/main/README_zh_CN.md#deploy-webui- 与 -mcp # SKILL 安装地址 https://github.com/nxtrace/NTrace-dev/tree/main/skills 下面是测试用例,附图为其结果: 用北京联通、北京 9929、北京电信、北京移动四个 NextTrace MCP 测 w135.gubo.org,按运营商给我结论。

😁10

23 Apr 2026, 01:59 UTC838 viewsread 8 August 2026

Ubuntu/Debian 系统建议使用 apt 源安装/更新: sudo install -d -m 0755 /etc/apt/keyrings curl -fsSL -o /tmp/nexttrace-archive-keyring.gpg https://github.com/nxtrace/nexttrace-debs/releases/latest/download/nexttrace-archive-keyring.gpg sudo install -m 0644 /tmp/nexttrace-archive-keyring.gpg /etc/apt/keyrings/nexttrace.gpg rm -f /tmp/nexttrace-archive-keyring.gpg printf '%s\n' 'Types: deb' 'URIs: https://github.com/nxtrace/nexttrac

23 Apr 2026, 01:50 UTC831 viewsread 8 August 2026

[软件更新] NextTrace v1.6.4 已正式发布 • 新增独立 CDN 测速模式 --speed:支持 Apple(默认)与 Cloudflare 后端、候选节点选择、指定 --endpoint、--source / --dev、TTY 输出、非交互模式和 --json 机器可读输出 • 新增文本 IP 标注模式 --nali:可标注命令参数或管道输入中的 IPv4 / IPv6 字面量,并复用 NextTrace 现有 GeoIP provider、--data-provider、--language、--dot-server、--dn42、-4 / -6 • MTR 的 Geo / RDNS metadata 改为异步补全:先显示基础 hop,再回填 Host / Geo 信息,减少 LeoMoeAPI、RDNS 慢查询对 TUI 启动和刷新的阻塞 • 补强 LeoMoeAPI / WebSocket 链路:避免旧

10 Apr 2026, 08:47 UTC953 views2 reactionsread 8 August 2026

[软件更新] NextTrace v1.6.2 已正式发布 相比v1.6.1: • 进一步补强 --source / --dev 的跨平台行为:macOS / Linux 上会绑定到指定源网卡;Windows 上 --dev 继续只用于选择 source address,不再进入不受支持的绑定路径,相关错误提示也更明确 • 补强 Darwin 抓包兼容性:TCP / UDP 的本机定向抓包不再强制请求 promisc,修复部分 macOS 环境下 pcap open failed ... Cannot set as promisc 导致 --tcp / UDP 探测不可用的问题 • 改进 Windows 下的 WinDivert 运行时容错:缺少 runtime 时不再直接崩溃,共享打开路径增加 panic 防护,并同步调整 --init 的说明与行为 • 收紧 source-device、sniff handle 与相关运行时

🥰2

Showing the 12 most recent of 16 posts we hold for @nexttrace. 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 — 945,689 of 1,169,250entries 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.

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

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

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

“NextTrace 公告板” (@nexttrace), 883 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/nexttrace.

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.