Offline 174.91.200.182:28016 checked 15d ago
Contracts Oxide Staging (28016)
Connect
srv = rust.server("174.91.200.182:28117")
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 bestTop 65% 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 05:28 UTC15d ago | 1 | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 174.91.200.182:28016
- region
- –
- max players
- 3
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 05:28 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 | 111/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 172/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 55/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 24/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Contracts Oxide Staging (28016) rank?
Over the last seven days Contracts Oxide Staging (28016) sits at #14,085 on player hours, in the top 65% of ranked servers.
How full does Contracts Oxide Staging (28016) run?
Offline now for Contracts Oxide Staging (28016), with the last sample 15 days 3 hours ago.
Server facts
What Rust version does Contracts Oxide Staging (28016) run?
The build is Rust network protocol 2634 and build 166569 on Windows, run by Contracts Oxide Staging (28016). Steam updates your game for you, but the protocol must match to join.
How reliable is Contracts Oxide Staging (28016), and is it up?
Offline now for Contracts Oxide Staging (28016), last seen 15 days 3 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.
In which location is Contracts Oxide Staging (28016) hosted?
No region is published by Contracts Oxide Staging (28016). Rust Data does not look up where the machine stands; it shows where a server says it is. 174.91.200.182:28016 is its address.
Settings and map
What rules and settings are recorded for Contracts Oxide Staging (28016)?
You will not find a gather rate in the string Contracts Oxide Staging (28016). The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has Contracts Oxide Staging (28016) loaded?
The game generates its map: procedural, on Contracts Oxide Staging (28016).
Wipe schedule
On what schedule does Contracts Oxide Staging (28016) wipe?
The record for Contracts Oxide Staging (28016) holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 15 days 3 hours ago, and that is the one in play.
On Contracts Oxide Staging (28016), what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold Contracts Oxide Staging (28016), and which filters?
On Rust Data, Contracts Oxide Staging (28016) appears in these lists: Modded Rust servers. It appears under these filters 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 Contracts Oxide Staging (28016)?
These tags are published by Contracts Oxide Staging (28016) and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp3 (Max players): 3 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166569 (Build): Recorded game build: 166569; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into Contracts Oxide Staging (28016)?
In Rust, F1 opens the console: type client.connect 174.91.200.182:28016. Launch Rust on this page does the same by opening the game through Steam and connecting.