Channel
@qunjiankongBot_help
On this record: Growth · Engagement · Posts · Citations · Cite this entry
227subscribers
-3 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001486083232 |
|---|---|
| Type | Channel |
| Username | @qunjiankongBot_help |
| Created | 13 May 2021 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/qunjiankongBot_help |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 12:03 | 227 | -2 |
| 17 Aug 2026, 23:22 | 229 | -1 |
| 11 Aug 2026, 00:30 | 230 | no change |
| 11 Aug 2026, 00:17 | 230 | first reading |
17 posts held, back to 13 May 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 17 posts for this entry, the most recent from 9 March 2026. An engagement rate over an empty window would be a number about nothing.
群关键词监控📮关键词监听📮导航群小助手📮电报群监控 pinned «◾️服务费用相关的问题 ▪️新用户免费试用2小时 ▪️月度会员为：10USDT ▪️季度会员为：25USDT ▪️年度会员为：50USDT 🔺支付方式：仅支持USDT ◾️关于账号、群组、关键词的数量限制 你可以选择绑定3个账号或者一个群组！ ▪️绑定群组，在群里使用机器人可以绑定30个关键词。 ▪️绑定账号，一个账号可以绑定10个关键词（可以同时绑定3个账号） 🔺机器人用户名 @qunjiankongBot 🔸返回目录 🔹联系客服 🔹进入机器人»
免费的频道机器人 @pd_gl_bot 免费的群管机器人 @qunguanliBot 免费的收款通知机器人：@jt_usdt_bot 🔺如需频道监听请联系 @lisi1024 定制
电报PC客户端 7月1号版本有BUG，机器人不会正常显示按钮。 🔺不要更新，不要更新，不要更新。IOS端会正常显示 ------------------------------------------------------- 🔺7月3号更新已修复
通知： 各位用户下午好，由于技术员操作失误导致用户信息出错，现已修复！但需要各位用户重新绑定令牌才能正常推送，给大家带来不便深感歉意，我们将补偿每位用户3天会员时间，系统会自动增加会员时间。
新增功能： 绑定关键词后需要选择匹配模式，每个关键词独立设置。之前的默认模糊匹配。 模糊匹配：只要包含关键词的消息都会被匹配到 精确匹配：与关键词完全相同的消息才会被匹配到 🔸返回目录 🔹联系客服 🔹进入机器人
机器人已恢复正常，给大家带来不便深感歉意，我们将补偿每位用户3天会员时间，系统会自动增加会员时间。
◾️关于账号、群组、关键词的数量限制 你可以选择绑定3个账号或者一个群组！ ▪️绑定群组，在群里使用机器人可以绑定30个关键词。 ▪️绑定账号，一个账号可以绑定10个关键词（可以同时绑定3个账号） 🔸返回目录 🔹联系客服 🔹进入机器人
◾️如何将消息推送到群里 ▪️选择将消息推送到群里可以减少更换账号带来的麻烦，关键词也无需重新添加！群成员都可以看到推送！群成员都可以操作机器人。 🔺操作方法：新建群组或者选择一个群组--->管理群组--->群组类型--->选择公开群组--->邀请机器人 @qunjiankongBot 加入群组。最后在群里发送/start命令唤起机器人菜单即可操作机器人。 🔺操作完成后可以修改为私人群组。已经是公开群的就不需要设置了，直接邀请机器人加入群组。 🔸返回目录 🔹联系客服 🔹进入机器人
◾️账户相关的问题 在个人中心里可以看到账户信息包含用户ID、昵称、用户名、状态以及服务时间。 也可以点击按钮关闭或者开启推送，关闭后机器人将不会推送订阅消息给当前用户。其他账户不受影响。 在屏蔽用户管理中可以解除之前屏蔽的用户。 🔸返回目录 🔹联系客服 🔹进入机器人
◾️推送相关的问题 当你收到推送消息后可以点击“分析历史”查看这个用户之前都发送了些什么。也可以选择将这个用户屏蔽，屏蔽后将不在接收这个用户的消息。被多人屏蔽后机器人将永久拉黑这个用户。 🔸返回目录 🔹联系客服 🔹进入机器人
◾️导航群相关的问题 我们监控的是中文的各大导航群，目前已收录140多个，还会持续不断的更新。如果你有什么好的导航群推荐，也可以联系我们。 ▪️查询导航群的方法： 在机器人窗口中发送：/nav 你就可以看到我们已加入的导航群 ▪️查询导航群中最热门的关键词 在机器人窗口中发送：/top 你就可以看到当前最热门的关键词。24小时更新哦！ 🔸返回目录 🔹联系客服 🔹进入机器人
◾️关键词相关的问题 首先要注意的是，当用户发送的内容包含你设定的关键词时，才会将用户信息推送给你。因此，你需要根据自己的业务内容去考虑你的客户群体可能会搜索的关键词。 默认情况下，当用户发送的内容中包含你监控的关键词时，则会匹配成功发送给你。认真选用自己的关键词，是用好监控服务的重点，准确的关键词能让你更精准的定位客户！ ▪️添加关键词的具体操作： 在机器人窗口中点击：关键词管理 ---> 点击“➕”按钮 ---> 发送你的关键词给机器人。 ▪️删除关键词的具体操作： 在机器人窗口中点击：关键词管理 ---> 点击要删除关键词的对应按钮 ---> 点击确认或者取消。 🔸返回目录 🔹联系客服 🔹进入机器人
Showing the 12 most recent of 17 posts we hold for @qunjiankongBot_help. 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.
Citation-graph rank — 753,699 of 1,629,535 entries 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.
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.
Names
Channels on the register whose handles appear in this channel's 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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“群关键词监控📮关键词监听📮导航群小助手📮电报群监控” (@qunjiankongBot_help), 227 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/qunjiankongBot_help.
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.