Oxide Self-Built Test
Offline 83.228.144.230:28015 checked 32d ago
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
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
- 17/ 100
- 300/ 400
- 173/ 225
- 122/ 100
- 338/ 1000
- 26/ 700
Quick answers
Tags and listings
Where does Oxide Self-Built Test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Oxide Self-Built Test: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on Oxide Self-Built Test?
The server browser shows these tags for Oxide Self-Built Test: gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): It holds 2 players; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163794 (Build): The build number is 163794; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What location is Oxide Self-Built Test in?
There is no published region for Oxide Self-Built Test. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 83.228.144.230:28015.
What's the uptime like for Oxide Self-Built Test?
Right now Oxide Self-Built Test is offline, having last been seen 32 days 6 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 16 September 2026.
What is the Rust version for Oxide Self-Built Test?
On Linux, Oxide Self-Built Test runs Rust network protocol 2633 and build 163794. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
How often does Oxide Self-Built Test wipe?
Oxide Self-Built Test's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 32 days 6 hours ago.
Settings and map
What settings are in place on Oxide Self-Built Test?
No gather rate appears in the name of Oxide Self-Built Test. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser puts it under Modded, as plugins or settings alter the game. You will find Oxide plugins installed. VAC, Valve's anti-cheat, is enabled.
What's the map on Oxide Self-Built Test?
A procedural map, generated by the game, is in play on Oxide Self-Built Test.
Player count
Is Oxide Self-Built Test busy?
Oxide Self-Built Test was last seen 32 days 6 hours ago and is offline as you read this.
What position does Oxide Self-Built Test hold in the server rankings?
For player hours in the last seven days, Oxide Self-Built Test ranks #15,468, within the top – of ranked servers.
How to join
What's the way to join Oxide Self-Built Test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 83.228.144.230:28015.