Oxide Self-Built Test
Offline 83.228.144.230:28015 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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- 186/500
- 134/100
- 179/225
- 91/700
- 284/200
- 236/700
Quick answers
from the figures on this pageReset cycle
What wipe timing does Oxide Self-Built Test follow?
To tell the rhythm of Oxide Self-Built Test, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 43 days 11 hours ago.
Tag meanings
Which tags does Oxide Self-Built Test carry, and what do they mean?
These are the tags Oxide Self-Built Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Oxide Self-Built Test appear in Rust Metrics lists and filters?
On Rust Metrics, Oxide Self-Built Test sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does Oxide Self-Built Test sit in the rankings?
Ranking for Oxide Self-Built Test: #15,468 on seven-day player hours, top – of all ranked servers.
How full does Oxide Self-Built Test get?
Oxide Self-Built Test is not responding; status offline, last seen 43 days 11 hours ago.
Server
Which location does Oxide Self-Built Test run from?
No region tag on Oxide Self-Built Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 83.228.144.230:28015.
What Rust version is Oxide Self-Built Test on?
Reading: Oxide Self-Built Test, Rust network protocol 2633 and build 163794, Linux. Matching protocol is required to join. Let Steam update your game.
Is Oxide Self-Built Test up, and how often does it stay up?
Check: connection. Oxide Self-Built Test is offline at this moment. Last contact was 43 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 16 September 2026, recorded by Rust Metrics.
Settings and map
How is Oxide Self-Built Test configured, and what rules are in force?
Reading the name gives no gather rate for Oxide Self-Built Test. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.
What map is Oxide Self-Built Test on?
Check: map. Procedural, generated by the game, on Oxide Self-Built Test.
Connection
What do you do to join Oxide Self-Built Test?
Press F1 in Rust and enter client.connect 83.228.144.230:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.