@GVsPbot 临时维护通知! 2025-02-25 时间 22:40分开始 正常一到两个小时可正常使用❗️
Signed ◔͜͡◔ vahid ◔͜͡◔

Channel
@Me_Groupbot
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
2,108subscribers
+17 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001420295323 |
|---|---|
| Type | Channel |
| Username | @Me_Groupbot |
| Created | Between 1 April 2019 and 30 October 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/Me_Groupbot |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 07:07 | 2,108 | +17 |
| 8 Aug 2026, 11:00 | 2,091 | no change |
| 8 Aug 2026, 10:56 | 2,091 | first reading |
20 posts held, back to 30 October 2019 — 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 pageof 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 January 2020. An engagement rate over an empty window would be a number about nothing.
@GVsPbot 临时维护通知! 2025-02-25 时间 22:40分开始 正常一到两个小时可正常使用❗️
Signed ◔͜͡◔ vahid ◔͜͡◔
部分已知bug 正在更新中....... 问题反馈商务合作 ✅ 联系客服 ├ @GVsPKFbot
Signed ◔͜͡◔ vahid ◔͜͡◔
這是最好的群組管理機器人,擁有數百種功能,免費使用。 群管机器人 @GVsPbot 问题反馈商务合作 ✅ 联系客服 ├ @GVsPKFbot
Signed ◔͜͡◔ vahid ◔͜͡◔
🌘 夜间模式 指定时间自动开启、解除全员禁言。 已修复时间bug问题
Signed ◔͜͡◔ vahid ◔͜͡◔
已修复新成员限制 bug ❌限制发消息: └ 新群员进群在设置时间 10分钟 内,不能发送消息 群组设置更简单
Signed ◔͜͡◔ vahid ◔͜͡◔
文本设置你的消息内容,已全面支持 💡HTML 和文字字体格式(加粗、链接、剧透、块引用等): 简单易懂❗️
Signed ◔͜͡◔ vahid ◔͜͡◔
#群管机器人 @GVsPbot #已逐渐增加其它国家语言 现已全面开放功能免费使用
Signed ◔͜͡◔ vahid ◔͜͡◔
This is the best group management bot with hundreds of features and free to use. ✅ Official Bots ├ 🇬🇧 @GVsPbot 🌐 Support Groups ├ 🇬🇧 English Support Group ├ 🇫🇷 问题反馈商务合作 ✅ 联系客服 ├ @GVsPKFbot
Signed ◔͜͡◔ vahid ◔͜͡◔
增加转发垃圾检测
Signed ◔͜͡◔ vahid ◔͜͡◔
修复已知 BUG
Signed ◔͜͡◔ vahid ◔͜͡◔
机器人用户使用协议 用户在使用本软件时,必须遵循以下原则: 1) 遵守当地有关的法律和法规; 2) 不得为任何非法目的而使用本服务软件; 3) 遵守所有与本服务有关的网络协议、规定和程序; 4) 不得利用本软件系统进行任何可能对互联网的正常运转造成不利影响的行为; 5) 不为任何色情、赌博、诈骗、暴力、恐怖或者教唆犯罪、危害国家安全等违法群组提供服务; 6) 不使用外挂或者其他作弊手段、不正当或不公平手段参加本软件提供的服务。 免责声明 本软件禁止⽤于任何违法⽤途,因违反本声明的规定而触犯法律和法规的,一切后果自己负责,本软件不承担任何责任,凡以任何方式使用本软件的,视为自愿接受本免责声明。
Signed ◔͜͡◔ vahid ◔͜͡◔
日常更新: #命令 /mute 禁言 和 /ban 封禁 增加时间参数 时间参数用法: /mute 4m (4m = 4 minutes, 3h = 3 hours, 6d = 6 days, 5w = 5 weeks) /mute 4 不加单位,默认分钟 #用户检查 - 增加 必须订阅频道:群成员必须订阅指定频道(或加入指定群)后获得发言权限
Signed ◔͜͡◔ vahid ◔͜͡◔
Showing the 12 most recent of 20 posts we hold for @Me_Groupbot. 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 — 978,769 of 1,183,361entries 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.
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.
@Me_Groupbot named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“GVsPbot 群管机器人频道” (@Me_Groupbot), 2,108 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Me_Groupbot.
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.