Working its way up from the back of the class: #15,506 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
7/ 100
F
Lost ground: down 13,485 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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.
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 67% 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
No region is published for R4R Oxide Dev 2. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 57.129.153.14:28019.
How reliable is R4R Oxide Dev 2, and is it up?
At this moment, R4R Oxide Dev 2 is offline; the last time it was seen was 40 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 16 September 2026.
Which Rust version is R4R Oxide Dev 2 running?
The server R4R Oxide Dev 2 is on Rust network protocol 2633 and build 163794 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does R4R Oxide Dev 2 reset?
The record holds too few of R4R Oxide Dev 2'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. The world it runs now was created 41 days 9 hours.
Player numbers
Where does R4R Oxide Dev 2 place in the wider field of Rust servers?
In the top 67% of all ranked servers, R4R Oxide Dev 2 sits at #15,506 for player hours over the last seven days.
What does the population on R4R Oxide Dev 2 look like?
R4R Oxide Dev 2 is offline at the moment; the last time it was seen was 40 days 12 hours ago.
Tags
How should you read the tags on R4R Oxide Dev 2?
The game's browser takes its cue from the tags R4R Oxide Dev 2 has set: gmvanilla (Game mode): You play vanilla survival here; mp0 (Max players): Its slot count is 0; ts32 (Group limit): Teams cap out at 32; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): This runs on build 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; rustmaps (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner. 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 lists and filters on Rust Server Score show R4R Oxide Dev 2?
Rust Server Score lists that include R4R Oxide Dev 2: 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; Players now: At least 50.
Rules and settings
What settings and rules apply on R4R Oxide Dev 2?
You will find no gather rate in the name of R4R Oxide Dev 2. A group here can reach 32 players. You get survival here, gather and build and raid: 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map R4R Oxide Dev 2 uses?
A procedural map, generated by the game, is what R4R Oxide Dev 2 runs.
How to join
How should you connect to R4R Oxide Dev 2?
Enter client.connect 57.129.153.14:28019 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?,v2633,gmvanilla,cs163794,ts32,^o^z,rustmaps
Game
gmvanilla
Game modeYou play vanilla survival here.
mp0
Max playersIts slot count is 0.
ts32
Group limitTeams cap out at 32.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Other
rustmaps
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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 standing (F); momentum is the one to work on (F).