Telegram RegisterThe public register of Telegram
Telegram profile photo for YuShe Official 🔔

Channel

YuShe Official 🔔

@Yushe_Official

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

1,372subscribers

+35 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-1001904596303
TypeChannel
Username@Yushe_Official
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/Yushe_Official

Growth

1,3361,3721,3547 August 2026 — 1,337 subscribers7 August 2026 — 1,337 subscribers8 August 2026 — 1,336 subscribers11 August 2026 — 1,341 subscribers14 August 2026 — 1,346 subscribers17 August 2026 — 1,352 subscribers21 August 2026 — 1,356 subscribers25 August 2026 — 1,355 subscribers27 August 2026 — 1,358 subscribers30 August 2026 — 1,355 subscribers2 September 2026 — 1,359 subscribers6 September 2026 — 1,360 subscribers11 September 2026 — 1,367 subscribers15 September 2026 — 1,372 subscribers7 August 202615 September 2026
14 measurements spanning 38 days, net +35. 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 1,331–1,377 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 00:571,372+5
11 Sept 2026, 10:171,367+7
6 Sept 2026, 16:171,360+1
2 Sept 2026, 05:331,359+4
30 Aug 2026, 15:361,355-3
27 Aug 2026, 23:031,358+3
25 Aug 2026, 00:031,355-1
21 Aug 2026, 00:411,356+4
17 Aug 2026, 16:261,352+6
14 Aug 2026, 20:391,346+5
11 Aug 2026, 07:151,341+5
8 Aug 2026, 08:111,336-1
7 Aug 2026, 22:231,337no change
7 Aug 2026, 14:401,337first reading

Engagement

20 posts held, back to 24 December 2024the 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 25 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

219 reactions across 16 posts, in 12 distinct kinds. The most used accounts for 37.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😭8137.0%
6831.1%
🥰2210.0%
👍156.85%
👏104.57%
🔥83.65%
🕊52.28%
🤡41.83%
💘20.913%
😁20.913%
🐳10.457%
🤓10.457%

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 17 of the 20 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 219 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 24 December 2024 to 25 May 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

25 May 2026, 08:04 UTC≈2,490 views4 reactionsread 7 August 2026

主站域名更换通知: 2026/5/25 15:00 原主站域名 my.yushe.org 已经被污染(已做301重定向) 已经切换到新域名: https://www.yushe.org 点我打开官网

2👏2

21 May 2026, 16:10 UTC≈2,280 views1 reactionsread 7 August 2026
Photo

恢复通知: 2026/5/21 22:12 因上游国内机房部署了最新的傲盾跨境流量检测系统 原SS2022协议已经被禁止使用 为确保服务不中断,我们已经将节点协议升级为AnyTLS 您必须切换至官网教程中指定的代理软件使用。 旧版或第三方软件将无法适配新架构。 您需要按照 官网教程 的步骤重新导入一次订阅,非常抱歉 之后会下发补偿:重置所有在有效期内的用户已用流量 (2026/5/23 18:29 补偿已经下发,所有用户流量已经重置)

1

21 May 2026, 12:08 UTC≈1,690 views0 reactionsread 7 August 2026

故障通知: 2026/5/21 20:05 入口服务器被北京网信办通报,正在更换节点协议中... 等待更换完成之后您需要重新导入一次订阅

13 Apr 2026, 23:10 UTC≈3,050 views3 reactionsread 7 August 2026

通知: 目前 SS 协议节点已经恢复成功,但是升级到了SS-2022 协议 如果您的客户端不支持 SS-2022 协议的话则不会显示可用节点 请您去官网的教程文档里面下载 Clash verge,Clash Meta For Android,Shadowrocket 使用 Tip: 所有节点已经更新完成,您需要重新导入一次订阅链接 由于上游要求国内入口不能通报,5分钟临时订阅机制已经重新开启 导入时请注意时间,超时请刷新网页重新复制最新的订阅链接

2👍1

8 Apr 2026, 16:52 UTC≈3,080 views2 reactionsread 7 August 2026

通知: 从 2026/4/8 晚上接到2个上游的通知 所有国内入口将会拔线,联通入口也将命不久矣 目前节点已经从 SS协议 换成了 Vless直连协议,电信体验会有点差 正在想办法优化 由于更换了节点的协议,很多客户端不支持新协议,因为不支持所以不会显示可用节点 请到官网的教程文档里面下载通用客户端:Clash Verge 或者小火箭使用 如果已经是上述客户端依旧不能使用的话请重新导入一次订阅 (目前已经关闭动态订阅策略,因为没必要了...)

2

28 Feb 2026, 12:15 UTC≈3,690 views15 reactionsread 7 August 2026

通知: 由于国内入口通报情况日益严重(2天通报4次) 我们已经启动了订阅 5分钟 有效期 的策略 来缓解通报速度 您需要重新导入一次订阅 请您确保自己在5分钟内成功导入订阅,如果未成功请刷新页面后重新获取订阅导入 当导入成功之后,在节点没有大规模失效的时候无需更新订阅 如果您不想每次更新订阅,可以使用教程文档中的一键客户端(可以无感刷新订阅) 非常抱歉对使用体验造成严重破坏,但是没有更好的办法了

👏7🤡43🤓1

15 Feb 2026, 00:31 UTC≈4,680 views14 reactionsread 7 August 2026

辞旧迎新,万马奔腾!🧨 祝大家新的一年,事业马到成功,生活龙马精神! 为了感谢你们的陪伴,也为了给你们的马年开一个好头,我们特意准备了一份新春薄礼: 🚀 全场套餐限时 75 折!(25% OFF) 新春快乐!2026 马年专属福利已送达 🐎 🧧 优惠码: Horse (结账时输入,立享折扣) 📅 活动时间: 2026/02/15 00:00 ~ 2026/02/20 23:59 愿你在新的一年,依旧能在这个互联的世界里自由呼吸,极速穿梭

🔥8💘2😁2🐳1🥰1

31 Jul 2025, 22:12 UTC≈6,730 views10 reactionsread 7 August 2026

通知: 月初节点入口有些变动,具体如下 🇭🇰 香港 0.1x -> 广州移动 🇲🇴 澳门 0.1x -> 广州移动 🇭🇰 香港 01,02 -> 佛山移动 🇭🇰 香港 03,04 -> 三线IEPL 🇹🇼 台湾 01,02 -> 佛山移动 🇸🇬 狮城 01,02 -> 佛山移动 🇯🇵 日本 01,02 -> 佛山移动 🇺🇸 美国 01,02 -> 上海联通 🇨🇦 加拿大 01,02 -> 上海联通 🇰🇷 韩国01 -> 福州联通 🇹🇭 泰国01 -> 福州联通 🇬🇧 英国01 -> 福州联通 🇩🇪 德国01 -> 福州联通 您可以选择距离自己较近且运营商相同的入口使用 体验可能会更加优异 以上入口均有跨网跨省优化

9🥰1

13 Jul 2025, 10:20 UTC≈5,280 views17 reactionsread 7 August 2026

通知: 鉴于目前通报过多的情况,已经做出如下改动 新增香港,台湾,新加坡,日本 4个地区的直连节点 节点标识为: DC 节点倍率为: 0.1倍 节点协议为: Vmess+ws+tls 目前不知道多久会墙一次IP,所以还在测试阶段 等有个大概心理预期之后会上线自动更换IP的脚本,保证节点的可用性 也有做灾备节点的意思,防止全线断联导致失联 然后就是预计会 下线 2个国内中转的香港0.1倍率节点 因为只能减少入口来减少通报带来的损失 以上是本次所有更新内容 需要刷新一次订阅才能使用新的节点哦!~

16👍1

1 Jul 2025, 07:59 UTC≈4,510 views113 reactionsread 7 August 2026

一些碎碎念: 刚刚在Crisp被骂了(就是网站右下角的在线客服) 说我是垃圾机场,坑钱,还对我进行人身攻击 说实话挺难受的 我自认为在我能力范围内我已经做到了最好了 我也确实没有通过机场盈利很多(亏得挺多 上个月一共流水3w2623块钱 6台入口花费了3w9500块钱 每天的AWS出口费用是200块钱,一个月差不多6000块钱 还支出了几百块钱佣金 落地机器和一些杂七杂八的费用也有五六千块钱了 我真的燃尽了 我确实没有别的机场主那样的非常优质的资源 如果有的话,你们知道的,我肯定会给你们用上 我也不想我的钱花了,但是大家体验都不好 可是现在各大运营商相互QOS,我这种没有资金没有用户的小机场确实吃不消 如果大家觉得不好用的话,请默默不续费就好了 是我太玻璃心了,你的一句很卡我确实会难受很久

😭8119🥰8🕊5

30 Jun 2025, 19:59 UTC≈2,980 views5 reactionsread 7 August 2026

通知: 原本说好的专线因为一些不可抗力的原因,终究还是没落实下来 确实有努力过了,但是内网传输很诡异的一直出问题,没有一点办法解决 再一方面考虑到电信用户也不少 所以我们把原有的深圳移动和广州移动更换到了如下机器 几乎没有跨网的 广州移动 没有跨网和跨省的 上海移动 这代表电信用户的体验会好非常多 然后我们增加了公网出口机器的容量 需要1号晚高峰再看看节点状态再做判断(不够会继续加) 这是目前所有的变动 如遇节点不通,请尝试更新订阅

5

4 Jun 2025, 21:40 UTC≈3,480 viewsread 7 August 2026

通知: 香港1,2 台湾1,2 节点的原 苏州移动 入口已经替换成了 安徽移动 因为实在是太难用了,而且故障率也挺高 更换后的安徽移动QOS等级更高,体验会更好一点 原苏州移动已经加入日美节点负载 移动网络使用日美节点会通过DNS解析智能分流到原苏州移动入口 然后还有一件事情,就是 cp.yushe.org 没有挺过这次6.4域名大污染,已经炸缸了 新域名: https://my.yushe.org 新域名也会在发布页进行更新 请关注收藏YuShe的发布页: https://home.yushe.org

Showing the 12 most recent of 20 posts we hold for @Yushe_Official. 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Duyao|SpeedTest|科技生活|资讯转发
@DuyaoSS · 67,787
Telegram ranks this channel #18 of 45 here — alongside 44 others — read 20 August 2026
科学上网观察与机场测速
@jichangtj · 134,086
Telegram ranks this channel #35 of 54 here — alongside 53 others — read 15 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“YuShe Official 🔔” (@Yushe_Official), 1,372 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Yushe_Official.

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.