Rust Data

rustdata.spaceservers159.112.73.50:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 159.112.73.50:28015 checked 5d ago

Oxide Council Staging

Connect

srv = rust.server("159.112.73.50:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/300 # 0% full
7-day average 0 # peak –
rank #15,338 # top 69%
last wipe 28d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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, measured since 1 Oct. 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
RankRank in region
15k10k15k20k20 Sep3 Oct9 Oct16 Oct22 Oct29 Oct

Top 69% 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.

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 5 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 03:28 UTC28d ago 2 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

4500 · seed 4000
Map of Oxide Council Staging
map
Procedural Map
size
4500
seed
4000
Open on RustMaps

Server

srv.info()
address
159.112.73.50:28015
region
–
max players
300
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 03:28 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 519 on average401/400
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average338/350
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average36/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average35/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average46/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 244 on average150/200

Quick answers

From the figures on this page.

Population

What position does Oxide Council Staging take in the server rankings?

Over the last seven days Oxide Council Staging sits at #15,338 on player hours, in the top 69% of ranked servers.

What population does Oxide Council Staging carry?

Oxide Council Staging returns no live count at this refresh, having last been seen 5 days 6 hours ago. Over the last seven days it averaged 0 players.

About the server

What Rust version does Oxide Council Staging run?

Rust network protocol 2634 and build 166448 on Linux is what Oxide Council Staging runs. Steam updates your game for you, but the protocol must match to join.

How reliable is Oxide Council Staging, and is it up?

Offline now for Oxide Council Staging, last seen 5 days 6 hours ago. Uptime of 31% across the last 7 full days: 52 hours of 168. Rust Data logged it first on 13 September 2026.

Where does Oxide Council Staging sit?

For Oxide Council Staging, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 159.112.73.50:28015.

Rules, settings, map

Which rules apply on Oxide Council Staging, and what settings?

You will not find a gather rate in the string Oxide Council Staging. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Community is its browser category. Anti-cheat status: VAC on.

Which map has Oxide Council Staging selected?

Size 4,500, seed 4000: the procedural map on Oxide Council Staging, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

When does Oxide Council Staging wipe, and how often?

Too few wipes are on record for Oxide Council Staging to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 28 days 6 hours ago.

On Oxide Council Staging, what happens on wipe day?

The average peak over recent wipes is 2 players. 5 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Which Rust Data filters and lists contain Oxide Council Staging?

These Rust Data lists include Oxide Council Staging: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on Oxide Council Staging hold?

The game's server browser reads these tags from Oxide Council Staging: gmrust (Game mode): Survival play, standard Rust; mp300 (Max players): The server lists 300 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166448 (Build): The server runs build 166448; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. 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

What is the way into Oxide Council Staging?

In Rust, F1 opens the console: type client.connect 159.112.73.50:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp300,ptrak,$r?,v2634,gmrust,cs166448,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp300
Max players The server lists 300 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs166448
Build The server runs build 166448.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

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.

Rust Data 55,754 players 11,716 servers online