Telegram RegisterThe public register of Telegram
Telegram profile photo for Telegram高速代理 vpn 节点

Channel

Telegram高速代理 vpn 节点

@zuozhudaili

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

11,848subscribers

+1,125 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-1003961439778
TypeChannel
Username@zuozhudaili
CreatedBetween 1 April 2026 and 21 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/zuozhudaili

Topic

Other / unclassifiable — 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 87% 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 why it has no browse page of its own yet.

Growth

10,58011,84811,21410 August 2026 — 10,723 subscribers10 August 2026 — 10,757 subscribers11 August 2026 — 10,712 subscribers12 August 2026 — 10,714 subscribers13 August 2026 — 10,682 subscribers14 August 2026 — 10,662 subscribers16 August 2026 — 10,586 subscribers17 August 2026 — 10,580 subscribers18 August 2026 — 10,627 subscribers19 August 2026 — 10,695 subscribers20 August 2026 — 10,829 subscribers22 August 2026 — 10,986 subscribers23 August 2026 — 11,068 subscribers25 August 2026 — 11,017 subscribers26 August 2026 — 11,033 subscribers27 August 2026 — 11,087 subscribers28 August 2026 — 11,210 subscribers29 August 2026 — 11,217 subscribers30 August 2026 — 11,209 subscribers31 August 2026 — 11,220 subscribers1 September 2026 — 11,230 subscribers2 September 2026 — 11,152 subscribers3 September 2026 — 11,166 subscribers5 September 2026 — 11,331 subscribers8 September 2026 — 11,561 subscribers11 September 2026 — 11,675 subscribers13 September 2026 — 11,733 subscribers14 September 2026 — 11,769 subscribers16 September 2026 — 11,762 subscribers18 September 2026 — 11,848 subscribers10 August 202618 September 2026
30 measurements spanning 39 days, net +1,125. 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 10,390–12,038 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
18 Sept 2026, 13:1611,848+86
16 Sept 2026, 08:5811,762-7
14 Sept 2026, 17:5911,769+36
13 Sept 2026, 05:1911,733+58
11 Sept 2026, 05:3811,675+114
8 Sept 2026, 12:1511,561+230
5 Sept 2026, 08:5611,331+165
3 Sept 2026, 08:4511,166+14
2 Sept 2026, 05:0711,152-78
1 Sept 2026, 02:4511,230+10
31 Aug 2026, 01:0411,220+11
30 Aug 2026, 00:5311,209-8
29 Aug 2026, 00:2711,217+7
28 Aug 2026, 03:2511,210+123
27 Aug 2026, 01:3811,087+54
26 Aug 2026, 03:3811,033+16
25 Aug 2026, 02:0511,017-51
23 Aug 2026, 15:5411,068+82
22 Aug 2026, 00:1510,986+157
20 Aug 2026, 17:2310,829first reading

Engagement

22 posts held, back to 21 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 33 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
17.0%
avg views ÷ 11,848 subscribers
Avg views / post
2,020
4 posts measured
Reaction rate
5.56%
reactions ÷ views · ER floor
Posts in window
4
of 22 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 2 September 2026
Posts held22 (21 July 20262 September 2026)
Views total8,079
Reactions total449
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 01:57 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

2,739 reactions across 22 posts, in 27 distinct kinds. The most used accounts for 43.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,19743.7%
1,17843.0%
😭863.14%
🔥612.23%
🤔321.17%
🤓281.02%
👏250.913%
😍180.657%
🕊160.584%
👻120.438%
🤯120.438%
🍓90.329%
🙏90.329%
🍌80.292%
🥰80.292%
🫡80.292%
🌚60.219%
😁40.146%
🤩40.146%
😱30.11%
7 further kinds150.548%

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

Measured over the 22 most recent posts we hold, published 21 July 2026 to 2 September 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

2 Sept 2026, 22:20 UTC219 views23 reactionsread 3 September 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7222173352

👍23

2 Sept 2026, 22:03 UTC230 views19 reactionsread 3 September 2026
Photo

🚀 今日线路维护通知 更新时间:2026.09.03 当前节点:🇸🇬Singapore 线路 🎙 稳定连接 🛡 优化网络体验 🔄 持续维护更新 💬 线路概览:点击蓝色字体连接代理使用 切记关闭vpn!!! ━━━━━━━━━━━━━━ 🟢①日本高速|🟢②新加坡普通 ━━━━━━━━━━━━━━ 🗺 线路说明:如遇连接异常,尝试切换其它线路 📍Tips: 线路会持续维护优化 欢迎分享给需要的朋友 一起保持高速稳定连接 🔔 免费更新高速代理 @zuozhudaili 下方点赞增加权重

👍19

31 Aug 2026, 21:49 UTC≈1,620 views84 reactionsread 3 September 2026
Photo

🚀 今日线路修复通知 更新时间:2026.09.01 当前节点:🇯🇵 Japan 高速线路 🎙 稳定连接 🛡 优化网络体验 🔄 持续维护更新 💬 线路概览:点击蓝色字体连接代理使用 切记关闭vpn!!! ━━━━━━━━━━━━━━ 🟢①日本高速|🟢②日本备用 ━━━━━━━━━━━━━━ 🗺 线路说明:如遇连接异常,尝试切换其它线路 📍Tips: 线路会持续维护优化 欢迎分享给需要的朋友 一起保持高速稳定连接 🔔 免费更新高速代理 @zuozhudaili 下方点赞增加权重

👍5524👻3😍2

26 Aug 2026, 04:44 UTC≈6,010 views323 reactionsread 3 September 2026
Photo

🚀 今日线路维护通知 更新时间:2026.08.26 当前节点:🇯🇵 Japan 高速线路 🎙 稳定连接 🛡 优化网络体验 🔄 持续维护更新 💬 线路概览:点击蓝色字体连接代理使用 切记关闭vpn!!! ━━━━━━━━━━━━━━ 🟢①日本高速|🟢②日本备用 ━━━━━━━━━━━━━━ 🗺 线路说明:如遇连接异常,尝试切换其它线路 📍Tips: 线路会持续维护优化 欢迎分享给需要的朋友 一起保持高速稳定连接 🔔 免费更新高速代理 @zuozhudaili 下方点赞增加权重

👍22280🕊14🤔6🍌1

22 Aug 2026, 12:22 UTC≈8,270 views44 reactionsread 3 September 2026
File

😄 Navo 4.0.3 现已发布! 这是一个紧急修复版本,同时在整体用户体验方面又向前迈进了一步。 🤩 修复了偶发的视频播放失败问题以及重试循环。 ⚡ 加快了聊天列表的加载速度,并解决了多个加载问题。 ✨ 优化了用户界面,提供更一致、更现代、更精致的用户体验。 加载速度更快。播放更可靠。Navo 更加现代化。 我们建议所有用户更新到 4.0.3 版本!🚀 ⚠️ 安装说明 🍎 1.macOS 安装完成后,打开终端并运行以下命令。否则,Navo 可能无法正常启动: xattr -rd com.apple.quarantine /Applications/Navo.app 🤩2. iOS navo-4.0.3+403-unsigned.ipa 文件未签名。请在安装前自行进行签名。 #navo #电报 #第三方tg #第三方客户端

👍2615🕊2🔥1

18 Aug 2026, 10:23 UTC≈9,910 views391 reactionsread 3 September 2026
Photo

🚀 今日线路维护通知 更新时间:2026.08.12 当前节点:🇯🇵 Japan 高速线路/🇸🇬Singapore线路 🎙 稳定连接 🛡 优化网络体验 🔄 持续维护更新 💬 线路概览:点击蓝色字体连接代理使用 切记关闭vpn!!! ━━━━━━━━━━━━━━ 👍 日本高速| 🥇 日本备用 | 🥈 新加坡 ━━━━━━━━━━━━━━ 🗺 线路说明:如遇连接异常,尝试切换其它线路 📍Tips: 线路会持续维护优化 欢迎分享给需要的朋友 一起保持高速稳定连接 🔔 免费更新高速代理 @zuozhudaili 下方点赞增加权重

👍271109👏8🔥3

16 Aug 2026, 07:15 UTC≈7,390 views68 reactionsread 3 September 2026

tg://proxy?server=34.84.170.183&port=32432&secret=eebc97d8b09e9f2c92678ec05f9545bf247777772e6d6963726f736f66742e636f6d 把测速打到评论区

👍4910😍7😢2

13 Aug 2026, 13:05 UTC≈9,240 views32 reactionsread 3 September 2026
File

🚀 Navo🌟 3.0.6 已正式上线! 本次版本重点围绕聊天体验、群组功能、媒体文件操作以及反垃圾能力进行了全面优化。 ✨ 主要更新 1. 全面优化聊天窗口体验 * 优化消息加载与渲染 * 修复聊天窗口闪屏问题 * 修复消息定位不准确问题 * 修复未读、回应、提及等状态无法实时刷新的问题 * 进一步提升聊天窗口整体流畅度与稳定性 2. 修复群组话题功能 * 修复话题相关功能异常,提升带话题群组的使用体验 3. 新增群组和频道成员展示 * 支持查看群组及频道成员信息 4. 移动端支持媒体和文件粘贴 * 现在可以直接从其他应用复制媒体或文件,并粘贴到 Navo 输入框 5. 关键词过滤升级为反垃圾系统 * 全面升级消息过滤能力 * 增加更多自定义选项 * 更灵活地控制垃圾消息与敏感内容 感谢大家一直以来的反馈与支持 ❤️ Navo 3

15👍13😍3🔥1

12 Aug 2026, 08:24 UTC≈6,780 views52 reactionsread 3 September 2026
Photo

🚀 今日线路维护通知 更新时间:2026.08.12 当前节点:🇯🇵 Japan 高速线路 🎙 稳定连接 🛡 优化网络体验 🔄 持续维护更新 💬 线路概览:点击蓝色字体连接代理使用 切记关闭vpn!!! ━━━━━━━━━━━━━━ 👍 推荐线路 | 🥇 备用 | 🥈 备用 ━━━━━━━━━━━━━━ 🗺 线路说明:三条线路均来自同一节点,不同端口,如遇连接异常,尝试切换其它线路 📍Tips: 线路会持续维护优化 欢迎分享给需要的朋友 一起保持高速稳定连接 🔔 免费更新高速代理 @zuozhudaili 👉点我连接新加坡线路👈

👍279🍓7😍5🌭2👾1🥰1

8 Aug 2026, 07:00 UTC≈8,600 views184 reactionsread 3 September 2026
Photo

🚀 今日维护通知 更新时间:2026.08.07 当前节点:🇯🇵 Japan 高速线路 🎙 稳定连接 🛡 优化网络体验 🔄 持续维护更新 💬 线路概览:点击蓝色字体连接代理使用 切记关闭vpn!!! ━━━━━━━━━━━━━━ 👍 推荐线路 | 🥇 备用 | 🥈 备用 ━━━━━━━━━━━━━━ 🗺 线路说明:三条线路均来自同一节点,不同端口,如遇连接异常,尝试切换其它线路 📍Tips: 线路会持续维护优化 欢迎分享给需要的朋友 一起保持高速稳定连接 🔔 免费更新VPN代理 @zuozhudaili 下方点赞增加权重

👍12947🔥5🥱3

4 Aug 2026, 13:32 UTC≈9,240 views194 reactionsread 3 September 2026
Photo

🚀 今日维护通知 更新时间:2026.08.04 当前节点:🇯🇵 Japan 高速线路 🎙 稳定连接 🛡 优化网络体验 🔄 持续维护更新 💬 线路概览:点击蓝色字体连接代理使用 切记关闭vpn!!! ━━━━━━━━━━━━━━ 👍 推荐线路 | 🥇 备用 | 🥈 备用 ━━━━━━━━━━━━━━ 🗺 线路说明:三条线路均来自同一节点,不同端口,如遇连接异常,尝试切换其它线路 📍Tips: 线路会持续维护优化 欢迎分享给需要的朋友 一起保持高速稳定连接 🔔 免费更新VPN代理 @zuozhudaili 下方点赞增加权重

154👍34👏3🤔2🥰1

4 Aug 2026, 13:02 UTC≈7,820 views16 reactionsread 3 September 2026

停机升级中ing……

🤯122👍2

Showing the 12 most recent of 22 posts we hold for @zuozhudaili. 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 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Telegram高速代理 vpn 节点” (@zuozhudaili), 11,848 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/zuozhudaili.

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.