Telegram RegisterThe public register of Telegram
Telegram profile photo for 无矢机器人

Channel

无矢机器人

@NPDev

On this record: Topic · Growth · Engagement · Posts · Polls · Cite this entry

60subscribers

-3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001158729862
TypeChannel
Username@NPDev
CreatedBetween 1 March 2018 and 24 August 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live2 October 2026
Measurements held5
Confirmed unchanged3 times, most recently 2 October 2026
On Telegramt.me/NPDev

Topic

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 28 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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

606361.57 August 2026 — 63 subscribers10 August 2026 — 63 subscribers14 August 2026 — 62 subscribers23 August 2026 — 61 subscribers5 September 2026 — 60 subscribers7 August 20265 September 2026
5 measurements spanning 29 days, net -3. 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 60–63 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 00:2160-1
23 Aug 2026, 05:5661-1
14 Aug 2026, 23:1462-1
10 Aug 2026, 03:3163no change
7 Aug 2026, 01:1363first reading

Engagement

19 posts held, back to 24 August 2020 — 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 19 posts for this entry, the most recent from 22 December 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Dec 2022, 09:45 UTC≈1,730 viewsread 10 August 2026

#公告 #CNSecurity 安全保卫局出现故障,暂时下线。

26 Feb 2022, 14:46 UTC≈2,190 viewsread 10 August 2026

#公告 部分机器人所在机房遭遇网络故障,请等待修复。

13 Dec 2021, 04:00 UTC≈2,310 viewsread 10 August 2026

#CNOstra #公告 由于官方 API 变动,@CNOstraBot 进行了更新。此次更新不兼容旧版本,因此,群内活跃度将重新统计。

18 May 2021, 08:28 UTC≈2,610 viewsread 10 August 2026

#CNSecret #公告 @CNSecretBot 上线,功能为对群内单个账户的消息设置定时自动销毁。 项目地址:https://github.com/NullPointerMaker/telegram_cn_secret_bot

12 Nov 2020, 09:14 UTC≈2,130 viewsread 10 August 2026

#CNSecurity #公告 @CNSecurityBot 正在内测,目前仅实现了链接防跟踪模块。源代码和和可执行文件将在完整的正式版发布时释出。 项目秉承“匿名才安全”的理念,旨在保护用户的隐私安全和信息安全不被泄露和渗透,这对于翻墙者尤为重要。 很多网站为了精准投放广告,会对用户进行追踪,所使用的技术包括 UTM 参数、Cookie、IP 等。这对用户的隐私安全造成一定隐患(所谓“大数据”)。链接防跟踪模块的作用就是检测乃至去除链接中可疑的 UTM 参数如用户标识、访问标识、时间戳等隐私信息,只保留必要信息,斩断追踪链。 对于 Cookie 和 IP 追踪,依据项目的建议通过代理软件使用浏览器 InPrivate 隐私模式即可防护。 项目主要服务于中文用户,因此所收录的也主要是中文用户经常访问的网站。 另外,项目为了自我保护,是通过 Tor 网络来探测目标网站的,这经常会被防火墙阻断。因此对于墙内网站的探测时常没有结果,会…

11 Nov 2020, 15:21 UTC≈1,760 viewsread 10 August 2026
File

#CNOstra #更新 #源代码 项目迁移至 Maven 管理。 添加自动置顶功能,投票结束后自动解除置顶。

11 Oct 2020, 13:37 UTC≈1,380 viewsread 10 August 2026
File

#CNArchive #更新 #源代码 #可执行文件 修复重复打开数据库的错误。

11 Oct 2020, 13:27 UTC≈1,270 viewsread 10 August 2026
File

#CNOstra #更新 #源代码 #可执行文件 兼容匿名账户。

4 Oct 2020, 17:42 UTC≈2,020 viewsread 10 August 2026
File

#CNOstra #更新 #源代码 #可执行文件 修复可举报机器人的漏洞。

3 Oct 2020, 14:52 UTC960 viewsread 10 August 2026
File

#CNOstra #更新 #源代码 #可执行文件 修复无法处罚从未发言的举报者的故障。

13 Sept 2020, 09:57 UTC942 viewsread 10 August 2026
File

#CNOstra #更新 #源代码 #可执行文件 根据 https://t.me/NPDev/7 投票结果添加管理员查询功能。 具体使用方法是:对想要查询的投票回复 /query 指令。

31 Aug 2020, 16:25 UTC895 viewsread 10 August 2026
File

#CNOstra #更新 #源代码 #可执行文件 修复判罚后仍有投票权的漏洞。

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

24 Aug 2020, 05:24 UTCFinal Results7 voters

CNOstra的追诉时效?请谨慎考虑,延长时效既可对较早的破坏者进行打击,但也方便了破坏者趁无人时进行破坏。

  1. 可举报3小时内消息29%
  2. 可举报6小时内消息0%
  3. 可举报12小时内消息14%
  4. 可举报24小时内消息29%
  5. 可举报48小时内消息0%
  6. 可举报72小时内消息14%
  7. 可举报168小时内消息14%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 19 most recent posts we hold, published 24 August 2020 to 22 December 2022. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“无矢机器人” (@NPDev), 60 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/NPDev.

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.