oxide-observation
Offline 34.91.74.176:28015 checked 32d 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 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
- 17/ 100
- 234/ 400
- 178/ 225
- 134/ 100
- 278/ 1000
- 22/ 700
Quick answers
Tags and listings
Where does oxide-observation appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry oxide-observation are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on oxide-observation?
gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): It holds 10 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163794 (Build): It's on build 163794; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The Modded category fits: plugins or settings are in play — that is the tag list oxide-observation puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What location is oxide-observation in?
No region comes from oxide-observation. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. To connect, use 34.91.74.176:28015.
How reliable is oxide-observation?
Right now oxide-observation is offline, having last been seen 32 days 4 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. Rust Going Deep has had it on record since 16 September 2026.
What Rust version is oxide-observation on?
Rust network protocol 2633 and build 163794 is what oxide-observation runs, on Linux. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
What schedule does oxide-observation follow for wipes?
Too few wipes are on record for oxide-observation 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. 32 days 5 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is oxide-observation running?
Its name does not state a gather rate for oxide-observation. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. 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.
Which map is active on oxide-observation?
The map on oxide-observation is procedural, made by the game.
Player stats
Is oxide-observation busy?
Right now oxide-observation is offline, with its last appearance 32 days 4 hours ago.
Where does oxide-observation sit in the rankings?
For player hours in the last seven days, oxide-observation ranks #15,468, within the top – of ranked servers.
How to join
What's the way to join oxide-observation?
Open Rust and press F1, then type client.connect 34.91.74.176:28015. Alternatively, click Launch Rust on this page to join via Steam.