On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,335top 69%
Last wipe15d 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,335 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: 130 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 373 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
Wed 14 Oct, 13:15 UTC15d 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
RustServer_6101 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 160.251.175.78:28015.
Is RustServer_6101 up, and how steady is its uptime?
Right now, RustServer_6101 is online. About 5 days 14 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.
Does RustServer_6101 perform well?
It averaged 130 server fps over the last 48 hours, with a low of 98. Buildings, deployables and everything else in the world added up to as many as 45,825 entities. Up to 2,485 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is RustServer_6101 running?
The server RustServer_6101 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 schedule
When does RustServer_6101 wipe, and how often?
The record holds too few of RustServer_6101's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 15 days.
What should you expect from wipe day on RustServer_6101?
Recent wipes have peaked at 0 players on average. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does RustServer_6101 place in the wider field of Rust servers?
In the top 69% of all ranked servers, RustServer_6101 sits at #15,335 for player hours over the last seven days.
What does the population on RustServer_6101 look like?
With 50 slots available, RustServer_6101 currently has 0 players. For the last seven days, the average number of players was 0.
Lists and filters
What is meant by the tags on RustServer_6101?
The game's browser takes its cue from the tags RustServer_6101 has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Its slot count is 50; 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): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set. 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 RustServer_6101?
These Rust Server Score lists count RustServer_6101 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.
Server rules
How is RustServer_6101 set up, and what rules does it keep?
The name of RustServer_6101 gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map RustServer_6101 uses?
A procedural map of size 3,000 and seed 32736, generated by the game, is what RustServer_6101 runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How do you get onto RustServer_6101?
Enter client.connect 160.251.175.78: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 modeSurvival in the standard Rust style.
mp50
Max playersIts slot count is 50.
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
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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).