Telegram RegisterThe public register of Telegram
Telegram profile photo for ArxBypass

Bot

ArxBypass

@OrxBypass_bot

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

53,113monthly users

-7,280 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 live18 November 2026
Measurements held54
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/OrxBypass_bot

Topic

Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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 the other topics.

Growth

53,04463,12758,085.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 users17 August 2026 — 58,659 monthly users18 August 2026 — 58,568 monthly users20 August 2026 — 58,573 monthly users21 August 2026 — 58,669 monthly users22 August 2026 — 58,611 monthly users24 August 2026 — 58,523 monthly users27 August 2026 — 58,096 monthly users29 August 2026 — 57,582 monthly users30 August 2026 — 57,754 monthly users31 August 2026 — 57,699 monthly users1 September 2026 — 57,978 monthly users2 September 2026 — 58,153 monthly users5 September 2026 — 57,268 monthly users8 September 2026 — 59,017 monthly users11 September 2026 — 57,413 monthly users13 September 2026 — 59,487 monthly users14 September 2026 — 59,893 monthly users16 September 2026 — 60,890 monthly users18 September 2026 — 60,774 monthly users25 September 2026 — 60,503 monthly users3 October 2026 — 60,382 monthly users8 October 2026 — 63,127 monthly users12 October 2026 — 62,687 monthly users14 October 2026 — 61,744 monthly users15 October 2026 — 60,927 monthly users17 October 2026 — 58,811 monthly users18 October 2026 — 58,620 monthly users19 October 2026 — 59,425 monthly users20 October 2026 — 59,789 monthly users23 October 2026 — 59,367 monthly users24 October 2026 — 59,224 monthly users25 October 2026 — 59,342 monthly users27 October 2026 — 60,262 monthly users28 October 2026 — 60,315 monthly users29 October 2026 — 60,268 monthly users30 October 2026 — 58,863 monthly users31 October 2026 — 58,423 monthly users2 November 2026 — 58,329 monthly users3 November 2026 — 58,597 monthly users6 November 2026 — 57,022 monthly users7 November 2026 — 55,828 monthly users8 November 2026 — 55,753 monthly users10 November 2026 — 55,837 monthly users12 November 2026 — 55,091 monthly users15 November 2026 — 53,044 monthly users18 November 2026 — 53,113 monthly users53,1137 August 202618 November 2026
54 measurements spanning 103 days, net -7,280. 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 51,532–64,639 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 54
Measured (UTC)Monthly usersChange
18 Nov 2026, 15:3653,113+69
15 Nov 2026, 13:2053,044-2,047
12 Nov 2026, 03:5055,091-746
10 Nov 2026, 07:5055,837+84
8 Nov 2026, 17:0055,753-75
7 Nov 2026, 09:2655,828-1,194
6 Nov 2026, 07:0857,022-1,575
3 Nov 2026, 01:4458,597+268
2 Nov 2026, 02:3158,329-94
31 Oct 2026, 03:0558,423-440
30 Oct 2026, 04:2058,863-1,405
29 Oct 2026, 06:3660,268-47
28 Oct 2026, 01:4960,315+53
27 Oct 2026, 03:0960,262+920
25 Oct 2026, 04:1759,342+118
24 Oct 2026, 05:3859,224-143
23 Oct 2026, 02:0959,367-422
20 Oct 2026, 19:0959,789+364
19 Oct 2026, 16:1059,425+805
18 Oct 2026, 13:1858,620first 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 18 November 2026 — this entry's latest reading, not the date you are reading this.

“ArxBypass” (@OrxBypass_bot), 53,113 monthly users as measured 18 November 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.