Telegram RegisterThe public register of Telegram
Telegram profile photo for TunNet 免费VPN|官方频道

Channel

TunNet 免费VPN|官方频道

@NextTunNet

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

21,948subscribers

+20,590 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003593831365
TypeChannel
Username@NextTunNet
DescriptionTunNet 官方频道,发布版本更新、产品公告、使用教程与网络安全资讯。关注 TunNet,让网络连接更安全、稳定、简单。
Created31 December 2025 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live12 November 2026
Measurements held46
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/NextTunNet

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 59% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

1,35821,94811,65310 August 2026 — 1,358 subscribers10 August 2026 — 1,499 subscribers14 August 2026 — 1,808 subscribers17 August 2026 — 2,144 subscribers20 August 2026 — 3,105 subscribers24 August 2026 — 4,520 subscribers27 August 2026 — 6,022 subscribers30 August 2026 — 7,077 subscribers2 September 2026 — 7,773 subscribers7 September 2026 — 10,094 subscribers10 September 2026 — 11,223 subscribers12 September 2026 — 11,406 subscribers14 September 2026 — 11,550 subscribers16 September 2026 — 11,690 subscribers18 September 2026 — 11,892 subscribers24 September 2026 — 13,809 subscribers3 October 2026 — 15,792 subscribers8 October 2026 — 16,469 subscribers12 October 2026 — 17,192 subscribers14 October 2026 — 17,420 subscribers15 October 2026 — 17,621 subscribers16 October 2026 — 17,774 subscribers17 October 2026 — 18,130 subscribers18 October 2026 — 18,343 subscribers19 October 2026 — 18,450 subscribers20 October 2026 — 18,521 subscribers21 October 2026 — 18,736 subscribers23 October 2026 — 18,980 subscribers23 October 2026 — 19,284 subscribers24 October 2026 — 19,529 subscribers25 October 2026 — 19,677 subscribers26 October 2026 — 19,859 subscribers27 October 2026 — 19,979 subscribers28 October 2026 — 20,076 subscribers29 October 2026 — 20,210 subscribers30 October 2026 — 20,376 subscribers1 November 2026 — 20,553 subscribers2 November 2026 — 20,701 subscribers3 November 2026 — 20,795 subscribers4 November 2026 — 20,899 subscribers5 November 2026 — 21,051 subscribers6 November 2026 — 21,170 subscribers7 November 2026 — 21,264 subscribers8 November 2026 — 21,545 subscribers10 November 2026 — 21,733 subscribers12 November 2026 — 21,948 subscribers10 August 202612 November 2026
46 measurements spanning 94 days, net +20,590. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 46
Measured (UTC)SubscribersChange
12 Nov 2026, 12:0721,948+215
10 Nov 2026, 07:4721,733+188
8 Nov 2026, 16:1721,545+281
7 Nov 2026, 10:1521,264+94
6 Nov 2026, 13:0521,170+119
5 Nov 2026, 11:0521,051+152
4 Nov 2026, 10:3120,899+104
3 Nov 2026, 07:0520,795+94
2 Nov 2026, 05:0020,701+148
1 Nov 2026, 02:4120,553+177
30 Oct 2026, 23:1420,376+166
29 Oct 2026, 20:2020,210+134
28 Oct 2026, 17:5720,076+97
27 Oct 2026, 18:1019,979+120
26 Oct 2026, 21:1619,859+182
25 Oct 2026, 22:4719,677+148
24 Oct 2026, 21:1519,529+245
23 Oct 2026, 20:4819,284+304
23 Oct 2026, 00:0818,980+244
21 Oct 2026, 18:1018,736first reading

Engagement

40 posts held, back to 31 December 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 22 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
74.7%
avg views ÷ 21,948 subscribers
Avg views / post
16,400
10 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
10
of 40 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 9 November 2026
Posts held40 (31 December 2025 – 9 November 2026)
Views total163,880
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 03:37 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

Lifetime counters from Telegram’s own channel header, read 13 November 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

155 reactions across 15 posts, in 4 distinct kinds. The most used accounts for 64.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍10064.5%
❤4327.7%
🥰95.81%
👏31.94%

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

Measured over the 40 most recent posts we hold, published 31 December 2025 to 9 November 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

Telegram’s own ‘edited’ marker: 3 of 10 posts held from the last 30 days (30.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

9 Nov 2026, 01:41 UTC≈7,070 viewsread 13 November 2026
File

优化网络切换与连接恢复,提升连接稳定性;修复若干问题。

7 Nov 2026, 22:00 UTC≈4,320 viewsread 8 November 2026
File

我们尝试加入了备用线路的逻辑,能够在高峰期实现无感按需切换。虽然目前还不是特别成熟,需要测试一段时间,但非常推荐大家升级体验,因为没有任何负面效果。

7 Nov 2026, 16:19 UTC≈5,010 viewsread 8 November 2026

因为近期用户激增,晚高峰出现线路拥堵,我们计划于下周五之前完成线路扩容工作

6 Nov 2026, 04:43 UTC≈7,980 viewsread 8 November 2026

部分节点因为有用户拿去下载BT(涉及 DMCA 等版权投诉)导致被机房罚款,目前正在等待服务商审核。请各位老大尽量别碰这些,网上很多都是钓鱼的 BT 链接,一旦被投诉罚款真的非常麻烦。

31 Oct 2026, 05:13 UTC≈16,800 viewsread 8 November 2026

iOS的测试遇到了一点小问题,我们协议实现内存占用太高了,会被iOS杀进程,可能要推迟一段时间了。

30 Oct 2026, 15:12 UTC≈18,400 viewsread 8 November 2026

以往开大会都是大会开始第一天象征性拉闸一波,这次似乎有点持久,GFW仍然在高强度工作

27 Oct 2026, 09:38 UTC≈23,700 viewsread 8 November 2026

这两天在开大会,线路可能被干扰的比较严重

25 Oct 2026, 09:20 UTC≈27,100 viewsread 8 November 2026
File

TunNet 0.2.18 更新日志 - 优化连接与后台恢复体验。 - 改善更新流程,修复部分下载与安装异常。 - 修复分应用列表偶发显示异常。 - 调整界面细节,改善大字体与小屏使用体验。

24 Oct 2026, 13:56 UTC≈26,900 viewsread 8 November 2026
Photo

这两天晚高峰体验确实比较差,主要还是国内运营商那边的问题。目前新线路已经下单,测试表现还不错;不过因为月底了,没拿到很大的端口,所以晚高峰可能还会有点拥挤。新线路计划在11月1日正式切换,届时晚高峰的使用体验会好很多。 另外,最近我一直在写iOS,安卓端的更新频率就没那么高。我平时只能利用工作之余做开发维护,还请各位老大理解一下。最近国内运营商这边状况比较多,我们商业项目那边也很忙,各种通报、拔线的问题目前还没处理完,确实有点分身乏术,感谢大家体谅。

22 Oct 2026, 13:43 UTC≈26,600 viewsread 8 November 2026

近期国内运营商愈发作妖,尽量选择同网入口

30 Sept 2026, 11:24 UTC≈42,000 viewsread 8 November 2026

日本节点(05-12)已更换新 IP。 同时,我们将在今天和明天推送新的客户端版本,重点修复当前协议不好用、速度较慢的问题。由于之前的协议是为了应对 GFW 紧急修改并仓促推送的,很多细节尚未完善,新版本已针对此做了大量优化。目前正在测试,测试好之后会推送更新。

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

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.

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

“TunNet 免费VPN|官方频道” (@NextTunNet), 21,948 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/NextTunNet.

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.