Channel
@oxustech
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,227subscribers
-82 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003762466201 |
|---|---|
| Type | Channel |
| Username | @oxustech |
| Created | 20 May 2026 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/oxustech |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 11:23 | 1,227 | -77 |
| 10 Aug 2026, 00:41 | 1,304 | -5 |
| 7 Aug 2026, 07:57 | 1,309 | no change |
| 6 Aug 2026, 14:32 | 1,309 | first reading |
11 posts held, back to 20 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 23 July 2026 |
|---|---|
| Posts held | 11 (20 May 2026 – 23 July 2026) |
| Views total | 1,537 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 14:32 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.
How to start Getting connected takes a few minutes and requires no trading skills. The platform handles the entire technical side — from executing trades to tracking rewards. Four steps: — sign up: email and password, access to every feature — deposit: from 50 USDT, balance credited within a minute — connect: funds are routed into the trading pool and start working in arbitrage strategies right away — track: real-t…
The partner program Alongside deposit rewards, the platform offers payouts for developing a partner structure. This is a voluntary layer: it expands your rewards but is not a condition of participation. How it works: Firstline — on the volume of first-line partners, up to 0.20% per day Downline — on team volume across the full depth, up to 0.04% per day Poolshare — shares of the total volume based on the level reac…
Deposit rewards The main stream works autonomously: arbitrage agents accrue daily rewards on your contract volume, regardless of the partner program. The rate depends on the contract volume and grows with it: from 50 USDT — up to 0.6% per day from 3,000 USDT — up to 0.8% per day from 15,000 USDT — up to 0.9% per day from 50,000 USDT — up to 1.1% per day Rewards land on your bonus balance every day. The entry thres…
Five reward streams Rewards at OxusTech come from several streams. The main one is arbitrage on your own deposit: it is available immediately after a top-up and works without invited partners. The remaining streams belong to the partner program and are optional: Firstline — on the volume of first-line partners Downline — on team volume across the depth of the structure Poolshare — shares in pools based on volume Ran…
Why now The prediction market is going through a phase of rapid growth: trading volumes are breaking records, and institutional capital has already entered the platform. In markets like these, early participants gain an advantage in timing. What this gives you at the start: — your capital connects to the arbitrage strategies right away — your partner structure forms before the main influx — rewards arrive from the f…
The OxusTech pre-launch is open The project is entering its pre-launch phase — early access ahead of the public launch. The platform is already running, and you can join among the first. Entering early offers an advantage in timing: your capital starts taking part in the arbitrage strategies right away, and your partner structure forms before the main influx of participants. Available right now: — registration on t…
Why speed decides everything Price discrepancies are short-lived — between 10 and 50 milliseconds. In manual trading, that window closes before a participant can place the trade. The outcome is determined by infrastructure. OxusTech's algorithmic agents execute a trade in 2–5 ms on dedicated servers and monitor thousands of markets simultaneously, around the clock. To get started, you need to: — register on the pla…
Where the income comes from Every event on the platform has two opposing sides. Each is a separate contract that settles at exactly one dollar once the event closes: the winning side is worth a dollar, the losing side goes to zero. Under normal conditions, the prices of the two sides add up to a dollar. But with a large number of participants and varying reaction speeds, the sum periodically drops below a dollar. At…
What Polymarket is? Polymarket is the world's largest prediction exchange. What trades here are the outcomes of real-world events — in politics, the economy, sports, and cryptocurrencies. The platform runs on exchange principles: prices are set by supply and demand and change every second, like any traded asset. A position can be opened and closed at any time. A few figures: — $10.5 billion trading volume in March …
OxusTech — Technology works for you Welcome. This is where we explain how technology earns on one of the fastest-growing markets in the world — Polymarket. OxusTech is a set of autonomous algorithmic agents that generate income through arbitrage on the price spread. The profit is built on the price structure itself and does not depend on event outcomes. The key edge is execution speed of 2–5 ms — impossible to mat…
Channel created
Showing the 11 most recent of 11 posts we hold for @oxustech. 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 — 525,391 of 1,345,403entries 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.
Named by 6 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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“OxusTech Notifications” (@oxustech), 1,227 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/oxustech.
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.