Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h4 48 h

Station XX-15308 · no signal

Oxide Debug

Offline 168.100.161.67:30004 checked 9d ago

moddedoxide
Connect
Players now
0/ ?
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,308
top 70%
Last wipe
30d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15308 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of ? slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k27 Sep3 Oct9 Oct14 Oct20 Oct26 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
2players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 27 Sep, 21:42 UTC30d ago M0.3rising 2 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 157 on average
205/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 127 on average
121/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 115 on average
183/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 90 on average
126/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
19/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
50/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Oxide Debug?

The procedural map on Oxide Debug is size 1,000 with seed 1337, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. You will find the map named Custom Map.

Which settings and rules apply on Oxide Debug?

The name of Oxide Debug gives no gather rate. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on Oxide Debug?

Oxide Debug is not responding at this moment and is offline, last seen 9 days 5 hours ago.

How does Oxide Debug rank against other Rust servers?

Over the last seven days, Oxide Debug recorded enough player hours to reach #15,308 worldwide, placing it in the top 70% of all ranked servers.

Server details

How reliably does Oxide Debug stay online?

No contact with Oxide Debug right now, and the last recorded contact was 9 days 5 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 27 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does Oxide Debug run from?

No region is published by Oxide Debug. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 168.100.161.67:30004 is the address it uses.

What build of Rust does Oxide Debug use?

Oxide Debug is running Rust network protocol 2634 and build 165972 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on Oxide Debug?

On average, the busiest point of its recent wipes drew 2 players. The peak on the most recent wipe came 0 hours after the wipe.

How often does Oxide Debug wipe, and on which days?

On record so far are too few of Oxide Debug's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 30 days 22 hours.

Tags

What do the server tags on Oxide Debug mean?

Tags published by Oxide Debug and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp0 (Max players): The server has 0 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs165972 (Build): It runs game build 165972; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Oxide Debug appear?

The Rust Server Trends lists that take in Oxide Debug are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

What steps get you onto Oxide Debug?

To join, enter client.connect 168.100.161.67:30004 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. For the website, go to https://oxidemod.com.

Instrument codes

Server tags

what each one means

Published as mp0,ptrak,$r?,v2634,gmrust,cs165972,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp0
Max players The server has 0 slots.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs165972
Build It runs game build 165972.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.