Oxide Self-Built Test
Key statistics
the figures behind the quote- Players now
- 0/ 2 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,468 no region published
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 28d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 16 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestWipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 126 on average | 195/300 | ▲+1+0.7% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 106 on average | 188/225 | ▼−18−8.7% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 91/100 | ▲+1+0.6% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 87 on average | 47/1000 | ▼−67−58.9% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 10/1000 | ▼−25−71.2% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 72/700 | ▼−55−43.3% |
Quick answers
from the figures on this pageMap and Rules
What settings and rules are in place on Oxide Self-Built Test?
No gather rate appears in the name of Oxide Self-Built Test. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. Modded is its category in the server browser; plugins or settings modify the game. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on Oxide Self-Built Test?
A procedural map runs on Oxide Self-Built Test, created by the game.
Activity
Where does Oxide Self-Built Test sit in the rankings?
In the top – of all ranked servers, Oxide Self-Built Test is #15,468 on player hours over the last seven days.
What is the population on Oxide Self-Built Test?
Right now, Oxide Self-Built Test is offline; the last sighting was 28 days 11 hours ago.
Wipe Frequency
On what cycle does Oxide Self-Built Test wipe?
No rhythm can be told for Oxide Self-Built Test yet: too few of its wipes are on record. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. 28 days 11 hours ago the current world was created.
Server Overview
Where can Oxide Self-Built Test be found?
There is no region published for Oxide Self-Built Test. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 83.228.144.230:28015.
What Rust version is Oxide Self-Built Test running?
Rust network protocol 2633 and build 163794 on Linux is what Oxide Self-Built Test runs. Joining requires the same protocol on your game, which Steam updates.
What is the uptime and reliability of Oxide Self-Built Test?
Offline at this moment: Oxide Self-Built Test. Last seen 28 days 11 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. The earliest Rust Analytics saw it was 16 September 2026.
Server Tags
What is the meaning of the tags on Oxide Self-Built Test?
The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp2 (Max players): Capacity: 2 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2633 (Protocol): Protocol 2633: matching game versions are required to join; cs163794 (Build): Build 163794; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which Oxide Self-Built Test publishes. The top of this page and the tags both show its players now, its queue and when its world was made.
Where does Oxide Self-Built Test show up in Rust Analytics lists and filters?
These Rust Analytics lists include Oxide Self-Built Test: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connection
What is the process to join Oxide Self-Built Test?
Type client.connect 83.228.144.230:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp2,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z
Game
gmrust
mp2
ts8
v2633
cs163794
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.