oxide-observation
Offline 34.32.217.132:28015 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe 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- 179/500
- 121/100
- 86/700
- 22/200
- 26/1000
- 268/700
Quick answers
from the figures on this pageReset cycle
What wipe timing does oxide-observation follow?
To tell the rhythm of oxide-observation, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 43 days 9 hours ago the current world was made.
Tags
How should you read the tags on oxide-observation?
These are the tags oxide-observation publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): The server runs game build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show oxide-observation?
Rust Metrics lists featuring oxide-observation: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does oxide-observation sit in the rankings?
Player hours over seven days put oxide-observation at #15,470, in the top – of all ranked servers.
What is the population on oxide-observation?
Reading for oxide-observation: offline at this moment; last seen 43 days 9 hours ago.
Server
Which location does oxide-observation run from?
No region comes from oxide-observation. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 34.32.217.132:28015.
What Rust version is oxide-observation on?
Rust network protocol 2633 and build 163794 on Linux is the build oxide-observation runs. To get in, your game needs the same protocol; Steam applies the update.
How reliable is oxide-observation, and is it online now?
Check: connection. oxide-observation is offline at this moment. Last contact was 43 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 16 September 2026, recorded by Rust Metrics.
Settings and map
What rules does oxide-observation enforce, and what are its settings?
Reading the name gives no gather rate for oxide-observation. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
What map is oxide-observation on?
Check: map. Procedural, generated by the game, on oxide-observation.
How to join
What do you do to join oxide-observation?
Press F1 in Rust and enter client.connect 34.32.217.132:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.