On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 3000% full
7-day average0peak –
Rank#15,326top 69%
Last wipe28d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 300 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,326 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 201 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
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
Players each hour, from the hour of the wipe. The latest peaked at 2, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 03:28 UTC28d ago
2
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Oxide Council Staging leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 159.112.73.50:28015 is the address to use.
Is Oxide Council Staging up, and how steady is its uptime?
The server is down: Oxide Council Staging is offline now, with the last sighting 5 days 9 hours ago. It was up 52 of 168 hours over the last 7 full days, which is 31% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is Oxide Council Staging on?
The server Oxide Council Staging is on Rust network protocol 2634 and build 166448 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does Oxide Council Staging reset?
Oxide Council Staging has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 28 days 10 hours.
What happens on Oxide Council Staging when wipe day arrives?
Recent wipes have peaked at 2 players on average. 5 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does Oxide Council Staging place in the wider field of Rust servers?
In the top 69% of all ranked servers, Oxide Council Staging sits at #15,326 for player hours over the last seven days.
What does the population on Oxide Council Staging look like?
The last sighting of Oxide Council Staging was 5 days 9 hours ago, and it is offline right now. For the last seven days, the average number of players was 0.
Lists and filters
What do Oxide Council Staging's tags stand for?
You'll see Oxide Council Staging tagged with gmrust (Game mode): Survival in the standard Rust style; mp300 (Max players): 300 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166448 (Build): Build number: 166448; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature Oxide Council Staging?
These Rust Server Score lists count Oxide Council Staging among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
What settings and rules apply on Oxide Council Staging?
Nothing in the name of Oxide Council Staging states a gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Oxide Council Staging uses?
The game generates the procedural map on Oxide Council Staging at size 4,500 with seed 4000. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto Oxide Council Staging?
To connect, start Rust, press F1, and type client.connect 159.112.73.50:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp300,ptrak,$r?,v2634,gmrust,cs166448,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp300
Max players300 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166448
BuildBuild number: 166448.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been 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.
A term to build on. Strongest in momentum (D); population is the one to work on (F).