#系统公告 💵为方便大家付款,云兔Cloud 现已新增以下支付方式: 😂 USDT- TRC20 💰 USDT- BEP20 💰 GRAM- TON 🎛️ USDT- Plasma 👛 OkPay ✔️下单时可在收银台选择对应方式,具体以页面显示为准。 ⁉️付款前请核对币种、转账网络、收款地址及金额,切勿跨链转账,以免造成资产损失。
👍9❤4👏1
Signed Channel Help

Channel
@soso_vpn
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
14,166subscribers
+5,484 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002135038529 |
|---|---|
| Type | Channel |
| Username | @soso_vpn |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 57 |
| Confirmed unchanged | 1 time, most recently 19 November 2026 |
| On Telegram | t.me/soso_vpn |
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 47% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Nov 2026, 03:19 | 14,166 | +96 |
| 16 Nov 2026, 05:59 | 14,070 | +145 |
| 12 Nov 2026, 17:51 | 13,925 | +51 |
| 10 Nov 2026, 14:01 | 13,874 | +63 |
| 8 Nov 2026, 23:11 | 13,811 | +73 |
| 7 Nov 2026, 12:35 | 13,738 | +60 |
| 6 Nov 2026, 12:39 | 13,678 | +56 |
| 5 Nov 2026, 10:46 | 13,622 | +65 |
| 4 Nov 2026, 11:47 | 13,557 | +39 |
| 3 Nov 2026, 11:15 | 13,518 | +36 |
| 2 Nov 2026, 11:27 | 13,482 | +33 |
| 1 Nov 2026, 13:06 | 13,449 | +52 |
| 31 Oct 2026, 11:54 | 13,397 | +75 |
| 30 Oct 2026, 13:45 | 13,322 | +26 |
| 29 Oct 2026, 17:05 | 13,296 | +38 |
| 28 Oct 2026, 19:49 | 13,258 | +49 |
| 27 Oct 2026, 21:16 | 13,209 | +45 |
| 26 Oct 2026, 18:49 | 13,164 | +26 |
| 25 Oct 2026, 22:10 | 13,138 | +28 |
| 24 Oct 2026, 20:26 | 13,110 | first reading |
24 posts held, back to 8 November 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 67 pages of 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.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 24 (8 November 2024 – 17 November 2026) |
| Views total | 7,890 |
| Reactions total | 28 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 21:40 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.
1,156 reactions across 24 posts, in 12 distinct kinds. The most used accounts for 58.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 672 | 58.1% | |
| 👍 | 185 | 16.0% | |
| 😍 | 57 | 4.93% | |
| 🔥 | 43 | 3.72% | |
| 🤩 | 40 | 3.46% | |
| 🥰 | 38 | 3.29% | |
| ❤🔥 | 36 | 3.11% | |
| 🎉 | 36 | 3.11% | |
| 💯 | 35 | 3.03% | |
| 😁 | 8 | 0.692% | |
| 👎 | 3 | 0.26% | |
| 👏 | 3 | 0.26% |
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 24 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,156 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 8 November 2024 to 17 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.
Telegram’s own ‘edited’ marker: 2 of 2 posts held from the last 30 days (100.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).
#系统公告 💵为方便大家付款,云兔Cloud 现已新增以下支付方式: 😂 USDT- TRC20 💰 USDT- BEP20 💰 GRAM- TON 🎛️ USDT- Plasma 👛 OkPay ✔️下单时可在收银台选择对应方式,具体以页面显示为准。 ⁉️付款前请核对币种、转账网络、收款地址及金额,切勿跨链转账,以免造成资产损失。
👍9❤4👏1
Signed Channel Help
#优惠活动 ▎🎁【双11】特别折扣码:1111 限量500次,用完即止! 任意套餐月付:7️⃣折 任意套餐季付:6️⃣折 不限时套餐,不参与本次活动! ⚠️ 注意:更换套餐会自动重置原套餐信息 🤡🤡搭配每日签到送流量(永久)活动,更香甜! 🗓 关注@Yuntuvpnbot 每日签到送200MB~2000MB流量 🔼🔼🔼 来自后知后觉的双11活动,等友商卖完先!
👍11❤3
Signed Channel Help
#系统公告 近期大环境多变,为提供更长久稳定的服务,即日起启用账号风控防火墙,系统自动识别、触碰红线自动封禁,请大家谅解并配合: 1、禁止使用国内云服务器访问平台(阿里云、腾讯云、华为云等境内厂商及机房 IP 一律拦截); 2、禁止通过即时通讯工具传播订阅信息(微信群、QQ 群、TG 群、公开频道等请勿转发订阅链接、节点、邀请码); 3、禁止键政、邪教邪修、儿童色情等违反国际法的使用(直接永久封禁,不退款,保留上报权利)。 另请避免账号共享转售、批量注册、扫描爆破等影响平台稳定的行为。 规则越清楚,服务越长久。感谢理解与配合。 注册协议详情:https://yuntu.sbs/#/docs/15
❤66👍11🔥2😁2
Signed Channel Help
#系统公告 📌尊敬的用户: ‼️此前,因部分地区运营商对客户端 API 实施了网络阻断,导致部分用户在登录及使用过程中出现查询后端、请求异常等情况。 目前该问题已修复完成,各项服务已全面恢复正常,您可正常使用全部功能。 💎对于此次故障给您带来的不便,我们深表歉意,并作出如下补偿: 一、全体用户账户有效时长统一延长 3️⃣天,系统已自动发放,无需任何操作。 二、不限时长用户额外补偿 5️⃣🔤🔤 流量,同样已自动到账,无需联系客服领取。 如有其他疑问,也欢迎随时联系客服协助处理。 感谢您的理解与支持! 2026 年 9 月 16 日
❤26👍4😁1
Signed Channel Help
#优惠活动 📌适用套餐:普及版 *原价16.8/月/100G,现价8.4元 *原价33/月/200GB,现价16元 💎优惠码:0901(仅限月付套餐📌) 👀活动时间:8月3日~8月9日有效 ‼️注意事项:已有套餐用户变更套餐会自动覆盖原套餐! 活动结束 @yuntuvpnbot 机器人签到赠送200MB~2GB流量👀 ↑↑↑搭配不限时套餐食用,口味更佳!‼️ 注册免费24小时试用,仅可试用部分【直连节点】👀
❤85👍1
Signed Channel Help
鉴于高危漏洞 CVE-2026-53359 影响广泛,我们将加固所有虚拟化系统,并重启修复。 已升级修复!✅
❤11
#官方公告 📢 关于刚才服务中断的说明及补偿 由于短时间内大量用户同时更新客户端,导致订阅更新和节点同步服务出现拥堵,中断约10分钟,给您带来不便,深表歉意! 🎁 补偿方案(已自动发放,无需联系客服) 时长套餐用户:赠送 1天 服务时长 不限时流量用户:赠送 5GB 流量 ✅ 补偿已直接到账,请留意账户变动。 感谢大家的理解与支持!
❤47🔥1🥰1
Signed Channel Help
Posted without readable text
❤12
⚠️ 【重要公告】赌博模式流量异常 & 补偿说明 由于 Telegram 官方功能异常,导致签到机器人 @yuntuvpnbot 的赌博模式流量成倍数增加。 📌 处理方案 近一周内通过赌博模式(老虎机、骰子类)参与获得的流量,平台已进行数据回滚(扣除异常增加的流量) 🎁 受回滚影响的用户,可联系客服免费领取 200G 不限时流量(每位用户限领一次) 🎉 额外福利说明 若您的账户未被执行数据回滚,则无需联系客服,该部分流量将自动作为免费福利赠送给您。 📞 需要领取 200G 补偿的用户,请联系在线客服或提交工单,提供账号信息+游戏截图即可。 不符合要求或者没受影响的别联系客服了,送不过来了。 对此造成的不便,我们深表歉意!感谢大家的理解与支持。 💋新注册用户免费赠送60分钟体验活动同步进行中(仅部分节点)
❤38
Signed ToT
#官方公告 为提升连接稳定性与协议兼容性,我们已对所有客户端进行版本更新。 🔔 请务必按以下步骤操作: 1️⃣先卸载 当前已安装的老版本客户端(包括残留配置) 2️⃣ 再下载 最新版本客户端(官网 / 频道置顶获取) 3️⃣重新安装 后导入订阅 / 配置文件即可正常使用 🙂支持平台:Windows / macOS / Android / iOS / (各平台均已同步更新) ❌不要尝试覆盖安装,否则可能导致配置冲突或协议不兼容。 【移动用户网络波动提醒】 ⛔️今日移动用户全网波动较大,此现象非本平台原因。如遇连接异常,建议暂时更换其他运营商网络(电信/联通)以获得更稳定的体验。 感谢您的配合!如有问题请联系在线客服或提交工单。
❤30👍2😁1
Signed Channel Help
#官方公告 鉴于近期形势日益严峻,以及三网优化专线中转的高成本压力,为保障平台长期稳定运营,我们将进行以下调整: ▎套餐及权益调整 ● 基本套餐上涨🔼20%(几乎保本销售) ● 所有低价套餐即日起同步下架,不再对新用户开放 ● @yuntuvpnbot 每日签到免费流量改为500MB~3GB ━━━━━━━━━━━━━━━━━ ▎SLA保障 🤩 电信 CN2 GIA / CN2 双栈热备 🤩 联通 9929 / 4837 毫秒级调度 🤩 移动 CMI / CMIN2 跨境直连加速 🛡 多节点BGP智能调度 + 冗余架构 🚩敏感时期,稳定如常 ━━━━━━━━━━━━━━━━━ 本次调整后售价已趋近于成本边缘,属于微利/保本状态。 感谢理解与支持!👀
❤36
Signed Channel Help
#官方公告 【流量异常通知】签到机器人故障 由于签到机器人 @yuntuvpnbot 出现异常,导致部分用户被误扣流量,对此我们深表歉意。 🛡处理方式 请受影响用户联系在线客服,提供您的账号信息,我们将为您补回被扣流量。 💎 如在线客服未及时回复 请提交服务工单(官网 → 服务工单 → 提交新工单),后台将在 1 小时内响应 并为您处理。 感谢您的理解与支持!⭐️
❤3
Signed Channel Help
Showing the 12 most recent of 24 posts we hold for @soso_vpn. 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.
@soso_vpn edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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.
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 19 November 2026 — this entry's latest reading, not the date you are reading this.
“🥇官方合作VPN-每日签到送” (@soso_vpn), 14,166 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/soso_vpn.
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.