近期部分节点掉线不稳定 已暂时优化调整 请大家更新订阅使用 后续将进一步优化线路质量与连接稳定性,带来更流畅、更高效的网络体验。
Signed shark

Channel
@shayumeow
On this record: Growth · Engagement · Posts · Citations · Cite this entry
131subscribers
+85 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002197973670 |
|---|---|
| Type | Channel |
| Username | @shayumeow |
| Created | 18 August 2024 — measured — dated from the channel’s first post |
| First recorded | 20 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/shayumeow |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 03:58 | 131 | +6 |
| 4 Sept 2026, 14:41 | 125 | +17 |
| 27 Aug 2026, 14:18 | 108 | +53 |
| 20 Aug 2026, 13:24 | 55 | +9 |
| 20 Aug 2026, 06:15 | 46 | first reading |
6 posts held, back to 18 August 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 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 6 posts for this entry, the most recent from 18 July 2026. An engagement rate over an empty window would be a number about nothing.
近期部分节点掉线不稳定 已暂时优化调整 请大家更新订阅使用 后续将进一步优化线路质量与连接稳定性,带来更流畅、更高效的网络体验。
Signed shark
部分用户运营商网络DNS节点无法解析 导致节点全部超时无法测速 已下发新的订阅配置使用公共DNS解析 有问题的更新订阅即可 节点全部优化更新协议 使用动态家宽住宅ISP原生IP支持流媒体 动态家宽住宅每天都会自动更换新的IP 添加了更多地区的节点 英国 法国 德国 泰国 印度 意大利 加拿大 乌克兰 挪威 瑞典 巴西 智利 波兰 多哥 捷克后续会添加更多冷门地区节点 需购买更高级订阅解锁
Signed shark
鲨鱼官方客户端已更新可前往官网下载
Signed shark
鲨鱼丨不限速不限流量,视频图片秒加载,安心服务,超低消费 官方网站:https://shayux.com 发布页:https://shayuovo.com(务必收藏) 频道小喇叭:https://t.me/shayumeow 🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀 现有香港,台湾,新加坡,日本,美国,英国,德国
Signed shark
Channel photo updated
Channel created
Showing the 6 most recent of 6 posts we hold for @shayumeow. 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.
Named by 3 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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“鲨鱼” (@shayumeow), 131 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/shayumeow.
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.