大家觉得好用可以推荐一下给朋友,朋友购买套餐你也将获得一份相同套餐

Channel
顺网加速官方频道
@ShunWangcc
On this record: Growth · Engagement · Posts · Citations · Cite this entry
315subscribers
-110 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003909544828 |
|---|---|
| Type | Channel |
| Username | @ShunWangcc |
| Created | Between 1 April 2026 and 13 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/ShunWangcc |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 12:42 | 315 | -50 |
| 3 Sept 2026, 10:06 | 365 | -17 |
| 27 Aug 2026, 18:24 | 382 | -26 |
| 20 Aug 2026, 06:48 | 408 | -15 |
| 12 Aug 2026, 15:14 | 423 | -2 |
| 11 Aug 2026, 16:45 | 425 | no change |
| 11 Aug 2026, 16:32 | 425 | first reading |
Engagement
20 posts held, back to 13 June 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 1 page 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
机器人不可用,大家请在官网购买订阅
swgw.swhulian.cc
现在完全已经恢复使用,网站可以恢复下单订阅,之前买了用不了的记得联系客服
因上一个服务器被封,数据库丢失,大家如果用不了以后重新在swgw.swhulian.cc注册,凭套餐剩余截图,补录数据,并且个人都将延长10天使用时间
买的月付套餐的朋友记得续费哦,到期了来问我怎么用不了,你没续费当然用不了啊
新的官网 swgw.swhulian.cc
其中一个节点用不了的一般是该节点流量没了,大家刷新更换新节点就可以继续用了,我们会不定期添加新的节点
新增6个节点,刷新订阅即可用
已恢复
异常问题已修复 所有异常问题已修复,机器人数据库也已恢复,请重新获取新的节点列表。
新的官网 guanwang.shunwanghulian.cc
Showing the 12 most recent of 20 posts we hold for @ShunWangcc. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“顺网加速官方频道” (@ShunWangcc), 315 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/ShunWangcc.
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.