Channel
@muguacloud
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
2,343subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001481061313 |
|---|---|
| Type | Channel |
| Username | @muguacloud |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 13 August 2026 |
| On Telegram | t.me/muguacloud |
Ecommerce storefront — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @muguacloud/132 · this entry28 Apr 2025, 00:52 UTC | @biteb2/15028 Apr 2025, 00:52 UTC | 1.00 | under a minute |
| @muguacloud/133 · this entry6 May 2025, 04:19 UTC | @biteb2/1516 May 2025, 04:19 UTC | 1.00 | under a minute |
| @muguacloud/134 · this entry14 Jun 2025, 04:25 UTC | @biteb2/15214 Jun 2025, 04:25 UTC | 1.00 | under a minute |
| @muguacloud/138 · this entry15 Aug 2025, 05:25 UTC | @biteb2/15615 Aug 2025, 05:25 UTC | 1.00 | under a minute |
| @biteb2/15720 Aug 2025, 17:00 UTC | @muguacloud/139 · this entry20 Aug 2025, 17:00 UTC | 1.00 | under a minute |
| @biteb2/15830 Aug 2025, 02:08 UTC | @muguacloud/140 · this entry30 Aug 2025, 02:08 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @biteb2 | 16 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (11–5) |
| @jinkelanotify | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @jinkelanotify (9–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 14 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 26 January 2025 to 16 June 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 3, the earliest publisher we hold is @muguacloud — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 04:15 | 2,343 | -2 |
| 6 Aug 2026, 21:00 | 2,345 | no change |
| 6 Aug 2026, 20:49 | 2,345 | first reading |
20 posts held, back to 26 January 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 2 pagesof 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 16 June 2026. An engagement rate over an empty window would be a number about nothing.
🎉🥢【端午 + 618 双节福利开冲！】🚀💥 粽子刚下肚，618 又来掏钱包了？ 别慌，Ninja 直接给你们上点真家伙 😎👇 🔥 全场任意套餐立减 20%！ 🎟 优惠码：20260618 ⏰ 活动截止：2026-06-23 23:59:59 ♻️ 不限制使用次数！想买几次买几次！ 这波属于： 钱包说“不行了不行了”💸 手指说“我还能点”👆 脑子说“先冲再说”🤣 ⚠️ 重点提醒：套餐等级别买错！别一顿操作猛如虎，回头问我时间去哪了 😂 ✅ 同等级购买：叠加时间 + 叠加流量 比如你现在是 VIP1，再买 VIP1： 👉 时间加上去，流量也加上去，快乐直接续杯 🥤✨ ⚠️ 跨等级购买：会覆盖老套餐时间，但流量会叠加 比如你现在是 VIP1，直接买 VIP3： 👉 老的 VIP1 时间会被 VIP3 覆盖 👉 但是流量会叠加 简单说就是：流量留下，时间换新老板了 👑😂 🚧 Ninja 2.0 升级版本 BETA 公测中！ 🥷⚡️…
【五一劳动节特别活动】 本次活动内容：价格没变，老板还在 😎 各位老铁，五一快乐！ 劳动节到了，按理说应该搞点活动，比如充值优惠、买一送一、抽奖返现什么的。 但考虑到最近这个环境，我们决定推出一个非常硬核的活动： 不涨价。 是的，你没看错。 在这个什么都涨的年代，我们还能保持原价，已经属于“含泪营业，带伤上岗”。🥲 最近圈子里的情况，大家懂的都懂。 压力越来越大，政策越来越紧，资源越来越难搞。 接下来机场行业可能会出现两种情况： 一种是技术升级，大家集体进化； 另一种是老板升级，直接升级成失联人员。🫠 所以这里也给大家说句实在话： 机场这种东西，建议月付。 别一激动就年付、三年付、传家宝套餐。 真不是我们唱衰自己，是现在这个环境谁拍胸口说“永远稳定”，那胸口大概率是钢板做的。 有条件的朋友，建议多准备几个备用。 别等真出问题了才到处问： “还有没有能用的？” 那时候大家都在问，客服也在问人生。😂 我们会继续尽…
📢🚨 重要公告｜请所有用户尽快完成切换 🚨📢 各位用户请注意 🙏 从 2026 年 4 月 1 日 起，线路环境再次明显收紧，情况比以前严重很多。现在已经不是以前那种“出了问题换机器、换 IP 还能继续扛”的阶段了。近一年多以来，订阅探测、协议探测越来越频繁 🔍⚠️，国内中转 / 专线入口一旦被通报，往往就是直接处理 ❌，几乎没有缓冲空间。 为了尽量保住线路、保证服务还能继续稳定运行 🛡🌐，我们决定： 🔥 即日起，所有用户必须统一切换到带 “Ninja” 字样的客户端 / 软件，并使用对应的 Ninja 订阅。 🔥 ✅ 后续专线线路只对 Ninja 客户端**开放。 ⛔️ 如果你使用的软件名称里 **不带 “Ninja”**，那么将 **无法继续使用专线业务**，只能走普通线路。 📉 这类情况下，常见体验就是：**延迟更高、不稳定、容易断开，甚至直接无法使用**。 🙏 这次调整不是为了折腾大家，而是当前环境下必须统一处…
# 春节 大优惠活动: 优惠码: 2026XN 可以-20% 截止到 2026-02-28 23:59:59 如果订单报错可能每日限额封顶, 这种情况请第2天凌晨再下单试试
# 元旦 大优惠活动: 优惠码: 20260101 可以-20% 截止到 2026-01-04 23:59:59 23:59:59 同等级重复购买＝时间+流量叠加 例：VIP1 青铜 → 再买 VIP1 青铜＝在原有基础上叠加时长与流量 跨等级购买＝立刻覆盖为新等级 VIP1 青铜 → 购买 VIP2＝立即变为 VIP2 的时长与权益，不与原套餐叠加 建议：想跨等级更划算？先留言客服把账号升级到目标等级，再下单更稳妥
CF 抽风, 等
# 双11 大优惠活动: 优惠码: 20251111 可以-20% 截止到 2025-11-17 23:59:59 同等级重复购买＝时间+流量叠加 例：VIP1 青铜 → 再买 VIP1 青铜＝在原有基础上叠加时长与流量 跨等级购买＝立刻覆盖为新等级 VIP1 青铜 → 购买 VIP2＝立即变为 VIP2 的时长与权益，不与原套餐叠加 建议：想跨等级更划算？先留言客服把账号升级到目标等级，再下单更稳妥 因为支付限额, 延续活动到17号晚上, 如果报500+错误码, 请等待限额重置后凌晨00:00后购买
# 双11 大优惠活动: 优惠码: 20251111 可以-20% 截止到 2025-11-12 23:59:59 同等级重复购买＝时间+流量叠加 例：VIP1 青铜 → 再买 VIP1 青铜＝在原有基础上叠加时长与流量 跨等级购买＝立刻覆盖为新等级 VIP1 青铜 → 购买 VIP2＝立即变为 VIP2 的时长与权益，不与原套餐叠加 建议：想跨等级更划算？先留言客服把账号升级到目标等级，再下单更稳妥 非iOS/路由器 用户请尽快切换到 Ninja 魔改协议!
📢 重要公告 | 协议与客户端升级通知 各位用户好，为提升稳定性与抗干扰能力，我们正在推进新一轮升级，具体如下： 🛑 老协议维护策略 由于“通报”已呈常态化，我们 不再为老协议（如 VMess 等）新增线路或带宽，仅做必要维护，直至过渡完成后 逐步退役。 老协议将继续可用，但不再扩容，请尽快规划迁移。 🧩 新方案上线 魔改协议（定制） 与 魔改 Clash 已 陆续上线。 新协议采用 独立转发机器 与老协议 完全隔离（⚠️ 仍不排除所有风险，持续观察与优化）。 📱 iOS 进度 iOS 内核测试已通过 ✅。 受上架与审核周期影响，近期优先提供离线形态（订阅方式）。 过渡期内，iOS 请先使用老的订阅系统 + Shadowrocket（小火箭） 正常使用；上架完成后将指引迁移至新方案。 🚀 部署节奏与体验 新协议的线路将 每日持续部署，目标是 更低延时、更高稳定性。 我们会根据观测数据 滚动优化，确保体…
# 中秋+国庆 大优惠活动: 优惠码: 20251001 可以-20% 截止到 2025-10-07 23:59:59 同等级重复购买＝时间+流量叠加 例：VIP1 青铜 → 再买 VIP1 青铜＝在原有基础上叠加时长与流量 跨等级购买＝立刻覆盖为新等级 VIP1 青铜 → 购买 VIP2＝立即变为 VIP2 的时长与权益，不与原套餐叠加 建议：想跨等级更划算？先留言客服把账号升级到目标等级，再下单更稳妥
🎒📚 开学季特惠 —————————————— 🔖 优惠码：2025KAIXUE 💸 折扣：全场 -10%（不限次数｜不限套餐类型） 🗓 有效期：即日起至 9 月 7 日晚上（以站点时间为准） 🛒 使用方式：结账时输入优惠码即可生效 📚 祝大家新学期：好好学习，天天向上！ 【套餐规则】 1）♻️ 同等级重复购买＝时间+流量叠加 例：VIP1 青铜 → 再买 VIP1 青铜＝在原有基础上叠加时长与流量 2）⬆️ 跨等级购买＝立刻覆盖为新等级 例：VIP1 青铜 → 购买 VIP2＝立即变为 VIP2 的时长与权益，不与原套餐叠加 3）💡 建议：想跨等级更划算？先留言客服把账号升级到目标等级，再下单更稳妥 【邀请返利（长期循环）】 1）🚫 请不要在群里公开传播节点或订阅链接 2）🧑🤝🧑 想邀请朋友一起用：私下发送你的专属邀请链接给对方注册 3）💰 循环返利机制：你邀请的用户每次充值，你都能获得其充值金额的固定比例…
请更新您的clash版本 安卓设备 android Clash Meta: https://github.com/MetaCubeX/ClashMetaForAndroid/releases/download/v2.11.15/cmfa-2.11.15-meta-universal-release.apk windows mihomo 便携版 64位: https://github.com/mihomo-party-org/mihomo-party/releases/download/v1.8.4/mihomo-party-windows-1.8.4-x64-portable.7z windows clash verge rev: https://github.com/clash-verge-rev/clash-verge-rev/releases/download/v2.3.2/Clash.Verge_2.3.2_x6…
Showing the 12 most recent of 20 posts we hold for @muguacloud. 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“木瓜云公告频道” (@muguacloud), 2,343 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/muguacloud.
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.