Supergroup
木牌聊天（总群）
@mupaifood
On this record: Growth · Engagement · Cite this entry
5,658members
-598 since we began measuring on 7 August 2026
216 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002160650699 |
|---|---|
| Type | Supergroup |
| Usernames | @mupaiav @mupaifood |
| Description | 《木牌头条》聚焦木牌大小事情！ 关注柬埔寨及东南亚新闻资讯！ 官方频道 @mupai717 官方聊天群 @mupaifood 唯一创始人 @mupai919 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 8 |
| On Telegram | t.me/mupaifood |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 30 Aug 2026, 19:43 | 5,658 | no change |
| 30 Aug 2026, 06:13 | 5,658 | -89 |
| 27 Aug 2026, 05:06 | 5,747 | -41 |
| 24 Aug 2026, 05:02 | 5,788 | -71 |
| 20 Aug 2026, 04:33 | 5,859 | -59 |
| 16 Aug 2026, 21:16 | 5,918 | -14 |
| 10 Aug 2026, 12:55 | 5,932 | -324 |
| 7 Aug 2026, 18:44 | 6,256 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“木牌聊天（总群）” (@mupaifood), 5,658 members as measured 30 August 2026. Telegram Register, tgregister.com/channel/mupaifood.
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.