nmBot 服务状态公告 由于系统故障,同频气氛组、nmBot 智能骚扰拦截、nmartChat、nmartChat+、nmBot Copilot 和 nmBot 预览版积分系统目前不可用。 14:50:我们确认此问题已解决,相应服务已恢复正常。 13:28:我们的服务合作方正在调查导致 nmTeam 服务故障的硬件故障。 12:27:我们注意到包括上述服务在内的部分 nmTeam 服务出现的故障。 我们将持续关注并更新服务运行情况。
🎃5❤2🫡1

Channel
@nmbotchannel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
33,648subscribers
+604 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 | 19 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/nmbotchannel |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 58% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 13:57 | 33,648 | +14 |
| 17 Sept 2026, 02:42 | 33,634 | +27 |
| 15 Sept 2026, 02:00 | 33,607 | +41 |
| 13 Sept 2026, 14:01 | 33,566 | +25 |
| 11 Sept 2026, 21:57 | 33,541 | +33 |
| 9 Sept 2026, 10:37 | 33,508 | +84 |
| 5 Sept 2026, 23:57 | 33,424 | +36 |
| 3 Sept 2026, 17:36 | 33,388 | +12 |
| 2 Sept 2026, 13:23 | 33,376 | +7 |
| 1 Sept 2026, 14:26 | 33,369 | +7 |
| 31 Aug 2026, 12:28 | 33,362 | +8 |
| 30 Aug 2026, 10:47 | 33,354 | +20 |
| 29 Aug 2026, 12:28 | 33,334 | -1 |
| 28 Aug 2026, 13:42 | 33,335 | +11 |
| 27 Aug 2026, 13:06 | 33,324 | +15 |
| 26 Aug 2026, 14:26 | 33,309 | +23 |
| 25 Aug 2026, 13:02 | 33,286 | +12 |
| 24 Aug 2026, 14:34 | 33,274 | +14 |
| 22 Aug 2026, 23:46 | 33,260 | -3 |
| 21 Aug 2026, 15:36 | 33,263 | first reading |
22 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 76 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 21 September 2026 |
|---|---|
| Posts held | 22 (12 April 2026 – 21 September 2026) |
| Views total | 11,370 |
| Reactions total | 36 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 05:41 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 22 September 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.
221 reactions across 21 posts, in 10 distinct kinds. The most used accounts for 64.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 143 | 64.7% | |
| 🫡 | 22 | 9.95% | |
| 👍 | 20 | 9.05% | |
| 👏 | 12 | 5.43% | |
| 🎃 | 8 | 3.62% | |
| 😘 | 8 | 3.62% | |
| 🎉 | 3 | 1.36% | |
| 🥰 | 3 | 1.36% | |
| ❤🔥 | 1 | 0.452% | |
| 💯 | 1 | 0.452% |
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 22 of the 22 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 221 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 12 April 2026 to 21 September 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 22 most recent posts we hold for this entry, published 12 April 2026 to 21 September 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.
nmBot 服务状态公告 由于系统故障,同频气氛组、nmBot 智能骚扰拦截、nmartChat、nmartChat+、nmBot Copilot 和 nmBot 预览版积分系统目前不可用。 14:50:我们确认此问题已解决,相应服务已恢复正常。 13:28:我们的服务合作方正在调查导致 nmTeam 服务故障的硬件故障。 12:27:我们注意到包括上述服务在内的部分 nmTeam 服务出现的故障。 我们将持续关注并更新服务运行情况。
🎃5❤2🫡1
nmBot 服务中断公告 由于 Telegram 服务器故障,nmBot、nmBot 预览版、nmBot 面板和 nmBot 预览版面板目前响应缓慢或不可用。 14:17:我们关注到大部分机器人功能已恢复正常。 14:11:我们关注到 nmBot 正在恢复对部分群组消息和私信的响应。 13:45:由于 Telegram 服务持续不稳定,用户可能仍然会在使用机器人时遇到问题。 11:32:我们已查明一个导致机器人向用户发送消息时卡住的 Telegram 服务器问题,这将影响用户在私信中与机器人的交互。 11:22:我们注意到群组中的多数机器人功能正在恢复。 我们将持续关注并更新服务运行情况。
🫡21❤6👏1
美加墨世界杯竞猜王 亲爱的 nm 人,“美加墨世界杯竞猜王”活动现已开启! 〓 活动内容 〓 竞猜赢奖:在美加墨世界杯期间,您可以在 nmBot 面板通过本活动消耗积分参与比赛结果竞猜。 〓 活动地址 〓 请到 nmBot 面板的“积分”板块参加活动。 或点击此链接参与活动:https://nmbot.nmnm.fun/#/credit/bet?eventId=3 〓 注意事项 〓 每场比赛仅可竞猜一次,确认竞猜后无法更改或取消选择;比赛开始后不可参与竞猜。 更多活动详情请前往活动页面查看。
❤33👍2
nmBot 2026 年 6 月版本已知问题和修复说明 nmBot 2026 年 6 月版本期间,此处将持续更新 nmBot 2026 年 6 月版本期间新增的已知问题和对应的修复内容说明。 已知问题 - (2024 年 11 月 17 日)正在调查特定情况下部分频道管理功能不生效的问题。 查看全部已知问题 #已知问题
❤6
nmBot 2026 年 6 月更新 本次更新为 nmBot 带来重要的错误修复。 在线阅读更新日志 问题修复 - 修复了特定情况下“同频气氛组”功能限额计算错误的问题。 - 修复了特定情况下入群验证功能可能在封禁用户操作完成前发送操作完成消息的问题。 - 修复了特定情况下群组定时任务功能可能在“系统模式”权限变更完成前发送选定消息模板的问题。 - 修复了特定情况下 nmartChat 功能返回的消息中有概率出现意外内容的问题。 - 修复了特定情况下 nmBot 面板开屏弹窗显示条件判断错误的问题。 - 修复了添加联防联控方案管理群组时判断条件错误的问题。 - 修复了传入空对话 ID 列表时,群组信息 API 无法正常返回内容的问题。 - 修复了特定情况下入群验证星币验证会在流程完成前提前通过的问题。 - 修复了特定情况下批量入群检测可能导致入群验证流程提前结束的问题。 - 修复了特定情况下入群验证对陈旧成员变更事件仅记录…
❤12
#Update 2026 年 5 月 22 日 13:05 nmBot 版本号:26.4.4-wine+7387 - “限制群成员使用指令”功能现在对所有群组开放,不再限制启用该功能所需的群组人数或需要 nmBot+ 订阅。 - 优化了 nmBot 服务的状态监测机制。 - 优化了获取用户信息的流程。
👏10❤8🎉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😘8
#Update 2026 年 5 月 15 日 15:54 nmBot 版本号:26.4.2-wine+7358.1000 - 修复了特定情况下机器人不正常响应群组中部分匿名消息的问题。
❤1
#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
Showing the 12 most recent of 22 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.
@nmbotchannel edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 12 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“nmBot 频道” (@nmbotchannel), 33,648 subscribers as measured 19 September 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.