On the class lists: F (37), with population over 48 hours and no performance mark.
Players now1/ 1010% full
7-day average0peak 1
Rank#8,486top 38%
Last wipe2d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
62/ 100
C
Working its way up from the back of the class: #8,486 on player hours.
Uptimehours on the list, last 48
50/ 100
D
Attendance needs work: on the list only 24 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 84 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in performance (A+); 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 25 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 38% 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 25 Oct, 19:06 UTC3d 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
You'll find no region listed by RUREADY. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 129.232.154.35:28065.
How dependable is RUREADY, and is it online at the moment?
The server is down: RUREADY is offline now, with the last sighting 23 hours ago. About 25 hours ago, it restarted, based on the uptime it reports. It was up 29 of 48 hours over the last 2 full days, which is 60% of the time. It was first seen by Rust Server Score on 25 October 2026.
Is RUREADY smooth to play on?
It never fell below 61 server fps in the last 48 hours, averaging 84. Up to 50,068 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 2,121 MB. When fps is low and entities climb, that is lag to players.
What Rust version is RUREADY on?
Rust network protocol 2635 and build 168909 on Windows is what RUREADY runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does RUREADY reset?
RUREADY 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 2 days 23 hours.
What happens on RUREADY when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player count
What position does RUREADY hold in the rankings?
Over the last seven days, RUREADY has #8,486 for player hours, in the top 38% of all ranked servers.
What does the population on RUREADY look like?
RUREADY is offline at the moment; the last time it was seen was 23 hours ago. The seven-day average is 0 players, with a peak of 1. The busiest time in the last 48 hours was 20:00 UTC, with an average of 0 players.
Tags
What is meant by the tags on RUREADY?
The game's browser takes its cue from the tags RUREADY has set: gmvanilla (Game mode): Survival, vanilla style; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it 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 RUREADY?
These Rust Server Score lists count RUREADY among them: 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; Last wipe: In the last 3 days.
Server rules
Which rules does RUREADY enforce, and what are its settings?
The name of RUREADY gives no gather rate. The group limit stays at the game's default of 8 players. You get survival 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. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map RUREADY uses?
RUREADY runs a game-generated procedural map at size 3,000, seed 6738. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to RUREADY?
To connect, start Rust, press F1, and type client.connect 129.232.154.35:28065. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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. Strongest in performance (A+); population is the one to work on (F).