Offline 154.176.223.251:28015 checked 33d ago
oxide test server
Connect
srv = rust.server("154.176.223.251:28016")
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 61% 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 | Sat 26 Sep, 02:46 UTC33d ago | 1 | NaN | running | 1 |
# 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 154.176.223.251:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 02:46 UTC
- hostname
- –
- first seen
- 26 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 | 21/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 44/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 182/215 |
Quick answers
From the figures on this page.
Population
How does oxide test server compare in the rankings?
Over the last seven days oxide test server sits at #14,157 on player hours, in the top 61% of ranked servers.
How many players does oxide test server hold at once?
oxide test server returns no live count at this refresh, having last been seen 33 days 22 hours ago.
Server facts
What Rust version does oxide test server run?
Rust network protocol 2634 and build 165937 on Windows is what oxide test server runs. Steam updates your game for you, but the protocol must match to join.
Is oxide test server up, and what does its uptime show?
Offline now for oxide test server, last seen 33 days 22 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 26 September 2026.
Which location does oxide test server run from?
There is no region published for oxide test server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 154.176.223.251:28015 is its address.
Map and rules
Which rules apply on oxide test server, and what settings?
No gather rate appears in the name: oxide test server. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Wipes and dates
When does oxide test server wipe, and on what schedule?
The record for oxide test server 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 33 days 22 hours ago.
What is wipe day on oxide test server like?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain oxide test server?
The Rust Data lists that oxide test server fits are: 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 oxide test server?
These tags are published by oxide test server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs165937 (Build): The server runs build 165937; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to oxide test server?
Enter client.connect 154.176.223.251:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.