Telegram RegisterThe public register of Telegram
Telegram profile photo for 云海Emby 公告板

Channel

云海Emby 公告板

@oceancloudemby

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

15,057subscribers

+1,560 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
TypeChannel
Username@oceancloudemby
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/oceancloudemby

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 44% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

13,49715,06514,28115,0577 August 202611 November 2026
62 measurements spanning 96 days, net +1,560. 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 13,262–15,300 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
11 Nov 2026, 06:3915,057+1
9 Nov 2026, 11:1115,056+16
8 Nov 2026, 01:2915,040+52
7 Nov 2026, 02:0914,988+93
6 Nov 2026, 00:5914,895-11
5 Nov 2026, 04:2114,906+12
4 Nov 2026, 00:4014,894+37
2 Nov 2026, 21:0414,857+17
1 Nov 2026, 23:1814,840-1
1 Nov 2026, 02:3814,841+14
31 Oct 2026, 03:1114,827-15
29 Oct 2026, 23:3114,842-21
28 Oct 2026, 21:4914,863-16
27 Oct 2026, 22:5914,879-12
26 Oct 2026, 22:3814,891-18
25 Oct 2026, 21:0814,909-14
24 Oct 2026, 18:3814,923-9
23 Oct 2026, 20:1814,932-4
22 Oct 2026, 21:2714,936-14
21 Oct 2026, 18:2114,950first reading

Engagement

31 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 66 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.3%
avg views ÷ 15,057 subscribers
Avg views / post
2,310
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
2
of 31 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 October 2026
Posts held31 (27 November 2025 – 30 October 2026)
Views total4,610
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 07:01 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
2
Videos
1
Links
32

Lifetime counters from Telegram’s own channel header, read 11 November 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

Telegram’s own ‘edited’ marker: 1 of 2 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

30 Oct 2026, 08:12 UTC≈1,880 viewsread 11 November 2026

给全体成员的通知: 维护后看不了的都去重置密码

27 Oct 2026, 00:34 UTC≈2,730 viewsread 11 November 2026

【Emby 线路维护及补偿通知】 接上游机房通知,目前节点正处于计划内网络升级维护中,期间服务暂不可用。 🔹 维护时间:10月26日 23:00 – 10月28日 00:00 🔹 影响线路:Emby 双服线路 🔹 补偿方案:维护结束后将给所有有效用户自动补时长 3 天 维护完成后服务将自动恢复正常,对您造成的观影不便敬请谅解,感谢大家的耐心与支持! 已恢复,补偿稍后自动发放! 云海Mart

25 Sept 2026, 02:31 UTC≈4,890 viewsread 11 November 2026

🍂 赏花赏月赏中秋 云海团队祝您中秋快乐,阖家团圆。 在此我们献上全场可用8.8折优惠码: “2026中秋国庆快乐“ 点击前往 ➡ 云海Mart

24 Sept 2026, 12:03 UTC≈3,800 viewsread 11 November 2026

📢云海Mart 全新升级公告 我们已完成面板升级,现已开放以下新功能: 1.会员等级体系 普通会员:注册账号,享98折 银卡会员:充值满100元升级,享95折 金卡会员:充值满300元升级,享9折 钻石会员:充值满800元升级,享85折 折扣可用于云海Mart所有产品 2.分销商系统 云海Mart现已支持申请成为分销商,拥有独立站点与自主定价,差价即利润,订单由我们统一发货。 3. 推广返利 开启推广返利后,使用您的专属链接,邀请好友消费每笔订单可获得20%返利。 点击前往注册 ➡ 云海Mart 🏝 LAST CHANCE | 金秋限定盲盒余量 影视服盲盒剩余 白名单 3枚 双服白名单 1枚 成人服盲盒剩余 黄名单 1枚 双服白名单 1枚 点击前往下单 ➡ 云海Mart

23 Sept 2026, 09:00 UTC≈3,090 viewsread 11 November 2026

通知: 🚨 【紧急提醒】请立即核销手中的注册码/续费码! 因发卡平台遭遇突发攻击与系统异常,未使用的卡密数据可能会提前失效。 手里目前还有 囤码、未激活注册码、未充值续费码 的同学,请立刻、马上去Bot里兑换使用,避免造成资产损失! 遇到任何兑换报错,请保留订单截图并私聊管理反馈。收到请互相转告!

11 Sept 2026, 15:36 UTC≈5,940 viewsread 11 November 2026
Photo

📢 云海 Emby × Rex|入库通知正式接入 只需在Rex中添加云海入库口令, 即可实时接收最新影视入库通知。 🌊 云海入库口令: ⁠云海emby ━━━━━━━━━━━━━━ 🎬 入库后会发生什么? 当你追更的剧集或关注的新片成功入库后, Rex将第一时间推送通知。 🔔 新片入库 → 实时提醒 🎞️ 点击通知 → 直达播放 让入库通知更及时, 让每一次追更都不再错过。 ━━━━━━━━━━━━━━ 🌊 漫游云海,光影随行。

9 Sept 2026, 04:10 UTC≈4,640 viewsread 11 November 2026

🍂 金秋将至,微风渐凉 「金秋限定」盲盒现已上架 点击前往 云海Mart

25 Aug 2026, 13:25 UTC737 viewsread 26 August 2026

机器人: 影视服 @oceancloudemby_bot 成人服 @oceancloudnsfwemby_bot

25 Aug 2026, 13:24 UTC755 viewsread 26 August 2026

🎯 oceancloudnsfwemby_bot已为您生成了 7天 注册码 50 个 云海互联-7-Register_FhAlkJQvJ7 云海互联-7-Register_MLr74eFBbE 云海互联-7-Register_wM9s9XzeRO 云海互联-7-Register_zWtCzYaF43 云海互联-7-Register_2Fi4WrkM02 云海互联-7-Register_rWqSnjHNLS 云海互联-7-Register_9saZ3J3Wtc 云海互联-7-Register_fj9QtS6Olh 云海互联-7-Register_WtJhYbpsJJ 云海互联-7-Register_kFTdECbemr 云海互联-7-Register_kQbltAxeXy 云海互联-7-Register_qCiSfqN8VT 云海互联-7-Register_CKzrBdeEfS 云海互联-7-Register_q7OIqG9lG…

25 Aug 2026, 13:23 UTC710 viewsread 26 August 2026

🎯 oceancloudemby_bot已为您生成了 7天 注册码 50 个 云海互联-7-Register_8l8peF8oNF 云海互联-7-Register_tqGqQktlxG 云海互联-7-Register_tsBYUluvU5 云海互联-7-Register_cdXQBJ3Lb6 云海互联-7-Register_ftb2arUgsZ 云海互联-7-Register_0oDOV7VPmE 云海互联-7-Register_XRQx5khuV6 云海互联-7-Register_WEwK2aahoA 云海互联-7-Register_ibSOcSoajU 云海互联-7-Register_j5kBVxEhBV 云海互联-7-Register_BIPjooeYEI 云海互联-7-Register_pgQoTg3i63 云海互联-7-Register_n0Yj2e203s 云海互联-7-Register_XvtlZNHwod 云海…

12 Jul 2026, 04:29 UTC≈10,200 viewsread 11 November 2026

🏝 LAST CHANCE | 盲盒余量 1️⃣ 「冰爽盲盒」影视 — 最后 0 枚 双服白名单 2️⃣ 「冒险盲盒」成人 — 最后 0 枚 黄名单 3️⃣ 「传奇盲盒」成人 — 最后 0 枚 黄名单 4️⃣ 「隐藏盲盒」成人 — 最后 0 枚 黄名单 💡 名额实时扣减,不设口头预留。 点击前往 ➡️云海Mart

Showing the 12 most recent of 31 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.

Posts edited after publishing

@oceancloudemby edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
27 August 2026
Most recent edit
27 August 2026

Posts recorded as deleted after publishing

We recorded 4 posts on @oceancloudemby as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
13 August 2026
Most recent seen missing
25 August 2026
Median time before seen missing
9 days
Seen missing in the last 30 days
0

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.

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

“云海Emby 公告板” (@oceancloudemby), 15,057 subscribers as measured 11 November 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.