Channel
@nextinapp
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
1,029subscribers
+17 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003306282448 |
|---|---|
| Type | Channel |
| Username | @nextinapp |
| Created | Between 1 November 2025 and 28 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/nextinapp |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 09:03 | 1,029 | +17 |
| 9 Aug 2026, 13:01 | 1,012 | no change |
| 9 Aug 2026, 12:32 | 1,012 | first reading |
19 posts held, back to 19 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 pageof Telegram’s post history, 20 posts per page.
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 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 19 (19 March 2026 – 9 August 2026) |
| Views total | 2,513 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 12:32 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.
Measured directly from 2 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.
21 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 66.7% | |
| 👍 | 7 | 33.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 13 of the 19 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 21reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 19 March 2026 to 9 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.
🚀 Nextin 安卓版即将正式发布 安卓版将延续 Nextin 一贯的产品设计，并与 iOS 版保持统一的 UI 与使用体验。 📱 主要功能 • iOS / Android 统一 UI 设计，原生 Kotlin 架构开发，纵向丝滑 • 内置代理功能 • 完整的 App 内套餐购买功能 • 内置弹窗通知与在线客服 • 完整的邀请系统 • 支持直接分享 App 安装包 • 链式代理功能 • 高级订阅加密，进一步保护节点与订阅安全 • iOS / Android 均已内置 Nextin 自研协议（需额外购买） 同时，Nextin 独立打包程序也即将上线，后续将进一步完善整个 Nextin 多平台生态。 更多功能和发布时间将在近期公布，敬请期待。 🚀 如果您有好的建议或者想法也可以联系我们 📩 快速接入 老板：@nextin_app 自助下单 & 对接：@NextinApp_bot 点击打开小程序
👍2
目前小程序中已经可以添加技术人员，技术人员可以帮您配置站点。如果之前有老板把站点转移给技术人员的可以联系我迁回 📩 快速接入 老板：@nextin_app 自助下单 & 对接：@NextinApp_bot 点击打开小程序
🎉 Nextin v1.2.3 正式版已发布！ ✨ 新增功能 👥 邀请功能 新增邀请功能。 可在机器人后台开启或关闭，默认关闭。 🔐 订阅链接智能登录 用户导入你的订阅链接后，将自动跳转至登录页面。 适用于未完全封端的用户，无需手动输入账号。 使用前请前往机器人后台完成相关配置。 机器人小程序 新增机器人小程序，可直接通过网页进行 UI 配置。 配置界面更加直观，操作更加便捷。 新增配置向导，新站点可快速完成初始化配置。 ⚡ 优化 优化机器人配置流程，降低新站点部署成本。 提升整体配置体验与易用性。 📩 快速接入 老板：@nextin_app 自助下单 & 对接：@NextinApp_bot 点击打开小程序
📢 测试版更新 最新测试版新增了防呆设计。 当用户没有输入识别码，而是导入的是订阅链接，App 会自动识别，并直接跳转到登录页面，引导用户完成登录。 具体设置可在机器人高级设置中开启。 售后群中置顶链接，可下载最新测试版。 欢迎大家更新测试版体验，如有问题或建议，欢迎随时反馈！ 🚀
❤1
最新测试版已添加邀请功能，机场主可在售后群置顶找到testflight链接，安装后在机器人中开启邀请功能即可，支持xiaov2board、xboard、v2board、ppanel。 📩 快速接入 老板：@nextin_app 自助下单 & 对接：@NextinApp_bot
👍1
https://wiki.nextinnet.com/merchant/overview.html#机场主说明总览
最新测试版 v1.1.1 build（88）添加注册功能，默认开启，如想关闭，请前往机器人高级设置中关闭。同时各位机场主也可以测试一下有没有bug，可以反馈一下
🚀 Nextin v1.1.1 build（84）测试版更新 本次版本带来多项核心能力升级，进一步提升可玩性与兼容性： ✨ 新功能 🔧 支持 HTTPS 重写（Rewrite）功能 🔗 支持链式代理（Proxy Chain） 长按节点即可设置链式出口 🧩 兼容大部分小火箭（Shadowrocket）模块规则 ▶️ 支持 YouTube 去广告模块（实验性） ⚡ 一键导入示例 复制下方链接到浏览器即可快速体验 YouTube 去广告模块，支持画中画，后台播放等功能： nextin://install?module=rewrite&url=https://yfamilys.com/module/YouTubeAd.sgmodule 🌐 更多模块 可前往以下网站获取更多模块进行测试与导入： 👉 https://yfamilys.com/shadowrocket 如遇模块兼容问题，欢迎在群内反馈，我们会持续优化适配。 …
❤2👍1
🚀 Nextin v1.1更新日志 🎉 🌐 支持内置代理 再也不用担心后端地址被 GFW 污染，导致 App 无法获取配置或连接失败。 现在支持设置 代理优先 或 故障转移，后端访问更稳定，连接体验更安心。 📷 支持扫描二维码获取配置 现在可以通过扫描二维码快速获取配置，一键完成导入，操作更简单。 同时支持在一键导入中直接携带 加密后的订阅信息，即使在福建等特殊网络环境下，也能更顺利地获取订阅文件。 🔗 支持多个获取订阅 URL 覆盖 机场主可配置多个订阅获取地址，提高订阅获取成功率。 即使某个接口异常，也可以自动尝试其他地址，减少订阅获取失败的问题。 📢 支持弹窗公告功能 重要公告、优惠信息、维护通知等内容，现在可以直接在 Nextin 主页展示。 用户打开 App 即可第一时间看到关键信息。 🔔 支持 iOS 系统通知 可用于重要公告、活动提醒、优惠通知等场景。 该功能将稍后推出，敬请期待。 🏠 支持主页不检测地…
❤3👍3
V1.0.10已通过审核，正式上架App stote •🚀 支持 VLESS XHTTP 协议 新增对 VLESS Reality XHTTP 协议的支持。 •🔍 无需启动代理即可选择节点 现在用户可以在未开启代理的情况下自由选择和切换节点，操作更加便捷高效。 •🛠 支持直接编辑订阅分流规则 用户可在应用内直接修改订阅中的分流规则，实现更加灵活的个性化配置。 •🔗 兼容 Shadowrocket 格式的订阅链接 新增对小火箭（Shadowrocket）订阅格式的支持，迁移配置更加轻松顺畅。 •🐞 问题修复与性能优化 修复了一些已知问题，进一步提升应用的稳定性与使用体验。 📩 快速接入 老板：@nextin_app 自助下单 & 对接：@NextinApp_bot
❤2
TVOS现已通过审核，正式上架App store！
1.0.9已通过审核 订阅加密先已正式可用
❤1
Showing the 12 most recent of 19 posts we hold for @nextinapp. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
开发优先级
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 19 most recent posts we hold, published 19 March 2026 to 9 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 1,145,673 of 1,160,990entries 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Nextin-iOS/Mac一键客户端” (@nextinapp), 1,029 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/nextinapp.
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.