ultra/pro/海外服 Emby账号到期后删除Emby账号时间修改: 账号到期停用 5 天后删除已停用的 Emby账号 修改为: 账号到期停用 14 天后删除已停用的 Emby账号 若您的账号已停用并被删除,请新增Emby账号
❤3

Channel
@mooguudepindao
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
4,203subscribers
+1,496 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002475833553 |
|---|---|
| Type | Channel |
| Username | @mooguudepindao |
| 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 | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/mooguudepindao |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 05:41 | 4,203 | +99 |
| 14 Sept 2026, 08:19 | 4,104 | +142 |
| 10 Sept 2026, 07:19 | 3,962 | +175 |
| 5 Sept 2026, 07:18 | 3,787 | +111 |
| 1 Sept 2026, 01:08 | 3,676 | +66 |
| 29 Aug 2026, 07:34 | 3,610 | +151 |
| 25 Aug 2026, 21:03 | 3,459 | +147 |
| 22 Aug 2026, 17:56 | 3,312 | +173 |
| 19 Aug 2026, 04:02 | 3,139 | +140 |
| 15 Aug 2026, 17:45 | 2,999 | +142 |
| 12 Aug 2026, 00:32 | 2,857 | +111 |
| 8 Aug 2026, 16:38 | 2,746 | +39 |
| 7 Aug 2026, 17:32 | 2,707 | no change |
| 7 Aug 2026, 17:25 | 2,707 | first reading |
20 posts held, back to 15 February 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 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 26 July 2026. An engagement rate over an empty window would be a number about nothing.
117 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 90.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 106 | 90.6% | |
| 👍 | 10 | 8.55% | |
| 🗿 | 1 | 0.855% |
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 15 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 117 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 15 February 2026 to 26 July 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.
ultra/pro/海外服 Emby账号到期后删除Emby账号时间修改: 账号到期停用 5 天后删除已停用的 Emby账号 修改为: 账号到期停用 14 天后删除已停用的 Emby账号 若您的账号已停用并被删除,请新增Emby账号
❤3
维护完成通知: ✔️ 海外服和公益服 已完成维护,现可以正常使用 ✔️ 海外服用户双倍时长补偿已全部下发到账户,在原有补偿的基础上,我们还赠送了2天。在维护期间到期的用户,可以联系客服启用账号补偿时间。白名单没有补偿,主要是因为没有好的补偿方案,其次,白名单涨价也没有让存量白名单补差价不是,非常感谢白名单用户的支持
Ultra和pro 服 23:30停机维护,维护时长约3小时 公费和公益服预计今晚-明天恢复
维护通知: 海外服,硬盘集群换盘维护,优化播放体验。7月1日开始维护,维护时间约7天 Ultra/Pro不受影响 Ultra/Pro不受影响 Ultra/Pro不受影响 📺维护完成后 双倍 时长补偿 感谢理解
👍3
最近海外服和见手青业务有点调整,服务器换硬盘,存储需要做数据备份,更新和观看有些受影响 所以海外服从中断服务计时,维护完成后双倍补偿时长。大约需要4-5天时间。
海外服和见手青晚22:30开始维护,维护期间速度可能比较慢,到凌晨
📺📺📺蘑菇端午促销活动📺📺📺 蘑菇祝所有用户端午安康 端午通用促销折扣码: mgdwzk8zk 除白名单和试用外,ultra,pro,海外服均可用
❤16👍1
部分联通用户有点卡,22:00 业务不中断维护10分钟,正在播放的不受影响~ 维护完成
📦 海外媒体资源共享计划 已有: ✅ 蘑菇全量影视资源 ✅ 海外高速对象存储 ✅ 大带宽出口 ✅ 稳定直链访问 支持: Emby / Jellyfin / Plex STRM 挂载 / 资源分发 / 存储租赁 面向服主开放合作 🤝 需要资源、带宽、存储的欢迎联系。 官网: https://mooguu.net 共享服务:https://mh.mooguu.net 定制/支持联系: @mogu_ch_bot
❤4
蘑菇 Ultra & Pro & 海外服 五一钜惠 限时8折 统一折扣码: mooguu51-8
❤8
蘑菇海外服(公费)升级上线通知 蘑菇公费升级为海外硬盘服,无国内线路优化,需自行翻墙使用。 优化线路推荐使用Ultra或者pro服(https://mooguu.net) 网址:蘑菇海外服账号管理网站https://wf.mooguu.net miniapp(机器人): @mooguu_wf_bot 蘑菇群组: @mooguu_group1 本次升级带来: ·资源扩充,与国内优化线路资源同步更新; ·网盘切硬盘,畅享秒开秒播;码率整体升级; ·带宽升级,20G服务带宽,速度取决于您的海外网络环境。 网址:https://wf.mooguu.net miniapp(机器人): @mooguu_wf_bot 老用户使用指南: 1、 进入网站,并注册用户名、邮箱,如果您无法过人机验证,请更换干净的网络节点,蘑菇不对网络环境进行支持。 2、 首页点击绑定原账号,或者进入菜单-我到账号-绑定原账号 (不要点击购买或创建试用账号…
❤10👍6
蘑菇硬盘上两个折扣码,统统85折 ultra: mooguu2026-ultra-4 pro: mooguu85-pro-4
❤8
Showing the 12 most recent of 20 posts we hold for @mooguudepindao. 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 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.
@mooguudepindao named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“蘑菇emby通知频道” (@mooguudepindao), 4,203 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/mooguudepindao.
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.