
Supergroup
magic88官方交流群
@Magic88_VIP
On this record: Growth · Engagement · Citations · Cite this entry
6,955members
-71 since we began measuring on 7 August 2026
104 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002479216356 |
|---|---|
| Type | Supergroup |
| Username | @Magic88_VIP |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/Magic88_VIP |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 4 Sept 2026, 02:16 | 6,955 | -16 |
| 31 Aug 2026, 08:04 | 6,971 | -53 |
| 28 Aug 2026, 04:02 | 7,024 | +24 |
| 27 Aug 2026, 11:54 | 7,000 | no change |
| 24 Aug 2026, 17:12 | 7,000 | -44 |
| 20 Aug 2026, 17:13 | 7,044 | -27 |
| 17 Aug 2026, 22:58 | 7,071 | +21 |
| 14 Aug 2026, 12:18 | 7,050 | +13 |
| 10 Aug 2026, 23:15 | 7,037 | +7 |
| 8 Aug 2026, 09:32 | 7,030 | +4 |
| 7 Aug 2026, 11:30 | 7,026 | 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.
Mentions
Named by 46 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@nb688 · 350,52833 posts菲律宾大事件
@PHDA15 · 91,22826 posts吃瓜新闻
@chiguaxinwen1 · 23,15025 posts菲律宾新闻
@flbxinwen01 · 21,84325 posts曝光骗子
@baoguang2022 · 138,04724 posts抖音吃瓜
@douyinchigua1 · 22,80224 posts骗子曝光
@pzbgfabu666 · 359,49324 posts求职招聘
@qzzpfabu888 · 626,51424 posts🇦🇪迪拜大事件
@YYL333 · 114,06524 posts迪拜求职招聘
@dibai2025 · 316,79723 posts影视软件、TVBox接口分享
@TVBoxjkou · 70,93822 posts亚美尼亚大事件🇦🇲
@YMNY222 · 107,58422 posts今日全网曝光频道
@bg833 · 292,42220 posts吃瓜群众348头条新闻大事件
@CG348 · 49,66720 posts东南亚人才资源库
@YYL117 · 108,16620 posts禁忌书屋/成人小说/长篇精选
@JJSW125689 · 170,79919 posts迪拜/二手物品/二手交易
@YYL119 · 38,78518 posts菲律宾华人大事件
@ke5689 · 171,95717 posts吃瓜群众🍉
@chigua2022 · 201,93916 posts东南亚曝光频道
@BG2288 · 85,34915 posts吃瓜群众12307国产精选视频
@CG12307 · 61,30014 postsChigua🍉吃瓜中心
@chigua974 · 24,79013 posts东南亚|吃瓜|灰产|博彩|体育
@avpao · 308,87212 posts好奇喵(沙雕猎奇)
@gaoxiaoqipa · 25,59412 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.
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“magic88官方交流群” (@Magic88_VIP), 6,955 members as measured 4 September 2026. Telegram Register, tgregister.com/channel/Magic88_VIP.
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.