oxide test server
Offline 197.46.158.203:28015 checked 17d 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 bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 12/ 100
- 114/ 400
- 72/ 225
- 127/ 100
- 116/ 1000
- 6/ 700
Quick answers
Tags and filters
Where does oxide test server appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include oxide test server: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on oxide test server?
oxide test server's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): It holds 1 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs166289 (Build): It's on build 166289; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What location is oxide test server in?
There is no published region for oxide test server. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 197.46.158.203:28015.
How reliable is oxide test server?
Right now oxide test server is offline, having last been seen 17 days 21 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 30 September 2026 is when Rust Going Deep first saw it.
What Rust version is oxide test server on?
Rust network protocol 2634 and build 166289 is what oxide test server runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe info
When does oxide test server wipe?
Too few wipes are on record for oxide test server to show its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 22 days 3 hours is how long ago this world came into being.
Settings and map
What settings and rules have been applied to oxide test server?
No gather rate appears in the name of oxide test server. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. Oxide plugins are running here. VAC is on: Valve's anti-cheat is active.
Player count
Is oxide test server busy?
The last sighting of oxide test server was 17 days 21 hours ago; it is offline right now.
Where does oxide test server sit in the rankings?
Over the last seven days, oxide test server is #16,839 by player hours, among the top 70% of all ranked servers.
How to join
What's the process to join oxide test server?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 197.46.158.203:28015.