Oxide Self-Built Test
Offline 83.228.144.230:28015 checked 43d ago
Vital stats
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
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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.
Quick answers
From the figures on this page.
Lists and tags
Which Rust Pop Watch lists and filters include Oxide Self-Built Test?
You'll find Oxide Self-Built Test on the following Rust Pop Watch lists: Modded Rust servers, live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What do the server tags on Oxide Self-Built Test mean?
The game's server browser picks up these tags from Oxide Self-Built Test: gmrust (Game mode): This one runs standard Rust survival, as it comes; mp2 (Max players): There are 2 slots; ts8 (Group limit): This uses the default limit of 8 players per team; v2633 (Protocol): You need the same game version to get in: protocol 2633; cs163794 (Build): It's on game build 163794; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^o (Oxide): A plugin framework called Oxide (uMod) is running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, queue and world creation time, all shown at the top of this page.
Population
How does Oxide Self-Built Test rank against other Rust servers?
The last seven days of player hours place Oxide Self-Built Test at #15,468, in the top – of all ranked servers.
How many players are on Oxide Self-Built Test right now?
The last sighting of Oxide Self-Built Test was 43 days 14 hours ago, and it is offline now.
About the server
Is Oxide Self-Built Test online, and how reliable is it?
Down at the moment: Oxide Self-Built Test was last seen 43 days 14 hours ago. Out of 168 hours in the last 7 full days, it was online for 0, a 0% uptime. The first time Rust Pop Watch saw it was 16 September 2026.
Where is Oxide Self-Built Test located?
There is no region from Oxide Self-Built Test. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. You'll find it at 83.228.144.230:28015.
Which Rust version is Oxide Self-Built Test on?
On Linux, Oxide Self-Built Test runs Rust network protocol 2633 and build 163794. Joining requires your game to match the protocol, which Steam updates for you.
Wipe days
What is the wipe schedule on Oxide Self-Built Test?
The record of Oxide Self-Built Test's wipes is still too thin to show its rhythm. The monthly force wipe takes every Rust server down for a new world, and the next one lands on Thursday 5 November at 19:00 UTC. Its current world has been live for 43 days 14 hours.
Rules and settings
Which map does Oxide Self-Built Test run?
A procedural map is what Oxide Self-Built Test runs, generated by the game.
What are the rules and settings on Oxide Self-Built Test?
Nothing in the name tells you the gather rate on Oxide Self-Built Test. The group limit is 8 players, the game's default. the usual game of gathering, building and raiding: that is the survival mode. Players can raid and fight one another. Plugins or settings alter the game, and the browser lists it as Modded. Oxide plugins power it. Anti-cheat is on: VAC, Valve's system.
Getting in
How do I join Oxide Self-Built Test?
The console method: start Rust, press F1, and type client.connect 83.228.144.230:28015. Launch Rust on this page is another way, opening Rust via Steam and connecting.