On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,268top 68%
Last wipe21d 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
32/ 100
F
Working its way up from the back of the class: #15,268 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: 134 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
33/ 100
F
Lost ground: down 5,133 places this week. A strong wipe could turn it round.
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 68% 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 peak3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 19 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 19:13 UTC21d ago
3
–
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_2626 leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 160.251.250.29:28015.
How reliable is RustServer_2626, and is it up?
Right now, RustServer_2626 is online. About 5 days 22 hours ago, it restarted, based on the uptime it reports. 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_2626 run?
It never fell below 104 server fps in the last 48 hours, averaging 134. At its peak, it held 46,707 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,378 MB. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does RustServer_2626 sit?
You will find RustServer_2626 on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does RustServer_2626 wipe, and how often?
There are too few wipes on record for RustServer_2626 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. The world it runs now was created 21 days 2 hours.
What happens on RustServer_2626 when wipe day arrives?
Across its recent wipes, the busiest moments averaged 3 players. Peak numbers came 19 hours into the latest wipe.
Player numbers
What position does RustServer_2626 hold in the rankings?
In the top 68% of all ranked servers, RustServer_2626 sits at #15,268 for player hours over the last seven days.
How many players does RustServer_2626 usually have?
Right now, 0 players are on RustServer_2626, which has 50 slots. A seven-day average of 0 players applies here.
Tags and filters
How should you read the tags on RustServer_2626?
The game's browser takes its cue from the tags RustServer_2626 has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Its slot count is 50; ts8 (Group limit): The limit is 8 per team, the default the game ships with; 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): A region code is not set here. 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_2626?
Rust Server Score lists that include RustServer_2626: 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.
Map and rules
What settings and rules apply on RustServer_2626?
The name of RustServer_2626 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_2626 runs which map?
A procedural map of size 3,000 and seed 2011, generated by the game, is what RustServer_2626 runs. 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_2626?
Enter client.connect 160.251.250.29: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 limitThe limit is 8 per team, the default the game ships with.
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 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).