Working its way up from the back of the class: #15,980 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
35/ 100
F
Slipped a little: down 4,661 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.
AveragePeak
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 71% 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
Rust Oxide Dev - Local leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 176.60.46.44:28115.
How dependable is Rust Oxide Dev - Local, and is it online at the moment?
At this moment, Rust Oxide Dev - Local is offline; the last time it was seen was 22 days 4 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 5 October 2026.
Which Rust version is Rust Oxide Dev - Local running?
Rust network protocol 2634 and build 166652 on Windows is what Rust Oxide Dev - Local runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does Rust Oxide Dev - Local wipe its map?
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. It has been running its current world for 24 days 19 hours.
Population
Where does Rust Oxide Dev - Local place in the wider field of Rust servers?
Over the last seven days, Rust Oxide Dev - Local has #15,980 for player hours, in the top 71% of all ranked servers.
Is Rust Oxide Dev - Local a busy server?
It has been 22 days 4 hours since Rust Oxide Dev - Local was last seen, and it is offline right now.
Lists and filters
What do Rust Oxide Dev - Local's tags stand for?
The game's browser takes its cue from the tags Rust Oxide Dev - Local has set: gmrust (Game mode): Rust survival, played by the standard rules; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Rust Oxide Dev - Local?
Rust Server Score lists that include Rust Oxide Dev - Local: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is Rust Oxide Dev - Local set up, and what rules does it keep?
The name of Rust Oxide Dev - Local gives no 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. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Rust Oxide Dev - Local uses?
A procedural map, generated by the game, is what Rust Oxide Dev - Local runs.
How to join
How do you get onto Rust Oxide Dev - Local?
Enter client.connect 176.60.46.44:28115 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp2
Max playersThe server holds 2 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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.