Offline 86.30.113.113:28025 checked 18d ago
Brian's Rusty Box - OXIDE TEST
Connect
srv = rust.server("86.30.113.113:28027")
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 best
Top 72% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 12:29 UTC26d ago | 0 | 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
- 86.30.113.113:28025
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 12:29 UTC
- hostname
- –
- first seen
- 15 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 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 251 on average | 230/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 241 on average | 92/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 105 on average | 123/200 |
| 3 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 60 on average | 39/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 40/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 51 on average | 9/100 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Brian's Rusty Box - OXIDE TEST rank?
Rank #15,846 on seven-day player hours for Brian's Rusty Box - OXIDE TEST, within the top 72% of all ranked servers.
How many players does Brian's Rusty Box - OXIDE TEST hold at once?
Offline now for Brian's Rusty Box - OXIDE TEST, with the last sample 18 days 14 hours ago.
About the server
Which Rust version is Brian's Rusty Box - OXIDE TEST on?
Version Rust network protocol 2634 and build 167398 on Windows is reported by Brian's Rusty Box - OXIDE TEST. Steam updates your game for you, but the protocol must match to join.
How reliable is Brian's Rusty Box - OXIDE TEST, and is it online now?
The latest sample has Brian's Rusty Box - OXIDE TEST offline, with a last sighting 18 days 14 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 15 September 2026.
Which location does Brian's Rusty Box - OXIDE TEST run from?
For Brian's Rusty Box - OXIDE TEST, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 86.30.113.113:28025 is its address.
Rules, settings, map
What rules and settings are recorded for Brian's Rusty Box - OXIDE TEST?
You will not find a gather rate in the string Brian's Rusty Box - OXIDE TEST. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Brian's Rusty Box - OXIDE TEST loaded?
Brian's Rusty Box - OXIDE TEST runs a procedural map, which the game generates.
Wipes and dates
When does Brian's Rusty Box - OXIDE TEST wipe, and how often?
A rhythm cannot be read from the wipes of Brian's Rusty Box - OXIDE TEST on record, which are too few. 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 26 days 15 hours ago.
On Brian's Rusty Box - OXIDE TEST, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Where does Brian's Rusty Box - OXIDE TEST appear among Rust Data lists and filters?
On Rust Data, Brian's Rusty Box - OXIDE TEST appears in these lists: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Brian's Rusty Box - OXIDE TEST hold?
Read by the game's server browser, the tags Brian's Rusty Box - OXIDE TEST publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): The server runs build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to Brian's Rusty Box - OXIDE TEST?
The manual route: launch Rust, F1, then client.connect 86.30.113.113:28025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.