Telegram RegisterThe public register of Telegram
Telegram profile photo for Dxa Bypass

Bot

Dxa Bypass

@DeltaAzureScriptsbot

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

21,968monthly users

-3,408 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8048640103
TypeBot
Username@DeltaAzureScriptsbot
First recorded15 August 2026
Last confirmed live25 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/DeltaAzureScriptsbot

Growth

21,96825,37623,6727 August 2026 — 25,376 monthly users9 August 2026 — 25,237 monthly users11 August 2026 — 24,637 monthly users12 August 2026 — 24,457 monthly users15 August 2026 — 24,457 monthly users15 August 2026 — 24,012 monthly users17 August 2026 — 23,115 monthly users19 August 2026 — 22,883 monthly users21 August 2026 — 22,572 monthly users22 August 2026 — 22,317 monthly users25 August 2026 — 21,968 monthly users7 August 202625 August 2026
11 measurements spanning 18 days, net -3,408. 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 21,457–25,887 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
25 Aug 2026, 11:2821,968-349
22 Aug 2026, 22:1822,317-255
21 Aug 2026, 15:0822,572-311
19 Aug 2026, 11:1522,883-232
17 Aug 2026, 09:2723,115-897
15 Aug 2026, 16:0524,012-445
15 Aug 2026, 16:0424,457no change
12 Aug 2026, 00:4224,457-180
11 Aug 2026, 03:5624,637-600
9 Aug 2026, 01:1125,237-139
7 Aug 2026, 18:4525,376first 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“Dxa Bypass” (@DeltaAzureScriptsbot), 21,968 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/DeltaAzureScriptsbot.

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.