Working its way up from the back of the class: #15,895 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
52/ 100
D
Moving up: up 644 places this week.
A term to build on.
Strongest in momentum (D); 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.
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.
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
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.
Average fpsLowest fpsWipe
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, measured since 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% 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_SERVER_NAME==. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 133.88.121.224:28015 is the address to use.
How dependable is ==RUST_SERVER_NAME==, and is it online at the moment?
The server is down: ==RUST_SERVER_NAME== is offline now, with the last sighting 27 days 2 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 2 October 2026, Rust Server Score saw it for the first time.
What Rust version is ==RUST_SERVER_NAME== on?
The server ==RUST_SERVER_NAME== is on Rust network protocol 2634 and build 166586 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does ==RUST_SERVER_NAME== reset?
==RUST_SERVER_NAME== has not had enough wipes recorded to reveal its 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 27 days 3 hours.
Player count
Where does ==RUST_SERVER_NAME== place in the wider field of Rust servers?
In the top 70% of all ranked servers, ==RUST_SERVER_NAME== sits at #15,895 for player hours over the last seven days.
How many players does ==RUST_SERVER_NAME== usually have?
It has been 27 days 2 hours since ==RUST_SERVER_NAME== was last seen, and it is offline right now.
Lists and filters
How should you read the tags on ==RUST_SERVER_NAME==?
The game's browser takes its cue from the tags ==RUST_SERVER_NAME== has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; 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; cs166586 (Build): The game build is 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^p (PvE): Players do not fight one another here; the world is the danger. 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_SERVER_NAME==?
These Rust Server Score lists count ==RUST_SERVER_NAME== among them: Best community servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Rules and settings
What settings and rules apply on ==RUST_SERVER_NAME==?
You will find no gather rate in the name of ==RUST_SERVER_NAME==. The group limit stays at the game's default of 8 players. It runs pve, no PvP between players. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
==RUST_SERVER_NAME== runs which map?
A procedural map of size 3,500 and seed 580500824, generated by the game, is what ==RUST_SERVER_NAME== runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to ==RUST_SERVER_NAME==?
Enter client.connect 133.88.121.224:28015 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 asmp50,ptrak,$r?,v2634,^p,gmrust,cs166586,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
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.
cs166586
BuildThe game build is 166586.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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 (D); standing is the one to work on (F).