12 Mar 2025, 03:14 UTCviews —
托尔酱的 Captcha 更新&状态发布 pinned «因Contabo 续费已停止，目前所有机器人均已停止服务，因本人时间有限，且 pyrogram 项目已停止开发，因此本 bot 也将无限期停止服务。»
Channel
托尔酱的 Captcha 更新&状态发布
@toorucaptcha_news
On this record: Growth · Engagement · Posts · Citations · Cite this entry
101subscribers
+1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001273973510 |
|---|---|
| Type | Channel |
| Username | @toorucaptcha_news |
| Created | Between 1 March 2018 and 2 February 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 4 times, most recently 19 September 2026 |
| On Telegram | t.me/toorucaptcha_news |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 22:33 | 101 | +2 |
| 17 Aug 2026, 13:58 | 99 | -1 |
| 9 Aug 2026, 10:46 | 100 | no change |
| 9 Aug 2026, 09:17 | 100 | first reading |
Engagement
20 posts held, back to 2 February 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 20 posts for this entry, the most recent from 12 March 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
12 Mar 2025, 03:14 UTC≈3,270 viewsread 9 August 2026
因Contabo 续费已停止，目前所有机器人均已停止服务，因本人时间有限，且 pyrogram 项目已停止开发，因此本 bot 也将无限期停止服务。
3 May 2022, 13:39 UTC≈2,610 viewsread 9 August 2026
Forwarded from @TooruchanNews
Tooruchan's Captcha Bot 更新至 DX 2022 ver.CH-1.20 更新日志： 1. 修正代码与引用以适配 Pyrogram v2.x 2. 修正部分文本与字串 3. 部分 bug 修复 若在使用或者过程中遇到问题，请在本条消息或者 GitHub 仓库留言（不保证及时处理）。
24 Jan 2022, 12:18 UTC≈4,570 viewsread 9 August 2026
感谢 @NewlearnerChannel 频道主指出代码 bug，紧急更新 CH-1.10A 版本。 更新日志： 修复了由于 Pyrogram 乱改方法名导致超时踢出无法正常工作且无法正常定时清理消息的 bug。
24 Jan 2022, 09:46 UTC≈2,100 viewsread 9 August 2026
维护结束。
24 Jan 2022, 09:43 UTC≈4,010 viewsread 9 August 2026
https://github.com/Tooruchan/Telegram-CAPTCHA-bot-pyrogram Telegram CAPTCHA bot DX 2021 ver CH-1.10 已发布。 更新日志： 1. 修复两处由于 Pyrogram 更新导致的认证通过后无法自动解开禁言的恶性 bug。 2. 正式兼容 Pyrogram v1.3，修复了 Unsupported Users 的问题。
24 Jan 2022, 09:30 UTC≈3,410 viewsread 9 August 2026
https://docs.pyrogram.org/releases/v1.3 Pyrogram v1.3 已正式发布，我们正在对现行机器人进行迁移，在此期间机器人将无法正确处理加群请求。
23 Sept 2021, 01:53 UTCviews —
托尔酱的 Captcha 更新&状态发布 pinned «机器人现在无需申请白名单即可正常使用。»
23 Sept 2021, 01:53 UTC≈3,670 viewsread 9 August 2026
机器人现在无需申请白名单即可正常使用。
13 Aug 2021, 04:31 UTCviews —
托尔酱的 Captcha 更新&状态发布 pinned «重新部署的机器人现在已恢复正常工作，使用的仍然是 @toorucaptchabot 这一用户名，如需申请使用，请在下一推送的评论区下回复以下信息（允许回复多条）以便管理员能够手动将您的群组加入白名单。 1. 带有群组头像和群组名称的截图 2. 能够证明你在该群组拥有“封禁用户”和“添加管理员”这两项管理权限的截图 3. 你想使用 Bot 的群组 ID，格式一般为 -100 开头的一串数字 需要注意的是，若群组存在违反 ToS 的情况，你和你的群组很有可能无法获得白名单。»
5 Aug 2021, 06:00 UTC≈1,870 viewsread 9 August 2026
现在你可以在这条消息下回复相关信息。
5 Aug 2021, 05:59 UTC≈4,140 viewsread 9 August 2026
重新部署的机器人现在已恢复正常工作，使用的仍然是 @toorucaptchabot 这一用户名，如需申请使用，请在下一推送的评论区下回复以下信息（允许回复多条）以便管理员能够手动将您的群组加入白名单。 1. 带有群组头像和群组名称的截图 2. 能够证明你在该群组拥有“封禁用户”和“添加管理员”这两项管理权限的截图 3. 你想使用 Bot 的群组 ID，格式一般为 -100 开头的一串数字 需要注意的是，若群组存在违反 ToS 的情况，你和你的群组很有可能无法获得白名单。
Showing the 12 most recent of 20 posts we hold for @toorucaptcha_news. 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.
Forward network
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.
Mentions
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“托尔酱的 Captcha 更新&状态发布” (@toorucaptcha_news), 101 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/toorucaptcha_news.
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.