Channel
@KinhRoBotChannel
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
8,840subscribers
-57 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001639912263 |
|---|---|
| Type | Channel |
| Username | @KinhRoBotChannel |
| 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 | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/KinhRoBotChannel |
Technology — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 18 Sept 2026, 12:17 | 8,840 | -7 |
| 13 Sept 2026, 19:56 | 8,847 | -13 |
| 9 Sept 2026, 19:18 | 8,860 | +11 |
| 4 Sept 2026, 08:22 | 8,849 | -16 |
| 1 Sept 2026, 02:05 | 8,865 | -11 |
| 28 Aug 2026, 19:59 | 8,876 | -1 |
| 26 Aug 2026, 03:56 | 8,877 | +3 |
| 22 Aug 2026, 23:14 | 8,874 | -5 |
| 19 Aug 2026, 19:08 | 8,879 | -13 |
| 16 Aug 2026, 20:45 | 8,892 | -9 |
| 13 Aug 2026, 15:26 | 8,901 | +6 |
| 10 Aug 2026, 17:51 | 8,895 | -3 |
| 7 Aug 2026, 13:38 | 8,898 | +1 |
| 7 Aug 2026, 11:15 | 8,897 | no change |
| 7 Aug 2026, 11:03 | 8,897 | first reading |
18 posts held, back to 23 March 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 30 pages 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 18 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.
我们又又又又又又又又又又又鸽了~~~ 因为临时途中我们想要“合规化” https://t.me/KinhRoBotGroup/106047 然后导致我们的受众用户必须从亚洲转向全地，导致我们要做多语言支持导致我们的进度缓慢，所以小小小小小小小小小鸽~~~ 支持的语言： 英语、简体中文、繁体中文、日语、韩语、西班牙语、法语、俄语、阿拉伯语（反着写太麻烦了，砍了，等开源i18n文件让社区自己适配吧） 实时进度： 资产分割 完成 非盈利基金会 注册中 用于私有化AI的DGX算力托管 完成 V2 开发中 分布式TDLib 完成 分布式注册机 完成 分布式一致网关 完成 分布式负载路由器 完成 无状态业务逻辑 开发中 分布式WebAPI 开发中 V2 搭建与部署 等待中 社区生态 等待中 V1数据迁移V2 等待中 V1开源 等待中
刚刚看了下其他机器人，本来想看看他们有什么新功能。发现好多功能都要钱？！有的免费功能还有限制？！例如超过12条规则就要订阅？！ 细看功能实际上我们都已经实现了，而且我们没有限制，也不要钱。 我们目前已经开始重写了，我们将增加更多实用有趣的功能。并且我们采购两台DGX用来专门做广告识别和AI对话，我们将始终把数据留存在我们本地进行处理，拒绝像某些机器人发送到云厂商，这很有可能会泄露隐私。 我们将始终保持免费，因为我们是非盈利组织。
由于现在机器人太灵车了，我们决定现在开始重写。 如果一切顺利，本月内我们将上线V2版本将带来全新的体验跟最现代化的功能，同时我们不会丢失全TG最快响应机器人的称号，对广告识别也有新的模型与人工审核团队。 另外我们说下重点：可以部署自己的机器人到我们这。 以上所说的一切通通免费。
群组验证API传递的参数与签名方法如图所示 签名验证公钥 958c88f202082152addd41c3a91784b8744fad69f16133513bbb46fa42b6d79d 懒得写文档，自己看原码吧
目前机器人的代码已经无法在继续维护和提升扩展性。我们已经计划对机器人进行整体重构，但我们还未计划开始时间。 这个过程不会太久预计1~2周即可重构完成。网页控制台将更现代化，机器人可以随意克隆。
群验证消息无法自动删除的神秘BUG，我们已经在路由层面强制控制5分钟内删除。该问题应该已经彻底解决。
Posted without readable text
群验证信息时不时无法自动删除的历史问题已解决。 原因是机器人性能太高，tdlib处理不过来，一直报错：Too Many Requests 🤡
/kick 更新，指令更加人性化
垃圾信息模型已更新，欢迎使用 /sb 上报数据
我们是非盈利机构
请注意！如果群组创建者没有开放特定功能权限，机器人也没权限开启这些功能的权限，这会导致权限调整报错！例如上图所示。
Showing the 12 most recent of 18 posts we hold for @KinhRoBotChannel. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 1 seed channel's Telegram-generated recommendation list 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“KinhRoBot频道” (@KinhRoBotChannel), 8,840 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/KinhRoBotChannel.
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.