Telegram RegisterThe public register of Telegram

Channel

Nexus Riot Guide

@Nexus_riot

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

705subscribers

+0 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-1002065146117
TypeChannel
Username@Nexus_riot
DescriptionAnother guide to clone Nexus Search bot
CreatedBetween 1 November 2023 and 24 February 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Nexus_riot

Growth

7057 Aug 2026, 17:31 — 705 subscribers8 Aug 2026, 02:18 — 705 subscribers7 Aug 2026, 17:318 Aug 2026, 02:18
2 measurements taken within a single day. 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 704–706 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 02:18705no change
7 Aug 2026, 17:31705first reading

Engagement

11 posts held, back to 24 February 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 11 posts for this entry, the most recent from 8 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
5

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

Reaction mix

62 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 45.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2845.2%
1625.8%
🔥914.5%
23.23%
👎23.23%
😁23.23%
🤔23.23%
🤨11.61%

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 9 of the 11 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 62reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 24 February 2024 to 8 February 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

8 Feb 2026, 17:30 UTC830 views11 reactionsread 8 August 2026

New commands added to Nexus search bot: - /bots: List of the bots made available for public use by the cloners - /mybots: List of bots you have cloned - /bot_public: To set your bot either for private use or for public use. Syntax to set bot: For public use: /bot_public on or /bot_public @YourBotUsername on For private use (default when cloning): /bot_public off or

🔥82👍1

31 Dec 2025, 04:47 UTC≈1,860 views7 reactionsread 8 August 2026

Reminders to bot cloners: 1) From time to time, please check if your cloned bot is functional and responsive. 2) If the bot is unresponsive, please repeat Step 13 from the guide above to make the bot work again. 2.1) If no longer managing the bot, consider deleting your bot in BotFather and freeing the bot username.

👍7

21 Jul 2025, 00:35 UTC≈3,160 views8 reactionsread 8 August 2026

SEARCH BOT'S OPERATION STATUS ✅ In operation ✅ Note: This status is not endorsed by Nexus.

👍5👎21

21 Feb 2025, 18:04 UTC≈4,190 views17 reactionsread 8 August 2026

Announcement: 1) Official bot and most of clones listed are blocked due to copyright infringement. 2) Clone your own to keep the search undisturbed.

👍132😁2

22 Dec 2024, 07:12 UTC≈4,180 views5 reactionsread 8 August 2026

Share here the Nexus Search bot that you clone and want to share ⚒️ Warning: Sharing your bot increases the risk of your bot being reported and blocked in the future.

5

19 Mar 2024, 22:59 UTC≈4,080 views0 reactionsread 8 August 2026

To the top of this guide: Top of Guide To the top of this guide while using browser: Top of Guide

24 Feb 2024, 07:15 UTC≈3,930 views11 reactionsread 8 August 2026
File

CLONE A NEXUS BOT - RIOT (Continued) 12) In the original bot 13) Type and send (on 1 line and without the angle brackets): /riot @YourBotUsername <your_api_id> <your_api_hash> 14) Wait a few minutes and the cloned bot is ready to use. DONE

7👍2🔥1🤨1

24 Feb 2024, 07:13 UTC≈3,350 views3 reactionsread 8 August 2026
File

CLONE A NEXUS BOT - RIOT (Continued) 9) Go to the original bot 10) Follow the new instruction 11) Follow the guide hyperlink 11.1) Follow the guide here Note: - If you have cloned a bot before, skip to Step 12. Re-use your api_id and api_hash from the previous cloning process. Notes for Step 11: - For "Short name" in the form, fill in a name with the username's restrictions. (To Be Continued)

🤔21

24 Feb 2024, 07:11 UTC≈2,610 viewsread 8 August 2026

CLONE A NEXUS BOT - RIOT (Continued) (Optional) O.1) In @BotFather O.2) Type and send /setdescription O.3) Provide bot description O.4) Type and send /setabouttext O.5) Provide bot about text O.6) Type and send /setcommands O.7) Provide bot commands Notes for Steps O.6 and O.7: - These two steps are to create a menu of commands for quick selection. Not compulsory to set them. - Commands are provided by Nexus; copy

Showing the 11 most recent of 11 posts we hold for @Nexus_riot. 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.

Citation-graph rank

Citation-graph rank — 1,012,240 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“Nexus Riot Guide” (@Nexus_riot), 705 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Nexus_riot.

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.