🎯 oceancloudnsfwemby_bot已为您生成了 7天 注册码 30 个 云海互联-7-Register_PPaA0MpTkE 云海互联-7-Register_4mluyfvvYk 云海互联-7-Register_vb5S7PoXXl 云海互联-7-Register_AMCIN5Suux 云海互联-7-Register_RtxxjoeWsP 云海互联-7-Register_mmRmXk9seu 云海互联-7-Register_ze00ekBhjJ 云海互联-7-Register_g5CQVy3ZZU 云海互联-7-Register_C9Fxj7C3k1 云海互联-7-Register_WK2YhPXnvG 云海互联-7-Register_xzzHB90yeB 云海互联-7-Register_IG3jqZVLvP 云海互联-7-Register_N0ups7u3Ux 云海互联-7-Register_zyct6LazJ…

Channel
云海Emby 公告板
@oceancloudemby
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
13,582subscribers
+85 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002377752104 |
|---|---|
| Type | Channel |
| Username | @oceancloudemby |
| 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 | 12 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/oceancloudemby |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:58 | 13,582 | +22 |
| 11 Aug 2026, 18:45 | 13,560 | +12 |
| 10 Aug 2026, 19:12 | 13,548 | +2 |
| 9 Aug 2026, 21:12 | 13,546 | +22 |
| 8 Aug 2026, 19:21 | 13,524 | +27 |
| 7 Aug 2026, 19:27 | 13,497 | no change |
| 7 Aug 2026, 17:16 | 13,497 | first reading |
Engagement
22 posts held, back to 27 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 10.8%
- avg views ÷ 13,582 subscribers
- Avg views / post
- 1,470
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 22 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 7 August 2026 |
|---|---|
| Posts held | 22 (27 November 2025 – 7 August 2026) |
| Views total | 2,940 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 02:31 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.
What this channel posts
- Photos
- 1
- Videos
- 1
- Links
- 28
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
🎯 oceancloudemby_bot已为您生成了 7天 注册码 30 个 云海互联-7-Register_dsyCMmYdDf 云海互联-7-Register_UQnovrhYuZ 云海互联-7-Register_M6NXEd0ekw 云海互联-7-Register_1Thvmbo7rx 云海互联-7-Register_e2Oi2oXt9n 云海互联-7-Register_GjxGav03kq 云海互联-7-Register_LwiTby9i2i 云海互联-7-Register_A4JupsQE1d 云海互联-7-Register_YnnRAhYfpC 云海互联-7-Register_LPfke0N4N5 云海互联-7-Register_kM9yaYzkah 云海互联-7-Register_OBWzJa3Av9 云海互联-7-Register_dGFOhx8oTm 云海互联-7-Register_x8FNRWtTT9 云海…
🏝 LAST CHANCE | 盲盒余量 1️⃣ 「冰爽盲盒」影视 — 最后 1 枚 双服白名单 2️⃣ 「冒险盲盒」成人 — 最后 1 枚 黄名单 3️⃣ 「传奇盲盒」成人 — 最后 3 枚 黄名单 4️⃣ 「隐藏盲盒」成人 — 最后 7 枚 黄名单 💡 名额实时扣减,不设口头预留。 点击前往 ➡️云海Mart
🏝 夏日特卖 · 限时优惠 🎁 全场盲盒/续期码 统一半价 🔑 白/黄名单 限时价 ¥299 🌐 双服名单 特惠仅 ¥499 ⚡️ 数量有限,售完恢复原价! 点击前往 ➡️云海Mart 🔤🔤🔤🔤🔤 🔤🔤🔤🔤🔤
碧绿粽叶裹思念,艾香袅袅祈平安 🎋 各位频道的小伙伴们,今天端午节啦! 在这里真诚地祝大家:端午安康,诸事顺遂! 愿你: 剥开生活,全都是“粽”情欢笑 ☀️ 奔赴远方,能够“粽”横驰骋 🚀 日子过得有滋有味,平安喜乐,百病不侵! 今天记得吃粽子呀!
云海专属求片助手正式上线:@yunhaiqp_bot
🐎✨正月初五 · 迎财神✨🐎 金马踏财来,瑞气满门开。 今日迎财神,福禄滚滚至。 正月初五接财神,🍰🍰🍰 愿大家新岁一路生花,马上有钱,马上好运,马上成功!
🎆祝大家新年快乐🎆
🧧 2026 马年限定|「金马贺岁」盲盒 🎉 策马踏云海,除夕博头彩 云海年度压轴盲盒正式开启,陪你守岁迎新! 「金马贺岁」盲盒 🤩 本轮盲盒 · 除夕限量发售 💰 ¥18.88 / 个 🏆 双服全通白名单各 1 个 (价值¥998) 👑 白/黄名单资格各 3 个 (价值¥499) 🎬 365 天续期码各 12 个 🎬 180 天续期码各 30 个 🎬 90 天续期码各 54 个 🎬 30 天续期码各 100 个 (保底不走空) 🛡 非酋护航: 连抽 10 发全是 30/90 天? 凭订单截图找客服补发 180 天续期码! 🍾 「金马贺岁」盲盒入口 👉 影视服 👉 成人服 🎟 限时抢购 — 白名单/黄名单/双服白名单 ✨ 白名单:原价 ¥499 → 限时 ¥399 ✨ 黄名单:原价 ¥499 → 限时 ¥399 ✨ 双服白名单:原价 ¥998 → 限时 ¥699 👉 云海Mart ✨ 云海团队恭祝您: 新的一年
云海Emby 公告板 pinned Deleted message
🎉 春节快乐 · 限时特惠 祝大家2026年春节快乐~ DS One(原DS Cloud)现在限时促销 原价 ¥68,现仅需 ¥48 🎁 --- 无论是管理群晖 NAS,还是阖家一起看电影、独自沉浸音乐、听有声书,读电子书 一个应用搞定 Emby、Jellyfin、115 网盘、AudioStation、Navidrome、AudioBookShelf、Kavita! --- 👉 折扣仅限春节期间,别错过! 🌐 下载地址:点击下载 📢 更新推送频道:点这里 💬 用户交流群:加入讨论
云海Emby 公告板 pinned Deleted message
Showing the 12 most recent of 22 posts we hold for @oceancloudemby. 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.
Citation-graph rank
Citation-graph rank — 853,173 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 2 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“云海Emby 公告板” (@oceancloudemby), 13,582 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/oceancloudemby.
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.