Channel
@nexttrace
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
903subscribers
+21 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001767566952 |
|---|---|
| Type | Channel |
| Username | @nexttrace |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 10 September 2026 |
| On Telegram | t.me/nexttrace |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 11:38 | 903 | +3 |
| 24 Aug 2026, 13:27 | 900 | +6 |
| 16 Aug 2026, 08:18 | 894 | +11 |
| 8 Aug 2026, 12:02 | 883 | +1 |
| 8 Aug 2026, 01:06 | 882 | no change |
| 7 Aug 2026, 14:39 | 882 | first reading |
16 posts held, back to 13 March 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
47 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 78.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 37 | 78.7% | |
| 😁 | 10 | 21.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 47 reactions 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.
【关于 NextTrace 二次开发及官方 API 使用的说明】 近期，我们注意到部分社区项目对 NextTrace 项目来源及数据来源的说明不够清晰。为减少误解，并保障官方 API 的长期稳定运行，现对相关使用边界作统一说明。 NTrace-core 采用 GPLv3 开源，社区可以依照许可证使用、修改和分发代码。但代码的开源许可与 NextTrace 官方 API 服务是两个不同的授权范围：GPLv3 授予的代码权利，并不自动包含官方服务器、接口配额及数据服务的使用权。 面向用户提供功能的网站、App、Bot、面板等第三方产品，如需直接或间接接入 NextTrace 官方 API，请提前与项目组联系并确认授权。来源标注与接口授权是两项独立要求，均需满足。 经授权使用时，请在用户能够看到的位置注明： “IP 地理位置及线路标注数据由 NextTrace 官方 API 提供” 并附上 NextTrace 官网或 NT…
🥰1
OpenTrace v1.5.2 已发布 https://github.com/Archeb/opentrace/releases/tag/v1.5.2
🥰2
还是有很多用户不知道怎么让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
感谢大家的支持，NextTrace 已获得 8000+ STARS 🏆
🥰6
NextTrace TraceMap 服务已完成升级改造，使用 peer.as 提供服务。 #NextTrace
[软件更新] 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 …
[功能预告] 受到 TraceBar 的激励，NextTrace 将很高兴地带来全新的 MTR 可视化历史图表 功能。 该 feature 可以在 TUI 中展示每个 hop 的 latency history，帮助用户更直观地检查链路波动、丢包趋势和路径质量变化。 欢迎更新测试版试用，如有问题或 further improvement 建议，欢迎提交 Issue。 #NextTrace
🥰5
[软件更新] 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…
🦞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
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…
[软件更新] 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 链路：避免旧…
[软件更新] 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.
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.
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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“NextTrace 公告板” (@nexttrace), 903 subscribers as measured 31 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.