Telegram RegisterThe public register of Telegram
Telegram profile photo for TGBot News

Channel

TGBot News

@mybots

3 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

26,947subscribers

+2,383 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001002928352
TypeChannel
Usernames@hao12news @livegram @mybots
Description● 记录 @MBot @TGBot @QQQBot 最新消息 💎会员专属版: @NBot ● 反馈群: @GroupTG ● 管理员: @GroupTTGBot 抽奖频道 : @TGBot_Lottery 帮助网站 : https://TGBot.Bot
CreatedBetween 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live27 September 2026
Measurements held105
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/mybots

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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.

Growth

24,56426,94725,755.55 August 202627 September 2026
105 measurements spanning 52 days, net +2,383. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 24,207–27,304 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 105
Measured (UTC)SubscribersChange
27 Sept 2026, 05:1626,947+47
26 Sept 2026, 05:4126,900+26
24 Sept 2026, 23:2026,874+256
19 Sept 2026, 08:3926,618+49
17 Sept 2026, 17:5926,569+35
17 Sept 2026, 08:1826,534+8
17 Sept 2026, 00:4026,526+78
15 Sept 2026, 14:2226,448+17
15 Sept 2026, 08:5626,431+7
14 Sept 2026, 23:3726,424+33
13 Sept 2026, 21:5926,391+2
13 Sept 2026, 20:2026,389+28
13 Sept 2026, 11:4126,361+33
12 Sept 2026, 07:5926,328no change
11 Sept 2026, 23:3926,328+7
11 Sept 2026, 15:2226,321-2
10 Sept 2026, 05:1626,323+10
9 Sept 2026, 14:0126,313+28
9 Sept 2026, 03:1426,285+63
6 Sept 2026, 19:3726,222first reading

Engagement

22 posts held, back to 14 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 65 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
51.4%
avg views ÷ 26,947 subscribers
Avg views / post
13,900
2 posts measured
Reaction rate
0.199%
reactions ÷ views · ER floor
Posts in window
2
of 22 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 September 2026
Posts held22 (14 September 2025 – 11 September 2026)
Views total27,700
Reactions total55
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 08:51 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.

What this channel posts

Photos
105
Videos
47
Links
93

Lifetime counters from Telegram’s own channel header, read 27 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.

Video runtime
6m 50s
Average length
6m 50s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

828 reactions across 22 posts, in 19 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤66280.0%
👍516.16%
👎323.86%
🔥141.69%
👏121.45%
⚡70.845%
🎉70.845%
🖕70.845%
😢60.725%
🤡60.725%
😎50.604%
👌40.483%
💩40.483%
😁30.362%
🥰30.362%
❤‍🔥20.242%
😱10.121%
🤔10.121%
🥱10.121%

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 828 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 14 September 2025 to 11 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.

Recent posts

11 Sept 2026, 12:57 UTC≈13,000 views38 reactionsread 27 September 2026
Photo

🚀 TGBot|社区运营经理招聘 招聘岗位:社区运营经理 × 2 TGBot 是一款专注于 Telegram 群组与频道自动化管理的工具。随着产品持续发展,我们正在寻找真正了解 TGBot、愿意深入研究产品,并能够站在用户角度解决问题的社区运营人员。 💼 你将负责 • 负责 Telegram 群组及社区的日常运营与管理 • 深入了解并熟练掌握 TGBot 各项功能及使用场景 • 解答用户在使用 TGBot 过程中遇到的问题 • 引导新用户了解、使用 TGBot • 收集用户反馈、整理功能需求,并与产品团队同步 • 主动发现用户在使用过程中遇到的问题,并推动解决 • 协助社区活动、内容及日常运营工作 • 关注用户体验、社区活跃度及用户留存 🎯 我们希望你 • 熟悉 Telegram,或愿意投入时间深入了解 Telegram 生态 • 对 TGBot 各项功能感兴趣,能够主动学习并持续积累使用经验 • 具备良好的沟通能力、责…

❤23👍8🖕7

8 Sept 2026, 05:17 UTC≈14,700 views17 reactionsread 27 September 2026

Telegram全球多地出现故障 Telegram目前在全球多个国家和地区出现服务异常,大量用户反映无法正常发送消息、接收图片和视频,部分手机及电脑端一直显示“Connecting(连接中)”或“Updating(更新中)”。 据Downdetector监测,相关故障报告短时间内明显增加。目前Telegram尚未说明具体原因及恢复时间。

❤17

10 Jul 2026, 05:00 UTC≈52,200 views116 reactionsread 27 September 2026
Photo

功能更新|自动回复新增「正则模式」 为了让自动回复功能更加灵活、更加精准,TGBot 自动回复现已新增「正则模式」! 目前自动回复支持:精准模式、模糊模式、正则模式,可根据不同使用场景自由选择。 🔵 精准模式 消息内容与设置的关键词完全一致时,才会触发自动回复。 例如: 设置关键词:在吗 用户发送:在吗 ✅ 用户发送:你在吗 ❌ 🔵 模糊模式 消息内容中只要包含设置的关键词,即可触发自动回复。 例如: 设置关键词:价格 用户发送:价格多少 ✅ 用户发送:想问一下价格 ✅ 用户发送:这个价格怎么样 ✅ 🟣 正则模式|NEW 支持使用正则表达式编写更加灵活的匹配规则,一条规则即可覆盖多种消息格式和复杂场景。 例如可以实现: 📱 精准识别 11 位手机号 📦 匹配不同格式的订单号 📧 自动识别邮箱地址 💬 同时匹配「在吗」「在吗?」「在吗!」等不同写法 🚫 排除包含广告、推广等指定关键词的消息 🔤 灵活处理大小…

❤99⚡7🎉6😁3👎1

10 Jul 2026, 04:27 UTC≈36,900 views23 reactionsread 27 September 2026
Photo

功能更新|🕘支持自定义时区 🌍为了让全球用户拥有更准确的定时体验,TGBot 现已支持自定义时区设置! 无论您身处哪个国家或地区,都可以轻松设置属于自己的本地时间。 ✅ 功能介绍 📍 方式一:输入城市名称 输入城市名称即可自动匹配对应时区 无需手动计算 UTC 偏移 📍 方式二:发送位置 点击 📎 附件 → 位置 发送当前位置即可自动识别时区 ⚠️仅用于检测时区,不会保存您的位置信息 🌎 支持全球所有时区 支持 UTC±0 ~ UTC±14 完美兼容 印度(UTC+5:30)、尼泊尔(UTC+5:45)等特殊时区 满足全球用户使用需求 💡 适用场景 欢迎语定时 定时任务 定时关闭/开启功能 其他所有涉及时间的功能 从此,无需再手动换算 UTC,机器人将按照您的本地时间精准执行任务。 🎉 时区自定义功能现已上线,欢迎体验!

❤21💩2

26 Jun 2026, 08:02 UTC≈32,700 views21 reactionsread 27 September 2026

Posted without readable text

❤18💩2🥱1

6 Jun 2026, 06:31 UTC≈39,700 views40 reactionsread 27 September 2026
Photo

📢 关于定时广告不发送问题的说明 近期部分群组/频道出现定时广告未正常发送的情况,经排查发现,大多数情况是由于用于广告展示的会员表情符号(Emoji 合集)已失效或被删除导致。 请各位群主自行检查: 💡 检查方法 1. 打开【定时广告】设置 2. 点击【预览广告】 ✅ 如果能够正常看到预览广告内容 说明表情符号合集状态正常,无需处理。 ❌ 如果点击后没有显示预览广告内容 则说明广告文本中使用的会员表情符号已失效,需要重新编辑广告内容,将失效的会员表情符号删除或更换为新的会员表情符号。 ⚠️ 注意: 表情符号合集失效后,机器人将无法正常发送包含该表情符号的定时广告,因此会出现广告不发送、发送失败等情况。 请尽快完成检查,如发现失效请及时更新,以免影响广告正常投放。

❤34👍6

3 Jun 2026, 08:06 UTC≈34,100 views60 reactionsread 27 September 2026
Photo

📢 功能更新 机器人已取消默认 “签到” “活跃排名” 关键词,改为用户自定义指令别名,让每个群组都能按照自己的习惯设置命令。 如发送 “签到” “活跃排名” 无反应,请前往: 首页(欢迎页) └─ 设置群组 └─ 选择群组 └─ 群组命令 └─ 命令别名 └─ 修改 /sign_in(签到) └─ 修改 /stat(活跃排名) 你甚至可以根据群组文化创建专属称呼,让机器人更加有趣、更具个性化。 签到改成:打卡、报道、上班... 活跃排名改成:水群榜、话痨榜、贡献榜... ........ 同时也支持为以下命令设置自定义别名: /help(帮助) /link(邀请链接) /mute(禁言) /unmute(解除禁言) /ban(封禁) /unban(解除封禁) /info(用户信息) /points(增减积分) /clear(关闭底部键盘按钮) /cancel(取消操作) /kick(踢出成员) /link_sta…

❤34👎21👌3👏2

28 May 2026, 06:22 UTC≈30,200 views25 reactionsread 27 September 2026
Photo

【新增功能】|智能色情内容检测系统正式上线 为打造健康、纯净的社群交流环境,我们的群管机器人现已正式接入多维度智能色情内容检测模块。 ✅ 支持图片 / 视频 / GIF / 贴纸全格式识别 ✅ 4 档灵敏度可调,精准适配不同社群需求 ✅ 违规内容秒级处理,延迟删除 + 提示通知双重保障 💡 如何开启? 路径:设置群组 → 选择目标群组 → 色情检测 我们以技术为盾,为您的社群安全保驾护航,让交流更安心。

❤15👎9👍1

28 Mar 2026, 05:47 UTC≈57,300 views88 reactionsread 27 September 2026
Video

🔥 全能 Telegram 频道 & 群组管理机器人 🔥 想让你的 频道 & 群组 变得 更智能、更高效、更好玩? 试试@TGBot,24/7 自动管理,帮你省时省力!🚀 📢 频道管理功能 ✅ 定时消息 - 设定时间自动推送,还能置顶 & 循环发布! ✅ 频道同步 - 让多个频道 & 群组同时更新,不用手动复制粘贴! ✅ 自动按钮 - 让消息自带交互按钮,提升点击率! ✅ 修改按钮 - 已发布的消息按钮也能随时调整,无需重发! 👥 群组管理功能 ✅ 自动删除 - 自动清理进退群通知、头像修改、置顶提醒消息等! ✅ 进群欢迎 - 自定义文字+图片/视频+按钮,欢迎新成员! ✅ 自动回复 - 关键词触发智能回复,秒解答常见问题! ✅ AI反垃圾 - 自动拦截广告、马甲号、超长消息、@所有人等! ✅ 进群验证 - 数学题、验证码、按钮验证,拦截机器人 & 垃圾用户! ✅ 抽奖系统 - 关键词抽奖 & 积分抽奖,多种模式玩转互动!…

❤79👍5🔥3🥰1

5 Mar 2026, 23:31 UTC≈54,000 views73 reactionsread 27 September 2026
Photo

🥳【新增功能】 按钮背景色、按钮会员表情 1. 设置按钮背景色 按钮字符串最开头设置# +字母来设置背景色 #p 蓝色背景按钮 #g 绿色背景按钮 #r 红色背景按钮 举例红色背景按钮: #r按钮名称 - https://t.me/xxx 2. 设置按钮会员表情 按钮的第一个会员表情会显示到按钮中 举例: 😎按钮名称 - https://t.me/xxx

❤53👍7🔥5😎5🥰2🎉1

12 Feb 2026, 21:37 UTC≈51,100 views37 reactionsread 27 September 2026
Photo

💎 @NBot 会员专属版 💬 为什么选择 @NBot 会员版? ✅ 无广告 ✅ 仅会员可用(每个机器人会员是隔离的) ✅ 用户量少,响应更快 ✅ 专属功能持续更新 ✅ 优先更新及维护此版本 ⚠️注意:会员专属版机器人需在 @NBot 机器人内开通后才可使用。 免费版: 👉 @TGBot 👉 @QQQBot ✅ 我们的官方资源: 官网链接 / 主频道 / 官方群 / 机器人集合 / 抽奖频道

❤34🔥3

25 Jan 2026, 22:52 UTC≈45,600 views52 reactionsread 27 September 2026

Telegram Bot更新: 🤖机器人发送自定义表情符号规则变更 开发者发现 Telegram 调整了机器人使用高级表情符号(Premium Emoji)的逻辑: 此前机器人需绑定 NFT 用户名才能发送自定义表情符号(最开始绑定费用 5000 TON,后降至 1000 TON)。现在起,只要机器人是由开通 Telegram Premium 的账号创建(创建者账号开通了会员),就可以直接发送高级表情符号;若创建者账号无 Premium,则无法使用。此功能与机器人是否绑定 NFT 用户名无关。 ⚠️ 注意:高级表情符号在 Inline(内联) 模式下不可用,机器人也无法添加自定义 Reaction(除非 Bot API 明确支持) Telegram 官方尚未回应,后续规则可能调整。 补充内容:此类机器人无法在频道内使用机器人发送自定义表情

❤35😢6👍4🤡4🔥2👎1

Showing the 12 most recent of 22 posts we hold for @mybots. 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.

Mentions

Named by 9 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.

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 27 September 2026 — this entry's latest reading, not the date you are reading this.

“TGBot News” (@mybots), 26,947 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/mybots.

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.