Channel
@nmbotchannel
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
33,166subscribers
+122 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001681341595 |
|---|---|
| Type | Channel |
| Username | @nmbotchannel |
| Description | nmBot Telegram 官方频道。 柠动聊天，好戏连篇。 开始使用 nmBot: @nmnmfunbot |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/nmbotchannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:13 | 33,166 | +37 |
| 13 Aug 2026, 13:26 | 33,129 | +34 |
| 12 Aug 2026, 13:24 | 33,095 | +23 |
| 11 Aug 2026, 10:45 | 33,072 | -3 |
| 10 Aug 2026, 09:20 | 33,075 | +19 |
| 9 Aug 2026, 09:53 | 33,056 | +10 |
| 8 Aug 2026, 08:06 | 33,046 | +2 |
| 7 Aug 2026, 10:00 | 33,044 | no change |
| 7 Aug 2026, 09:49 | 33,044 | first reading |
20 posts held, back to 12 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 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 11 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
174 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 71.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 125 | 71.8% | |
| 👍 | 19 | 10.9% | |
| 👏 | 11 | 6.32% | |
| 😘 | 8 | 4.60% | |
| 🎃 | 3 | 1.72% | |
| 🎉 | 3 | 1.72% | |
| 🥰 | 3 | 1.72% | |
| ❤🔥 | 1 | 0.575% | |
| 💯 | 1 | 0.575% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 174reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 April 2026 to 11 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nmbotchannel. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 12 April 2026 to 11 June 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
美加墨世界杯竞猜王 亲爱的 nm 人，“美加墨世界杯竞猜王”活动现已开启！ 〓 活动内容 〓 竞猜赢奖：在美加墨世界杯期间，您可以在 nmBot 面板通过本活动消耗积分参与比赛结果竞猜。 〓 活动地址 〓 请到 nmBot 面板的“积分”板块参加活动。 或点击此链接参与活动：https://nmbot.nmnm.fun/#/credit/bet?eventId=3 〓 注意事项 〓 每场比赛仅可竞猜一次，确认竞猜后无法更改或取消选择；比赛开始后不可参与竞猜。 更多活动详情请前往活动页面查看。
❤28👍1
nmBot 2026 年 6 月版本已知问题和修复说明 nmBot 2026 年 6 月版本期间，此处将持续更新 nmBot 2026 年 6 月版本期间新增的已知问题和对应的修复内容说明。 已知问题 - （2026 年 7 月 19 日）已知特定情况下部分群组定时任务执行异常的问题。 - （2024 年 11 月 17 日）正在调查特定情况下部分频道管理功能不生效的问题。 查看全部已知问题 #已知问题
❤6
nmBot 2026 年 6 月更新 本次更新为 nmBot 带来重要的错误修复。 在线阅读更新日志 问题修复 - 修复了特定情况下“同频气氛组”功能限额计算错误的问题。 - 修复了特定情况下入群验证功能可能在封禁用户操作完成前发送操作完成消息的问题。 - 修复了特定情况下群组定时任务功能可能在“系统模式”权限变更完成前发送选定消息模板的问题。 - 修复了特定情况下 nmartChat 功能返回的消息中有概率出现意外内容的问题。 - 修复了特定情况下 nmBot 面板开屏弹窗显示条件判断错误的问题。 - 修复了添加联防联控方案管理群组时判断条件错误的问题。 - 修复了传入空对话 ID 列表时，群组信息 API 无法正常返回内容的问题。 - 修复了特定情况下入群验证星币验证会在流程完成前提前通过的问题。 - 修复了特定情况下批量入群检测可能导致入群验证流程提前结束的问题。 - 修复了特定情况下入群验证对陈旧成员变更事件仅记录…
❤11
#Update 2026 年 5 月 22 日 13:05 nmBot 版本号：26.4.4-wine+7387 - “限制群成员使用指令”功能现在对所有群组开放，不再限制启用该功能所需的群组人数或需要 nmBot+ 订阅。 - 优化了 nmBot 服务的状态监测机制。 - 优化了获取用户信息的流程。
👏10❤7🎉2💯1
#Update 2026 年 5 月 18 日 10:47 nmBot 版本号：26.4.3-wine+7375.2000 - 修复了特定情况下基于 nmBot 智能的“同频气氛组”功能不正常回复消息的问题。 - 修复了 nmBot 面板的“按类型自动删除消息”功能入口启用计数缺少“故事”和“访客机器人消息”两种类型的问题。
#Update 2026 年 5 月 17 日 17:03 nmBot 版本号：26.4.3-wine+7375 - 群组定时任务现在支持设置“编辑标签”和“对消息表态”权限和“自动删除访客机器人消息”。 - 群组按类型自动删除消息功能新增“自动删除访客机器人消息”。 - 启用骚扰拦截功能的群组中的骚扰表态现在将被自动删除。 - 使用 /spam, /dban, /dmute, /dkick 和 /dwarn 指令时将自动删除该用户在群组中的表态。 - 优化了机器人遇到特定致命错误时的自动重试机制。 - 修复了使用 /json 指令时，若原始消息过长，回复消息发送失败的问题。 - 修复了启用 nmartChat+ 的群组在 nmBot+ 过期后保持 nmartChat+ 启用且无法关闭的问题。 - 修复了导致群组骚扰拦截“识别其他机器人发送的消息”功能在特定情况下不起作用的问题。
❤3
识别机器人发送的骚扰消息 群组骚扰拦截新增“识别其他机器人发送的消息”功能，可允许 nmBot 对其他机器人发送的消息进行骚扰拦截识别，包括访客机器人。该功能可在 /config 菜单和 nmBot 面板中启用。 Powered by 🍋🍋 #nmBootsChat #柠动乐聊
😘8❤6
#Update 2026 年 5 月 15 日 15:54 nmBot 版本号：26.4.2-wine+7358.1000 - 修复了特定情况下机器人不正常响应群组中部分匿名消息的问题。
#Update 2026 年 5 月 15 日 10:58 nmBot 版本号：26.4.2-wine+7358 - 群组骚扰拦截新增“识别其他机器人发送的消息”功能，可允许 nmBot 对其他机器人发送的消息进行骚扰拦截识别，包括访客机器人。该功能可在 /config 菜单和 nmBot 面板中启用。 - 优化了检测到待处理更新堆积时的自动清理机制。 - 优化了机器人进程的退出和重启机制。
🥰3❤1🎉1
nmBot 服务状态公告 我们正在调查 nmBot 不正常处理和回复消息的问题。 13:14：我们轮换了机器人密钥并监测到机器人再次开始处理更新。 13:13：我们确认机器人接收的更新处理队列不包含任何更新。 我们将持续关注并更新服务运行情况。
❤2
nmBot 将添加针对访客机器人的拦截操作 Telegram 在最近的更新中引入了访客机器人 (Guest Bot)，这类机器人被允许在未加入群组的情况下通过被群组成员提及来在群组中发送消息。我们收到用户反馈，目前已有在野的通过该特性绕过机器人入群验证和骚扰拦截在群组中发送骚扰消息的机器人。 由于调用访客机器人的权限不受群组权限控制，群组管理员无法禁止访客机器人在群组中发送消息。 为避免访客机器人发送骚扰消息，在 nmBot Preview 26.3.0-wine.beta (内部版本号 7603.15000) 中，我们已启动对所有来自机器人的消息经过适用的骚扰拦截功能、nmBot 智能骚扰拦截功能、Combot Anti-Spam 和群组自定义规则识别的测试，识别与处理方式与普通用户相同。 我们将在该测试稳定后在 nmBot 中实施针对访客机器人的骚扰拦截功能，并发布关于该功能的更多信息。 #nmBootsChat …
👍6❤3👏1
#Update 2026 年 4 月 29 日 13:42 nmBot 版本号：26.4.1-wine+7344 - 调整了媒体组消息的处理时间，并修复了处理不完整的媒体组消息时出错的问题。 - 优化了联防联控机制在群组中未启用时的处理逻辑。 - 优化了骚扰拦截功能识别用户表情状态的逻辑。 - 修复了特定情况下机器人重复获取商业连接信息的问题。
❤12
Showing the 12 most recent of 20 posts we hold for @nmbotchannel. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 668,705 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“nmBot 频道” (@nmbotchannel), 33,166 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/nmbotchannel.
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.