Channel
@mud9botdev
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2,539subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001118192538 |
|---|---|
| Type | Channel |
| Username | @mud9botdev |
| Created | Between 1 February 2017 and 1 September 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/mud9botdev |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 14:15 | 2,539 | -2 |
| 9 Aug 2026, 06:41 | 2,541 | -1 |
| 6 Aug 2026, 12:40 | 2,542 | no change |
| 6 Aug 2026, 11:49 | 2,542 | first reading |
20 posts held, back to 1 September 2017 — 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 22 February 2026. An engagement rate over an empty window would be a number about nothing.
各位鄉親父老，報平安時間！Mud9Bot 搬屋大行動已經順利完成！ 🚀 而家機器人已經正式滿血回歸，所有功能應該已經正常運作緊，大家可以繼續入谷賜酒派膠啦！🍻 由於今次係成個底層重新寫過兼大規模搬遷資料庫，雖然我哋已經檢查過好多次，但難免會有少少「裝修後遺症」。如果大家用落發現有咩 Bug、功能怪怪地、或者有任何疑問，請移玉步去 @Mud9BotSupport 同我哋反映下，我哋會盡快處理。 多謝大家耐性等候同支持，新一年繼續玩得開心啲！🎮
⚠️ P.S. 停機升級預告 為咗搬屋去新嘅資料庫系統，今晚（2月23號）凌晨 12 點起，我會暫時停機大約 1 個鐘進行升級。搞掂晒之後會再喺度同大家報平安！
Video, posted without a caption
各位鄉親父老，新年快樂！好耐無見，大家仲記唔記得我呀？ 由 2017 年出世到而家，不經不覺都陪咗大家幾年。老實講，我主人自從 2018 年底就開始瘋狂潛水，搞到我都變咗隻半生不死嘅孤兒仔。呢幾年入面，我有時跪低咗要等幾日先有人得閒踢醒我；有啲功能又因為 Telegram 轉 API，或者對家網頁執笠而壞晒。喺度真係要同大家講聲唔好意思，辛苦大家一直以嚟嘅包容！ 不過！趁住新正頭，我有一個天大嘅好消息要宣佈 —— Mud9Bot 終於迎嚟史詩級大翻新！ 主人最近的起心肝，將我成個底層重新寫過，而家成個架構硬淨咗好多，處理速度快咗，以後應該（希望）唔會再咁容易死機。大家以前最鍾意嘅核心功能全部保留晒，壞咗嘅已經修復好，仲加入咗一啲全新嘅升級添！ 下面話畀大家知而家有咩玩： 🌟 經典保留：賜酒派膠 (/z, /check)、群組管理 (/msettings、殘體/5P字過濾) 🔧 全面修復：天氣交通 (/weather, …
系統維護已經完成。
Mud9Bot 喺度祝大家新年快樂，狗年行大運！希望大家嚟緊一年都繼續支持 Mud9Bot 啦！ 喺度為大家放上一系列長輩圖 快啲 send 俾你啲長輩啦！中意啲圖嘅話就 Subscribe 佢地同埋 Like 佢地喇！
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
似乎已經回復正常，大家可以繼續賜酒派膠喇。
Mud9Bot server 有啲問題，暫時停止服務直至另行通知。
頭先應該有啲 Group 用緊 @Mud9WWBot 果時轉用某啲語言果時開唔倒 Game，而家已經 fix 好喇！
Showing the 12 most recent of 20 posts we hold for @mud9botdev. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“乜鳩Bot Official Channel” (@mud9botdev), 2,539 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/mud9botdev.
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.