On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,327top 69%
Last wipe9d 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
31/ 100
F
Working its way up from the back of the class: #15,327 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 128 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
49/ 100
D
Slipped a little: down 202 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
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 69% 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
Mon 19 Oct, 18:26 UTC9d 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_20607. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 160.251.209.182:28015.
How reliable is RustServer_20607, and is it up?
You can join now: RustServer_20607 is online. The uptime it reports puts the last restart at about 5 days 17 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does RustServer_20607 run?
The average over the last 48 hours was 128 server fps, and it never went below 104. At its peak, it held 46,931 entities, including buildings, deployables and all else in the world. Up to 2,472 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is RustServer_20607 on?
The server RustServer_20607 is on Rust network protocol 2635 and build 168909 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does RustServer_20607 wipe, and how often?
There are too few wipes on record for RustServer_20607 to show a 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 9 days 22 hours.
What happens on RustServer_20607 when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does RustServer_20607 sit among Rust servers?
Over the last seven days, RustServer_20607 has #15,327 for player hours, in the top 69% of all ranked servers.
Is RustServer_20607 a busy server?
RustServer_20607 is showing 0 players right now, with 50 slots in total. For the last seven days, the average number of players was 0.
Tags and filters
How should you read the tags on RustServer_20607?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server are the tags RustServer_20607 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 Rust Server Score filters and lists feature RustServer_20607?
Rust Server Score lists that include RustServer_20607: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
What settings and rules apply on RustServer_20607?
The name of RustServer_20607 gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
RustServer_20607 runs which map?
A procedural map of size 3,000 and seed 28026, generated by the game, is what RustServer_20607 runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How should you connect to RustServer_20607?
Enter client.connect 160.251.209.182: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?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).