Telegram RegisterThe public register of Telegram
Telegram profile photo for 🏎️ DJARB VPN - BOT

Bot

🏎️ DJARB VPN - BOT

@DJARBVPNBOT

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

148,656monthly users

+37,928 since we began measuring on 7 August 2026

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

Register entry

Telegram ID7238514355
TypeBot
Username@DJARBVPNBOT
First recorded9 August 2026
Last confirmed live14 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/DJARBVPNBOT

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 76% 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

110,067174,847142,4577 August 2026 — 110,728 monthly users8 August 2026 — 110,067 monthly users9 August 2026 — 110,067 monthly users10 August 2026 — 112,709 monthly users11 August 2026 — 113,733 monthly users12 August 2026 — 116,740 monthly users14 August 2026 — 118,804 monthly users15 August 2026 — 119,504 monthly users18 August 2026 — 120,038 monthly users19 August 2026 — 120,774 monthly users20 August 2026 — 121,581 monthly users22 August 2026 — 121,208 monthly users24 August 2026 — 120,119 monthly users25 August 2026 — 121,059 monthly users26 August 2026 — 121,288 monthly users27 August 2026 — 119,354 monthly users28 August 2026 — 120,021 monthly users29 August 2026 — 122,172 monthly users30 August 2026 — 124,929 monthly users31 August 2026 — 123,626 monthly users1 September 2026 — 123,554 monthly users2 September 2026 — 125,797 monthly users3 September 2026 — 127,202 monthly users5 September 2026 — 129,242 monthly users8 September 2026 — 130,102 monthly users11 September 2026 — 131,785 monthly users14 September 2026 — 130,910 monthly users16 September 2026 — 134,757 monthly users19 September 2026 — 144,946 monthly users25 September 2026 — 155,749 monthly users4 October 2026 — 169,155 monthly users8 October 2026 — 174,847 monthly users13 October 2026 — 173,097 monthly users14 October 2026 — 173,300 monthly users16 October 2026 — 171,489 monthly users17 October 2026 — 171,270 monthly users19 October 2026 — 169,286 monthly users20 October 2026 — 161,933 monthly users21 October 2026 — 158,395 monthly users23 October 2026 — 158,785 monthly users24 October 2026 — 157,980 monthly users25 October 2026 — 163,136 monthly users26 October 2026 — 163,590 monthly users27 October 2026 — 160,461 monthly users29 October 2026 — 161,512 monthly users30 October 2026 — 161,124 monthly users31 October 2026 — 160,036 monthly users1 November 2026 — 153,896 monthly users2 November 2026 — 154,022 monthly users3 November 2026 — 145,707 monthly users4 November 2026 — 143,999 monthly users6 November 2026 — 147,320 monthly users8 November 2026 — 151,449 monthly users10 November 2026 — 150,996 monthly users11 November 2026 — 150,684 monthly users14 November 2026 — 148,656 monthly users148,6567 August 202614 November 2026
56 measurements spanning 100 days, net +37,928. 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 100,350–184,564 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 56
Measured (UTC)Monthly usersChange
14 Nov 2026, 23:01148,656-2,028
11 Nov 2026, 21:44150,684-312
10 Nov 2026, 02:28150,996-453
8 Nov 2026, 13:49151,449+4,129
6 Nov 2026, 10:46147,320+3,321
4 Nov 2026, 16:25143,999-1,708
3 Nov 2026, 16:57145,707-8,315
2 Nov 2026, 17:59154,022+126
1 Nov 2026, 18:49153,896-6,140
31 Oct 2026, 16:46160,036-1,088
30 Oct 2026, 15:30161,124-388
29 Oct 2026, 15:54161,512+1,051
27 Oct 2026, 17:06160,461-3,129
26 Oct 2026, 19:39163,590+454
25 Oct 2026, 17:05163,136+5,156
24 Oct 2026, 18:18157,980-805
23 Oct 2026, 20:27158,785+390
21 Oct 2026, 16:45158,395-3,538
20 Oct 2026, 12:11161,933-7,353
19 Oct 2026, 15:26169,286first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 13 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 November 2026 — this entry's latest reading, not the date you are reading this.

“🏎️ DJARB VPN - BOT” (@DJARBVPNBOT), 148,656 monthly users as measured 14 November 2026. Telegram Register, tgregister.com/channel/DJARBVPNBOT.

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.