Bot
南宫娱乐机器人@NN88
@nn88
On this record: Growth · Engagement · Citations · Cite this entry
15,524monthly users
+47 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 8578779904 |
|---|---|
| Type | Bot |
| Usernames | @ng66 @ngyx_bot @nn88 |
| First recorded | 17 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/nn88 |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 5 Sept 2026, 03:39 | 15,524 | no change |
| 4 Sept 2026, 08:19 | 15,524 | -327 |
| 2 Sept 2026, 18:17 | 15,851 | no change |
| 2 Sept 2026, 06:17 | 15,851 | -159 |
| 1 Sept 2026, 04:03 | 16,010 | no change |
| 31 Aug 2026, 21:57 | 16,010 | -247 |
| 30 Aug 2026, 05:49 | 16,257 | no change |
| 30 Aug 2026, 01:09 | 16,257 | -424 |
| 26 Aug 2026, 21:13 | 16,681 | no change |
| 26 Aug 2026, 04:48 | 16,681 | -412 |
| 24 Aug 2026, 22:28 | 17,093 | no change |
| 23 Aug 2026, 21:15 | 17,093 | -297 |
| 22 Aug 2026, 06:47 | 17,390 | no change |
| 22 Aug 2026, 01:38 | 17,390 | -346 |
| 18 Aug 2026, 20:28 | 17,736 | no change |
| 18 Aug 2026, 16:17 | 17,736 | -566 |
| 17 Aug 2026, 09:58 | 18,302 | no change |
| 16 Aug 2026, 13:58 | 18,302 | -302 |
| 12 Aug 2026, 19:33 | 18,604 | +1,003 |
| 9 Aug 2026, 20:21 | 17,601 | first reading |
Engagement
No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.
Mentions
Named by 19 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.
@VPNNNB · 127,35630 posts免费VPN-代理-加速器
@GSDL6 · 248,23627 posts飞机主题
@piyazt · 6,27623 posts树洞㊙️伤感电台/匿名小秘密
@shanggandiantai · 5,08320 posts流 量 大 王
@TOPBD88 · 4,84220 postsemoji分享
@piyaemoji · 6,99113 posts免费代理|免费加速器|飞机代理|免费梯子
@TGDL2024 · 9,16713 posts顶尖28大群核心频道
@LSZj8888 · 16,7507 posts吃瓜猎奇 黑料曝光 搞笑段子 幽默视频
@meihaochigua · 51,4437 posts大事件曝光/吃瓜热点/搞笑视频
@hhlgx · 75,5276 posts@tele
@tele · 11,2116 posts奇闻趣事|抽象热点|猎奇吃瓜
@fenhongshequ · 59,5275 posts吃瓜猎奇 幽默视频 搞笑段子
@ay2028 · 66,6664 posts吃瓜曝光|时事热点
@luanlunsdjg · 33,6553 posts南宫集团🏆官方频道 @NG99
@ng99 · 15,6143 posts柬埔寨新闻曝光（吃瓜）
@JRTT1233 · 44,6112 posts村里人福利频道
@cunlirenfuli · 3,1121 post红花果廉价NFT用户名
@honghuaguo · 31 post东南亚新闻大事件
@muzisd · 1,4331 post
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“南宫娱乐机器人@NN88” (@nn88), 15,524 monthly users as measured 5 September 2026. Telegram Register, tgregister.com/channel/nn88.
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.