Channel
@dopraxcloud
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
2,456subscribers
+22 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001435432498 |
|---|---|
| Type | Channel |
| Username | @dopraxcloud |
| Created | Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/dopraxcloud |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 07:04 | 2,456 | +2 |
| 24 Aug 2026, 12:04 | 2,454 | +7 |
| 20 Aug 2026, 16:56 | 2,447 | -1 |
| 17 Aug 2026, 11:58 | 2,448 | +9 |
| 14 Aug 2026, 05:47 | 2,439 | -3 |
| 11 Aug 2026, 06:08 | 2,442 | +8 |
| 7 Aug 2026, 21:00 | 2,434 | no change |
| 7 Aug 2026, 20:56 | 2,434 | first reading |
20 posts held, back to 5 May 2026 — the 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (5 May 2026 – 5 August 2026) |
| Views total | 2,266 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 21:00 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Cloudflare launched a new product yesterday. It's called Cloudflare Wallets, and it's built for AI agents (not people). The idea: AI agents need a way to pay for things on their own. An API call, a piece of data, access to gated content. Right now an agent hits a login page built for humans and just stops. Cloudflare wants to fix that with wallets agents can use directly. Two wallet types exist. Account Wallets are…
Ubuntu, Debian, or Fedora for your next server? The answer depends on what you're optimizing for. → Ubuntu Server: widest docs and compatibility, 5 years of support, the safe default → Debian Server: leanest base, no Snap, ideal for small VMs running one or two services → Fedora Server: newest packages, but a ~13 month clock before you need to upgrade → AlmaLinux / Rocky Linux: RHEL-compatible, ~10 year lifecycle, n…
Running your own V2Ray server is only half the setup. The other half is getting your phone or laptop to actually use it. If you're on iPhone or Mac, V2Box is a clean way to do that. Scan a QR code from your panel, tap connect, done. → Works with VMess, VLESS, and Trojan → Supports Reality and uTLS on the client side → Merges Wi-Fi and cellular for a more stable connection → Can share the tunnel locally over SOCKS5/…
Claude Code & Your VM: When It’s Especially Useful Some server tasks are faster to do by hand. Others are easier if you let Claude Code do them for you. IIf you run WireGuard, 3x-ui, or Marzban, you'll hit the second case more often than you think: → Two inbounds look the same. One works, one doesn't. Instead of checking both by hand, ask Claude Code to compare the configs and the logs. → Some WireGuard peers have…
Good news! We’ve been improving our infrastructure quality and IP availability. What’s new: 1. We’re doubling down on internal IP monitoring to ensure that any IPs assigned to servers are fully functional. 2. There’s now a full new IP range on Hetzner. Recent updates have reduced IP-related issues significantly, and we are working closely with our infrastructure partners to further improve reliability and connec…
How to spot a fake VPN Free VPN apps make one promise: your traffic stays private. But can you trust just about any third-party VPN provider? Running servers costs money. If the app is free and has no published audit, someone else is paying for your data. Check these five things before you install a VPN app: 1. Is there a real audit from an outside company? Or just a claim? 2. Can you find the company behind th…
If you connect your locally running Claude Code to a Doprax VM, you can use plain language to control any processes running on it. For example: → "Add a WireGuard peer for my phone" and get the config back in the same message. → "Check how many users are live on 3x-ui" instead of opening the panel. → "Restart the Marzban node and confirm the API's back up" while you do something else. → "Something's wrong with nginx…
3x-ui or Marzban? People argue features, but those barely differ. Both run on Xray-core, both do VLESS and Reality, both give you a dashboard, traffic stats, and a Telegram bot. The real question is: how many users are you serving? One server and a handful of users, run 3x-ui. It's a single Go binary, light on memory, up in minutes, and simple enough that you won't fight it. Many users, or servers in more than on…
Psiphon Conduit can be super helpful when you need reliable access to the open web. The nodes are run by volunteers and they can keep thousands of users connected simultaneously. Each node is just a VPS running a Docker container, forwarding encrypted packets. Here's how to run one on a ProVM: https://www.doprax.com/docs/run-a-psiphon-conduit-node-on-a-doprax-provm
Doprax pinned a photo
We’ve launched the ProVM Turbo tier! ⚡️ 3Gbps port speed, advanced 2026 CPU and high speed RAM / disk. You can spin up a more powerful ProVM now via your Doprax dashboard: https://www.doprax.com/v/virtual-machines
We’re always working on improving our systems and your experience. The most valuable feedback comes from our users, so we want to know what you think. What’s missing, what would you like to improve? Take a look at our anonymous survey (you can reply in any language): https://docs.google.com/forms/d/e/1FAIpQLScSlPQl7Agr-NsnoUP9UqQefi9IN7jxxl_u1jro3LbVy9guEQ/viewform
Showing the 12 most recent of 20 posts we hold for @dopraxcloud. 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 — 312,889 of 1,624,174entries 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.
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.
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.
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.
@dopraxcloud named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Doprax” (@dopraxcloud), 2,456 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/dopraxcloud.
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.