Working its way up from the back of the class: #13,675 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
40/ 100
F
Slipped a little: down 2,715 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
No daily history yet.
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 63% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
You'll find no region listed by Rust Oxide Dev - Local. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 176.60.35.31:28115.
Is Rust Oxide Dev - Local up, and how steady is its uptime?
You cannot join now: Rust Oxide Dev - Local is offline, last seen 15 days 11 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 13 October 2026.
On what Rust version does Rust Oxide Dev - Local sit?
The server Rust Oxide Dev - Local is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Rust Oxide Dev - Local reset?
There are too few wipes on record for Rust Oxide Dev - Local to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 21 days 17 hours.
Player numbers
What position does Rust Oxide Dev - Local hold in the rankings?
In the top 63% of all ranked servers, Rust Oxide Dev - Local sits at #13,675 for player hours over the last seven days.
Is Rust Oxide Dev - Local a busy server?
It has been 15 days 11 hours since Rust Oxide Dev - Local was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on Rust Oxide Dev - Local?
gmrust (Game mode): Rust survival, played by the standard rules; mp2 (Max players): 2 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Rust Oxide Dev - Local publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Rust Oxide Dev - Local appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Rust Oxide Dev - Local: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does Rust Oxide Dev - Local enforce, and what are its settings?
The name of Rust Oxide Dev - Local gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Rust Oxide Dev - Local uses?
The game generates a procedural map for Rust Oxide Dev - Local.
Getting in
What is the way to join Rust Oxide Dev - Local?
To connect, start Rust, press F1, and type client.connect 176.60.35.31:28115. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp2
Max players2 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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. Even marks across the subjects, from F to F.