🥛为提高 白小兔Bot 的实用性,现已新增以下功能: 🥛Emby 自定义密码 Emby 账号现已支持修改为自定义密码,登录更加方便。 🥛重置订阅链接 向 Bot 发送: /restsub 即可重置当前订阅链接。重置后,原订阅链接将失效,请及时在客户端更新。 🥛流量透支 当本周期已用流量达到 95%,且套餐剩余时长 大于一个月 时,可提前开启下一个流量周期。 向 Bot 发送: /overdraft 按照提示确认后,即可提前重置流量。 🥛请注意:该操作相当于提前使用下一个周期的流量,同时会扣除一定的套餐时长,请确认后再进行操作。 🥛 联系人工客服 向 Bot 发送: /contact 确认后即可开启人工客服沟通渠道,支持发送文字、图片和视频,方便大家更高效地反馈问题。 (客服在线时会及时回复;如暂时不在线,待上线后会第一时间处理并回复,请耐心等待) [新国内直连官网][备用国内直连官网1][备用国内直连官网2]

Channel
兔子窝的通知
@Yztcloud_notification
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,783subscribers
+14 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 | -1002313235452 |
|---|---|
| Type | Channel |
| Username | @Yztcloud_notification |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Yztcloud_notification |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 03:14 | 1,783 | +6 |
| 11 Aug 2026, 07:25 | 1,777 | +7 |
| 8 Aug 2026, 08:28 | 1,770 | +1 |
| 7 Aug 2026, 20:49 | 1,769 | no change |
| 7 Aug 2026, 18:23 | 1,769 | first reading |
Engagement
13 posts held, back to 21 January 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 51.2%
- avg views ÷ 1,783 subscribers
- Avg views / post
- 913
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 13 held
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 31 July 2026 |
|---|---|
| Posts held | 13 (21 January 2026 – 31 July 2026) |
| Views total | 913 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 20:49 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.
Recent posts
🥛特色套餐上线 为满足不同用户的使用需求,我们新增上线以下三款特色套餐: 🥛家种萝卜 仅提供家宽节点 更适合AI、流媒体、社交平台及日常使用 69元/季|160GB流量 [前去购买] 🥛野生萝卜 仅提供冷门地区节点 满足特殊地区访问需求 59元/季|160GB流量 [前去购买] 🥛进口萝卜 适合海外用户使用 提供更优跨区域访问体验 16元/月|120GB流量 [前去购买] 🥛以上套餐现已正式上线,可前往官网购买。 ⚠️套餐所包含节点范围与常规套餐不同,请根据自身需求选择。 另:旧官网域名已被污染,即日启用新官网 [新国内直连官网][备用国内直连官网1][备用国内直连官网2]
柚子兔网络官方IOS客户端已上线TestFlight。登录官网后持有效订阅获取邀请。 无需外区ID,您只需要下载TestFlight后,通过官网公告或订阅管理页面中的IOS客户端下载按钮,输入您的APPLE ID,并点击邮箱中的邀请链接即可下载。我们会持续续期,可放心使用。 IOS客户端目前属于早期阶段,优先解决Bug。功能较少会慢慢补充。同时欢迎您分享宝贵的意见。
▶️Emby入库通知频道已上线 https://t.me/yztcloud_emby
📢【故障说明及处理通知】 由于数据库出现异常故障,导致部分数据发生回滚,目前已完成故障处理并恢复服务。 受影响用户可能出现以下情况: * 账号密码提示错误或无法登录; * 套餐到期时间、剩余时长显示不正确; * 当前计费周期内流量使用情况显示异常; * 其他与账户数据相关的异常情况。 我们正在对受影响数据进行核查和修复。如您发现账户信息存在异常,请及时提交工单,我们将根据实际情况进行处理。 对于此次故障给大家带来的不便,我们深表歉意,感谢大家的理解与支持。
🥛【重要通知】 近期因入口域名遭到监测及封锁,我们已完成订阅系统和节点协议升级 🥛1、订阅链接已重置 所有用户的订阅链接(Token)已重置。 请登录官网重新复制最新订阅链接,旧链接已失效。 🥛2、订阅方式调整 为降低订阅入口被识别和封锁的风险,订阅更新方式已调整: ⚠️您需要在10秒订阅两次才能导入订阅 第一次会固定失败,第二次才会正常获取订阅,这是正常设计,并非故障。 🥛3、节点协议升级 所有节点已统一切换至 AnyTLS 协议。 请使用支持 AnyTLS 的客户端,否则无法正常获取节点。 ❓如遇无法更新订阅或无法连接,请优先确认: ✅ 已使用新的订阅链接 ✅已连续更新两次订阅 ✅ 客户端支持 AnyTLS 协议 感谢理解与支持。 PC/Mac软件推荐: Clash Verge 点我去下载 Mihomo Party 点我去下载 安卓端软件推荐: FlClash 点我去下载 NekoBox 点我去下载 IOS…
▶️新增Emby涩涩服! 涩涩服已同步追新服所有用户,使用相同的邮箱和密码即可登陆观看 (涩涩服地址通过 白小兔bot 获得,如出现密码错误,请手动发送命令重置密码) 🥛目前柚子兔网络提供三个Emby服务器供用户使用 🥛柚子兔追新服: 有效用户需通过 白小兔bot 完成自助开号: 向 Bot 发送 /bind 并按提示完成订阅绑定; 成功绑定后发送 /embycreate 即可注册 Emby 账号 🥛柚子兔涩涩服: 有效用户需通过 白小兔bot 完成自助开号: 向 Bot 发送 /bind 并按提示完成订阅绑定; 成功绑定后发送 /embycreate 即可注册 Emby 账号 🥛周三晚资源服: 有效用户通过直接访问链接验证邮箱后进行使用 https://emby.zhousanwan.xyz 🥛服务说明: 此服务仅在所购套餐有效期内可用,到期自动失效! 禁止外泄Emby服务器地址及账号! 有任何使用上的问题请…
🥛关于套餐价格调整的公告 🥛由于近期线路、服务器、家宽节点成本持续上涨,现有价格体系已经难以长期支撑当前服务规模。为了保证后续服务质量,我们迫不得已对套餐价格进行调整。 🥛新价格将于今日生效 已购买套餐不会受到影响,仍可正常使用至到期。 后续的续费、重置流量、新购买等操作,将按照新价格执行。 🥛感谢大家一直以来的支持,我们会继续尽力提供稳定、长期、可持续的服务体验。 🥛有任何使用上的问题请加内部群反馈,本群只做中转使用 https://t.me/Yztcloud_notification/60
🥛柚子兔网络2026五一活动 🥛活动一: 全场套餐通用8折优惠券:五一快乐 🥛活动二: 活动期间支付通道限时免除手续费 活动时间:2026.05.01 00:00 - 2026.05.06 00:00 有任何使用上的问题请加内部群反馈,本群只做中转使用 https://t.me/Yztcloud_notification/60
🥛内部群开放通知! 🥛群链接获取途径: 白小兔bot 🥛操作步骤: 1、发送 /bind 并按提示完成绑定 示例:/bind https://sub.yztcloud.cc/getnodeinfo?token=xxxxxxxxxxxx 注意:/bind 和订阅链接之间需要有一个空格 2、绑定成功后,发送 /getinvatelink 即可获取群邀请链接 🥛注意事项: 生成的邀请链接仅可使用一次,请在 30 分钟内完成加群。 套餐到期超过 3 天后,将会被移出内部群。 重新购买订阅后,可再次申请加入。
🥛柚子兔网络2026春节活动 🥛活动一: 全场套餐8折优惠券:2026新年快乐 🥛活动二: 活动期间支付通道限时免除手续费 🥛活动三: 活动期间群内不定时举行抽奖 活动时间:2026.02.13 00:00 - 2026.02.24 00:00
File, posted without a caption
Showing the 12 most recent of 13 posts we hold for @Yztcloud_notification. 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
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“兔子窝的通知” (@Yztcloud_notification), 1,783 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Yztcloud_notification.
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.