On the class lists: F (42), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#13,666top 61%
Last wipe25d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
39/ 100
F
Working its way up from the back of the class: #13,666 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 86 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
35/ 100
F
Slipped a little: down 4,223 places this week. Nothing a good wipe can't fix.
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
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 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 61% 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 peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 21:09 UTC25d ago
0
–
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 RustServer_2604. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 133.88.121.242:28015.
How dependable is RustServer_2604, and is it online at the moment?
Right now, RustServer_2604 is online. About 5 days 21 hours ago, it restarted, based on the uptime it reports. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Is RustServer_2604 smooth to play on?
The average over the last 48 hours was 86 server fps, and it never went below 56. At its peak, it held 45,129 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,293 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is RustServer_2604 running?
Rust network protocol 2635 and build 168909 on Linux is what RustServer_2604 runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does RustServer_2604 wipe, and how often?
RustServer_2604 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. It has been running its current world for 25 days 23 hours.
What should you expect from wipe day on RustServer_2604?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does RustServer_2604 sit among Rust servers?
In the top 61% of all ranked servers, RustServer_2604 sits at #13,666 for player hours over the last seven days.
Is RustServer_2604 a busy server?
Right now, 0 players are on RustServer_2604, which has 50 slots. The seven-day average is 0 players, with a peak of 2.
Tags
What do RustServer_2604's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags RustServer_2604 publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show RustServer_2604?
These Rust Server Score lists count RustServer_2604 among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
How is RustServer_2604 set up, and what rules does it keep?
You will find no gather rate in the name of RustServer_2604. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on RustServer_2604?
The game generates the procedural map on RustServer_2604 at size 3,000 with seed 20682. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to RustServer_2604?
To connect, start Rust, press F1, and type client.connect 133.88.121.242:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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).