21 Jul 2025, 00:36 UTC299 views0 reactionsread 10 August 2026
搜索机器人的运行状态 ✅ 正常运行 ✅ 注意：此状态尚未得到 Nexus 的确认。
Channel
Nexus Riot 指南
@Nexus_Riot_ZhiNan
On this record: Growth · Engagement · Posts · Citations · Cite this entry
72subscribers
+2 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 | -1002355181987 |
|---|---|
| Type | Channel |
| Username | @Nexus_Riot_ZhiNan |
| Created | Between 1 September 2024 and 25 February 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 14 September 2026 |
| On Telegram | t.me/Nexus_Riot_ZhiNan |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 07:55 | 72 | +1 |
| 23 Aug 2026, 10:04 | 71 | +1 |
| 10 Aug 2026, 00:01 | 70 | no change |
| 7 Aug 2026, 17:31 | 70 | first reading |
Engagement
10 posts held, back to 25 February 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 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 10 posts for this entry, the most recent from 21 July 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
25 Feb 2025, 08:35 UTC420 viewsread 10 August 2026
在此分享您克隆并想要分享的 Nexus 搜索机器人 ⚒️ 警告：共享您的机器人会增加您的机器人将来被举报和阻止的风险。
25 Feb 2025, 07:29 UTC418 viewsread 10 August 2026
返回本指南顶部：本指南的顶部 在浏览器中返回本指南顶部：本指南的顶部
25 Feb 2025, 07:26 UTC390 views0 reactionsread 10 August 2026
File
克隆 NEXUS 机器人 - RIOT （续） 12）进入原始机器人 13）发送（在一行内且没有尖括号）: /riot @您的_机器人_用户名 <您的_api_id> <您的_api_hash> 14）只需等待几分钟，直到您的克隆机器人变得可以正常使用。 完成了
25 Feb 2025, 07:24 UTC326 views0 reactionsread 10 August 2026
File
克隆 NEXUS 机器人 - RIOT （续） 9）进入原始机器人 10）按照这些指示操作 11）按照指南中的超链接操作 11.1）按照这里的指示操作 笔记： - 如果您之前已经克隆过机器人，请跳至步骤 12。使用上一个克隆过程中的 api_id 和 api_hash。 步骤 11 的笔记： - 要获取 <api_id> 和 <api_hash> 的值，请在 https://my.telegram.org 上登录，进入“API development tools”部分并填写以下表格。 - 在表格中的“App title”字段中，输入应用程序的名称。它可以是任何名称，但必须使用拉丁字母。 - 在表格中的“Short name”字段中，输入名称。您可以选择任何名称，但它必须使用拉丁字母、0-9、下划线，并且不能包含空格。 （未完待续）
25 Feb 2025, 07:22 UTC251 viewsread 10 August 2026
File
发送命令 /setdescription
25 Feb 2025, 07:21 UTC244 viewsread 10 August 2026
克隆 NEXUS 机器人 - RIOT （续）（可选） 可。1）进入 @BotFather 机器人 可。2）发送命令 /setdescription 可。3）提供机器人的描述 可。4）发送命令 /setabouttext 可。5）提供机器人的信息 可。6）发送命令 /setcommands 可。7）提供机器人的命令 步骤 可。6 和 可。7 的笔记： - 这两个步骤用于创建快速选择的命令菜单，设置不是必需的。 - 命令由 Nexus 提供；请从原始机器人中的 /help 和 /help_expert 复制并粘贴；伪造的命令将无法工作。 - 命令的描述可以从原始机器人中的 /help 和 /help_expert 复制并粘贴；您也可以进行个性化描述（例如，翻译描述成其他语言）。 （未完待续）
25 Feb 2025, 07:20 UTC227 viewsread 10 August 2026
File
发送命令 /newbot
25 Feb 2025, 07:20 UTC211 viewsread 10 August 2026
克隆 NEXUS 机器人 - RIOT （续） 4）使用 @BotFather 机器人 5）发送命令 /newbot 6）提供您的 Nexus 机器人克隆名称 您可以选择任何名称。 7）提供您的 Nexus 机器人克隆用户名 您可以选择任何用户名，但它必须使用拉丁字母、0-9、下划线，不能包含空格，并且必须以 bot 结尾。 7.1）如果 @BotFather 回复 "Sorry..."（表示用户名已被占用），请重新想一个名字并在下一条消息中提供。 8）当您向 @BotFather 提供了正确的名称和用户名后，它将回复 "Done!..." 的消息。请将该消息转发给原始机器人。 （未完待续）
25 Feb 2025, 07:19 UTC208 viewsread 10 August 2026
File
输入并发送 /riot
Showing the 10 most recent of 10 posts we hold for @Nexus_Riot_ZhiNan. 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 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Nexus Riot 指南” (@Nexus_Riot_ZhiNan), 72 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/Nexus_Riot_ZhiNan.
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.