oxide-observation
Key statistics
the figures behind the quote- Players now
- 0/ 10 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,470 no region published
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 28d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 16 Sep 2026 no hostname published
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
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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 127 on average | 159/300 | ▲+4+2.3% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average | 187/225 | ▼−15−7.5% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 88/100 | ▼−3−3.1% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 87 on average | 41/1000 | ▼−65−61.4% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 12/1000 | ▼−28−69.8% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 66/700 | ▼−30−31.2% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on oxide-observation?
No gather rate is given in the name of oxide-observation. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. In the server browser it appears under Modded, with plugins or settings that change the game. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, switched on.
Which map is played on oxide-observation?
oxide-observation uses a procedural map, which the game generates.
Population
Where does oxide-observation sit in the rankings?
For the last seven days, oxide-observation holds rank #15,470 on player hours, in the top – of all ranked servers.
How many players does oxide-observation have?
At present, oxide-observation is offline; the last sighting was 28 days 13 hours ago.
Wipe Cycle
When does oxide-observation schedule its wipes?
No rhythm can be told for oxide-observation yet: too few of its wipes are on record. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. Its world now is 28 days 14 hours old.
Server Details
What is the location of oxide-observation?
There is no region published for oxide-observation. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 34.32.217.132:28015.
What Rust version is oxide-observation running?
Rust network protocol 2633 and build 163794 on Linux is what oxide-observation runs. Your game needs the same protocol to get in; Steam takes care of the update.
What is the uptime and reliability of oxide-observation?
No response from oxide-observation. It was last seen 28 days 13 hours ago. The last 7 full days give 0% uptime, 0 hours on out of 168. First sighting by Rust Analytics: 16 September 2026.
Tags & Filters
What is the meaning of the tags on oxide-observation?
These tags are published by oxide-observation and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2633 (Protocol): Protocol 2633: matching game versions are required to join; cs163794 (Build): Game build: 163794; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The Modded listing applies: plugins or settings change play. The top of this page and the tags both show its players now, its queue and when its world was made.
Where does oxide-observation show up in Rust Analytics lists and filters?
These Rust Analytics lists include oxide-observation: 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.
Connection
What steps do I take to join oxide-observation?
Type client.connect 34.32.217.132:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z
Game
gmrust
mp10
ts8
v2633
cs163794
ptrak
$r?
Mods and access
^o
^z
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.