Offline 168.100.161.67:30004 checked 9d ago
Oxide Debug
Connect
srv = rust.server("168.100.161.67:30005")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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 · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 27 Sep, 21:42 UTC31d ago | 2 | NaN | 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.
display(srv.map, srv.info())Map
1000 · seed 1337
- map
- Custom Map
- size
- 1000
- seed
- 1337
Server
srv.info()- address
- 168.100.161.67:30004
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Sep 2026, 21:42 UTC
- hostname
- –
- first seen
- 27 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 157/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 66/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 11/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 21/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Oxide Debug rank?
Over the last seven days Oxide Debug sits at #15,308 on player hours, in the top 70% of ranked servers.
What population does Oxide Debug carry?
The current row shows Oxide Debug offline; the last response was 9 days 21 hours ago.
About the server
What is the Rust version on Oxide Debug?
Rust network protocol 2634 and build 165972 on Linux is what Oxide Debug runs. Joining needs the same protocol on your game; Steam handles the update.
Is Oxide Debug up, and what does its uptime show?
The latest sample has Oxide Debug offline, with a last sighting 9 days 21 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 27 September 2026.
Which location does Oxide Debug run from?
For Oxide Debug, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 168.100.161.67:30004.
Rules, settings, map
Which settings and rules does Oxide Debug run?
The name Oxide Debug carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Oxide Debug selected?
Oxide Debug runs a procedural map of size 1,000 with seed 1337, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.
Wipe schedule
When does Oxide Debug wipe, and how often?
Too few wipes are on record for Oxide Debug to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 31 days 13 hours ago.
What is wipe day on Oxide Debug like?
Across recent wipes the busiest point averaged 2 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold Oxide Debug, and which filters?
On Rust Data, Oxide Debug appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Oxide Debug?
Read by the game's server browser, the tags Oxide Debug publishes are: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): 0 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs165972 (Build): Recorded game build: 165972; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join Oxide Debug?
The manual route: launch Rust, F1, then client.connect 168.100.161.67:30004. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://oxidemod.com is the website recorded for it.