On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak 1
Rank#14,269top 64%
Last wipe8d 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 10 on average. Plenty of space to grow.
Standingrank on player hours
36/ 100
F
Working its way up from the back of the class: #14,269 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
69/ 100
C+
Slows down under load at times: 41 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
27/ 100
F
Lost ground: down 6,478 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (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 64% 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 peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 41 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 20 Oct, 18:36 UTC8d ago
2
–
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
No region is published for RustServer_5962. Rust Server Score takes the server's word for its location and does not trace the hardware. 160.251.201.172:28015 is the address to use.
How dependable is RustServer_5962, and is it online at the moment?
Right now, RustServer_5962 is online. The uptime it reports puts the last restart at about 6 days 17 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Does RustServer_5962 perform well?
The average over the last 48 hours was 41 server fps, and it never went below 28. Up to 120,835 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 4,893 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is RustServer_5962 on?
Rust network protocol 2635 and build 168909 on Linux is what RustServer_5962 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does RustServer_5962 reset?
RustServer_5962 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. 8 days 22 hours have passed since this world was made.
What happens on RustServer_5962 when wipe day arrives?
The average peak on its recent wipes was 2 players. 41 hours after the latest wipe began, the crowd hit its peak.
Population
Where does RustServer_5962 sit among Rust servers?
In the top 64% of all ranked servers, RustServer_5962 sits at #14,269 for player hours over the last seven days.
What does the population on RustServer_5962 look like?
Right now, 0 players are on RustServer_5962, which has 10 slots. The seven-day average is 0 players, with a peak of 1.
Lists and filters
What do RustServer_5962's tags stand for?
The game's browser takes its cue from the tags RustServer_5962 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): 10 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): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server. 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 RustServer_5962?
Rust Server Score lists that include RustServer_5962: 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; Last wipe: In the last 2 weeks.
Map and rules
What settings and rules apply on RustServer_5962?
The name of RustServer_5962 gives no gather rate. The group limit stays at the game's default of 8 players. survival is the mode 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. VAC, Valve's anti-cheat, is enabled.
RustServer_5962 runs which map?
The game generates the procedural map on RustServer_5962 at size 4,500 with seed 28423. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How do you get onto RustServer_5962?
Enter client.connect 160.251.201.172: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 asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max players10 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
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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 term to build on. Strongest in uptime (A+); population is the one to work on (F).