https://t.me/soso?start=boost_BetterWNews_7037005354 ⚡️ 帮「世界简报中文网」助力一下 点开 SOSO 即可完成,更多助力有助于获得更多搜索曝光。

Channel
v2ray免费节点
@clashvpnn
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,663subscribers
-149 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003869784749 |
|---|---|
| Type | Channel |
| Username | @clashvpnn |
| Created | Between 1 February 2026 and 16 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/clashvpnn |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 08:21 | 1,663 | -28 |
| 12 Sept 2026, 13:19 | 1,691 | -4 |
| 8 Sept 2026, 01:00 | 1,695 | -19 |
| 2 Sept 2026, 12:14 | 1,714 | -7 |
| 30 Aug 2026, 22:56 | 1,721 | +3 |
| 27 Aug 2026, 22:34 | 1,718 | -9 |
| 25 Aug 2026, 03:17 | 1,727 | -9 |
| 21 Aug 2026, 09:36 | 1,736 | -13 |
| 18 Aug 2026, 02:22 | 1,749 | -18 |
| 14 Aug 2026, 18:49 | 1,767 | -19 |
| 10 Aug 2026, 23:08 | 1,786 | -23 |
| 7 Aug 2026, 16:36 | 1,809 | -3 |
| 7 Aug 2026, 05:03 | 1,812 | first reading |
Engagement
18 posts held, back to 16 July 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 2 pages 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 18 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
56 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 76.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 43 | 76.8% | |
| 🔥 | 4 | 7.14% | |
| 👍 | 3 | 5.36% | |
| 😁 | 2 | 3.57% | |
| 👻 | 1 | 1.79% | |
| 💯 | 1 | 1.79% | |
| 😨 | 1 | 1.79% | |
| 🤔 | 1 | 1.79% |
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 11 of the 18 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 56 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 16 July 2026 to 4 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.
Recent posts
@Apple_CMS_bot 又又开放注册啦! 加油^0^~ 还有50个注位
❤7💯1
@Apple_CMS_bot Tre大佬的emby喔,目前有30个注位
❤7
美国节点vless://[email protected]:8443?path=%2F&security=tls&encryption=none&insecure=0&host=t1s1.rittbo.kdns.fr&fp=chrome&ech=cloudflare-ech.com%2Bhttps%3A%2F%2Fdns.alidns.com%2Fdns-query&type=ws&allowInsecure=0&sni=t1s1.rittbo.kdns.fr#Cactus vless://[email protected]:8443?path=%2F&security=tls&encryption=none&insecure=0&host=t1s1.rittbo.kdns.fr&fp=chrome&e…
❤7👍2🤔1😨1
Emby服测试 网页端注册 https://mi.ooxoo.cyou/ 邀请码:PKNXfzQ 邀请码使用次数 0/50
❤3
@GithubCOTV 求求你们进来玩
dGc6Ly9wcm94eT9zZXJ2ZXI9NDUuMjIxLjExNS4xNjkmcG9ydD01ODAxJnNlY3JldD1lYjFjMGVkMzA0ODdhZWQ0ZDBiOTNjMGZlOWU0YzU3Nw== base64版本的代理(提示,问ai)
❤3
极速tg代理 tg://proxy?server=195.172.139.60&port=32430&secret=ee01a888a94071a122b2c25153e940d1f97777772e6d6963726f736f66742e636f6d
❤5
File, posted without a caption
❤4
Kimi是真的强,完全不带吹的
🔥4😁2👻1
帮我助力,一起拿大奖!完成 Kimi 注册,你我都能 100% 拿奖,最高可得 1 年会员等值权益:https://kimi-bot.com/activities/zh-cn/viral-referral/share?scenario=invite&from=share_poster&invitation_code=PEPE8D
🥳🥳🥳新版本更新啦!! 更新功能 极高自由度的主页自定义 在基础的调整上,加入了css自定义样式,甚至可以自主编入html样式 更新性能 - 优化标签页点击、关闭和长按固定逻辑 - 新增网站级兼容模式 - 优化广告过滤请求路径 - 减少 Cookie 和用户脚本数据的同步写入 - 改进 WebView 预热与渲染进程恢复 - 修复后台任务可能被静默丢弃的问题 此次虽然更新的功能不多,但是bug可是修了一堆又一堆,代码仍然压缩在kb级别。 github: https://github.com/bi-box/Median
Showing the 12 most recent of 18 posts we hold for @clashvpnn. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“v2ray免费节点” (@clashvpnn), 1,663 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/clashvpnn.
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.