Telegram RegisterThe public register of Telegram

Bot

ArxBypass

@OrxBypass_bot

On this record: Growth · Engagement · Citations · Cite this entry

59,670monthly users

-723 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID7735617708
TypeBot
Username@OrxBypass_bot
First recorded11 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/OrxBypass_bot

Growth

59,67060,63360,151.57 August 2026 — 60,393 monthly users9 August 2026 — 60,633 monthly users9 August 2026 — 60,605 monthly users11 August 2026 — 60,426 monthly users11 August 2026 — 60,426 monthly users12 August 2026 — 60,201 monthly users13 August 2026 — 60,008 monthly users14 August 2026 — 59,670 monthly users7 August 202614 August 2026
8 measurements spanning 7 days, net -723. 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 59,526–60,777 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
14 Aug 2026, 10:2559,670-338
13 Aug 2026, 05:1860,008-193
12 Aug 2026, 01:5360,201-225
11 Aug 2026, 19:0760,426no change
11 Aug 2026, 00:5460,426-179
9 Aug 2026, 21:2160,605-28
9 Aug 2026, 00:5060,633+240
7 Aug 2026, 18:1560,393first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 3 registered channels — 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.

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

“ArxBypass” (@OrxBypass_bot), 59,670 monthly users as measured 14 August 2026. Telegram Register, tgregister.com/channel/OrxBypass_bot.

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.