Offline 34.91.74.176:28015 checked 44d ago
oxide-observation
Connect
srv = rust.server("34.91.74.176:28017")
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. 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 bestWipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 34.91.74.176:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Sep 2026, 03:48 UTC
- hostname
- –
- first seen
- 16 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 · 151 on average | 23/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 48/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 29/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 49/200 |
Quick answers
From the figures on this page.
Population data
What position does oxide-observation take in the server rankings?
Over the last seven days oxide-observation sits at #15,468 on player hours, in the top – of ranked servers.
How full does oxide-observation run?
The current row shows oxide-observation offline; the last response was 44 days ago.
Server data
What Rust version does oxide-observation run?
Version Rust network protocol 2633 and build 163794 on Linux is reported by oxide-observation. Joining needs the same protocol on your game; Steam handles the update.
How reliable is oxide-observation, and is it up?
Offline now for oxide-observation, last seen 44 days ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 16 September 2026.
Which location does oxide-observation run from?
No region is published by oxide-observation. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 34.91.74.176:28015.
Rules, settings, map
Which rules apply on oxide-observation, and what settings?
No gather rate appears in the name: oxide-observation. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has oxide-observation loaded?
A procedural map runs on oxide-observation, generated by the game.
Wipe data
When does oxide-observation wipe, and on what schedule?
The record for oxide-observation holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 44 days ago.
Lists and tags
Which lists on Rust Data hold oxide-observation, and which filters?
These Rust Data lists include oxide-observation: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on oxide-observation hold?
These tags are published by oxide-observation and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to oxide-observation?
In Rust, F1 opens the console: type client.connect 34.91.74.176:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.