Working its way up from the back of the class: #15,962 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 3,157 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); standing 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.
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.
Average fpsLowest fpsWipe
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.
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 17 Sep. 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
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 peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 13:46 UTC25d ago
1
–
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 Dev 3 leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 57.129.153.14:28023 is the address to use.
How reliable is Oxide Dev 3, and is it up?
You cannot join now: Oxide Dev 3 is offline, last seen 24 days 17 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 16 September 2026.
On what Rust version does Oxide Dev 3 sit?
Rust network protocol 2634 and build 166652 on Linux is what Oxide Dev 3 runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does Oxide Dev 3 wipe, and how often?
The record holds too few of Oxide Dev 3's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 25 days have passed since this world was made.
What should you expect from wipe day on Oxide Dev 3?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does Oxide Dev 3 sit among Rust servers?
Over the last seven days, Oxide Dev 3 has #15,962 for player hours, in the top 71% of all ranked servers.
How many players does Oxide Dev 3 usually have?
Oxide Dev 3 is offline at the moment; the last time it was seen was 24 days 17 hours ago.
Tags
How should you read the tags on Oxide Dev 3?
You'll see Oxide Dev 3 tagged with gmvanilla (Game mode): You play vanilla survival here; mp0 (Max players): 0 slots are available; ts32 (Group limit): A team can hold 32 players at most; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; rustmaps (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Oxide Dev 3?
These Rust Server Score lists count Oxide Dev 3 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is Oxide Dev 3 set up, and what rules does it keep?
The name of Oxide Dev 3 gives no gather rate. The limit for a group is 32 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on Oxide Dev 3?
Download the published file for the custom 3,000 map on Oxide Dev 3 from this page.
How to join
How do you get onto Oxide Dev 3?
Enter client.connect 57.129.153.14:28023 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 asmp0,ptrak,$r?,v2634,gmvanilla,cs166652,ts32,^o^z,rustmaps
Game
gmvanilla
Game modeYou play vanilla survival here.
mp0
Max players0 slots are available.
ts32
Group limitA team can hold 32 players at most.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
rustmaps
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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 (F); standing is the one to work on (F).