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 9 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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
65 measurements spanning 101 days, net -13,267. 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 26,964–44,211 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
17 Nov 2026, 02:58
28,954
-105
13 Nov 2026, 17:49
29,059
-52
11 Nov 2026, 00:55
29,111
-29
9 Nov 2026, 09:37
29,140
-19
7 Nov 2026, 21:48
29,159
-21
6 Nov 2026, 19:55
29,180
-11
5 Nov 2026, 19:26
29,191
-9
4 Nov 2026, 18:40
29,200
-46
3 Nov 2026, 17:05
29,246
-156
2 Nov 2026, 14:28
29,402
-21
1 Nov 2026, 11:26
29,423
-118
31 Oct 2026, 08:15
29,541
-25
30 Oct 2026, 08:37
29,566
-116
29 Oct 2026, 05:31
29,682
-7
28 Oct 2026, 06:16
29,689
-14
27 Oct 2026, 07:46
29,703
-12
26 Oct 2026, 07:28
29,715
-28
25 Oct 2026, 06:46
29,743
-159
24 Oct 2026, 06:46
29,902
-8
23 Oct 2026, 09:06
29,910
first reading
Engagement
25 posts held, back to 12 September 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 187 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
54.6%
avg views ÷ 28,954 subscribers
Avg views / post
15,800
1 post measured
Reaction rate
0.234%
reactions ÷ views · ER floor
Posts in window
1
of 25 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
Window
Rolling 30 days · latest post in window 28 October 2026
Posts held
25 (12 September 2024 – 28 October 2026)
Views total
15,800
Reactions total
37
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
18 Nov 2026, 13:02 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
21
Links
16
Lifetime counters from Telegram’s own channel header, read 18 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
1,212 reactions across 24 posts, in 17 distinct kinds. The most used accounts for 19.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
234
19.3%
❤
202
16.7%
🔥
128
10.6%
🎉
120
9.90%
🥰
104
8.58%
😍
87
7.18%
❤🔥
85
7.01%
💯
85
7.01%
🤩
71
5.86%
👏
45
3.71%
😁
28
2.31%
👎
10
0.825%
💩
4
0.33%
🤣
4
0.33%
🤯
2
0.165%
🦄
2
0.165%
👌
1
0.083%
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 24 of the 25 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 1,212 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 12 September 2024 to 28 October 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: 0 of 1 post held from the last 30 days (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).
当 AI 开始批量做监控:Anthropic 威胁报告给普通用户的隐私提醒
Anthropic 在 2026 年 9 月发布的威胁情报报告中披露,多国政府关联组织、商业情报公司及其他行为体正在利用 Claude 批量分析社交媒体内容,整理个人资料、判断用户位置和政治倾向,并辅助建立自动化监控系统。
AI 降低了大规模数据分析和个人画像所需的人力成本,也让原本零散的互联网信息更容易被集中处理。
365VPN 安全团队结合报告中的监控案例,分析 IP 地址、DNS 查询和网络连接信息在这一环境下所面临的隐私风险,以及 VPN 可以提供哪些实际保护。
Blog 全文👉 https://365vpn.com/blog/dang-a-i-kai-shi-pi-liang-zuo-jian-kong-a-n-t-h-r-o-p-i-c-wei-xie-bao-gao-gei-pu-tong-yong-hu-de-yin-si-ti-…
关于 365VPN 支付手段的说明:
365VPN 目前支持微信支付、支付宝等方式,方便国内用户快速完成订阅。不过从用户的个人隐私保护的角度,我们更建议优先选择虚拟货币、应用商店订阅或信用卡支付。
微信/支付宝在部分场景下可能受到通道稳定性、风控审核等因素影响。相比之下,虚拟货币、App Store / Google Play 订阅和信用卡支付链路更清晰,订单记录更完整,续费、退款和售后处理也更稳定。
因此,微信/支付宝可以作为便捷支付方式使用;对于长期订阅用户,我们更推荐使用虚拟货币、商店订阅或信用卡,以获得更稳定的支付与服务体验。
此外,我们还提供15天无理由退款;如有任何问题,24 小时客服随时为您服务。
频道 @a365VPN 群组 @b365vpn
❤14❤🔥11😍8👍7💯7🎉3🔥3🤩2
Showing the 12 most recent of 25 posts we hold for @a365VPN. 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
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 17 November 2026 — this
entry's latest reading, not the date you are reading this.
“365VPN官方频道” (@a365VPN), 28,954 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/a365VPN.
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.