Oxide Debug
168.100.161.67:30004 checked 9m 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, measured since 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 72% 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.
- wipe-day peak
- 2 players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 27 Sep, 21:42 UTC 17d ago | 2 | – | running | 0 |
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
Quick answers
Player Count
Oxide Debug ranking: what position does it hold?
In the top 72% of all ranked servers, Oxide Debug is #15,918 on player hours for the last seven days.
Is Oxide Debug busy?
0 players are on Oxide Debug at the moment. Averaged across the last seven days: 0 players.
Tags & Lists
How should the tags on Oxide Debug be interpreted?
The game's server browser reads these tags from Oxide Debug: gmrust (Game mode): Standard survival gameplay; mp0 (Max players): The server has 0 slots; ts8 (Group limit): Teams are limited to 8, the default; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs165972 (Build): Running build 165972; ptrak (Networking): Network layer: RakNet, the standard; $r? (Region code): Region code missing; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it appears under Modded. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
Oxide Debug in BestRustServers.xyz lists and filters: which ones?
The BestRustServers.xyz lists that include Oxide Debug are: Best modded Rust servers. These filters on the server list display it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server Information
Oxide Debug Rust version: which one?
Rust network protocol 2634 and build 165972 on Linux is what Oxide Debug uses. Joining requires the same protocol; Steam updates your game for you.
Oxide Debug performance: is it smooth?
Its average server fps over the last 48 hours was 239, with a low of 213. It held up to 3,577 entities: everything from buildings to deployables in the world. Memory use peaked at 871 MB. What players experience as lag is low fps combined with a rising entity count.
Oxide Debug uptime and reliability: what are they?
Oxide Debug is currently online. About 17 days 2 hours ago is when it last restarted, based on its uptime. It was up 100% of the time over the last 7 full days, 168 of 168 hours. The first time BestRustServers.xyz saw it was on 27 September 2026.
What is the location of Oxide Debug?
No region is published by Oxide Debug. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. 168.100.161.67:30004 is its address.
Rules & Map
Which map is used on Oxide Debug?
Generated by the game, the map on Oxide Debug is procedural, size 1,000, seed 1337. On RustMaps, from this page, the same size and seed show the same map. Map: Custom Map.
What rules and configuration does Oxide Debug have?
The name Oxide Debug carries no gather multiplier. With no stated limit, groups default to 8 players. It runs survival, gather, build, raid: the standard game. Fighting and raiding between players are allowed. Plugins or settings change the game, so it appears under Modded. Plugins in use: Oxide. VAC protection is on.
Wipe Cycle
Oxide Debug wipe schedule: what does it show?
Oxide Debug's wipe rhythm cannot be told from the wipes on record, which are too few. On Thursday 5 November at 19:00 UTC the next force wipe arrives, when all Rust servers wipe. The world in play was made 17 days 4 hours.
What happens on wipe day on Oxide Debug?
An average peak of 2 players was drawn by its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
Connect
What is the process to join Oxide Debug?
Use the F1 console: client.connect 168.100.161.67:30004. Launch Rust on this page does the same by opening Rust through Steam and connecting. You can find its website at https://oxidemod.com.
Server tags
Published as mp0,ptrak,$r?,v2634,gmrust,cs165972,ts8,^o^z
Game
gmrust- Game mode Standard survival gameplay.
mp0- Max players The server has 0 slots.
ts8- Group limit Teams are limited to 8, the default.
v2634- Protocol Your game must be on protocol 2634 to connect.
cs165972- Build Running build 165972.
ptrak- Networking Network layer: RakNet, the standard.
$r?- Region code Region code missing.
Mods and access
^o- Oxide Oxide (uMod) provides the plugin framework here.
^z- Modded Plugins or settings alter the game, so it appears under Modded.
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.