On the class lists: D (46), with population over 48 hours and no performance mark.
Players now0/ 50% full
7-day average0peak 1
Rank#14,680top 66%
Last wipe27d agono schedule published
Next wipe7d 19hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 5 on average. Plenty of space to grow.
Standingrank on player hours
34/ 100
F
Working its way up from the back of the class: #14,680 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
2/ 100
F
Needs to work on its frame rate: 1 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
52/ 100
D
Moving up: up 493 places this week.
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 66% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 19h.
The force wipe · high confidence
wipe-day peak0players, last three wipes
Coming wipes
7d 19hThu 5 Nov, 19:00 UTCFW
35d 19hThu 3 Dec, 19:00 UTCFW
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
Thu 1 Oct, 17:57 UTCFW27d 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
No region is published for build. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 151.80.25.50:28011.
Is build up, and how steady is its uptime?
The server is up: build is online now. About 2 days 16 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. It was first seen by Rust Server Score on 13 September 2026.
Is build smooth to play on?
The average over the last 48 hours was 1 server fps, and it never went below 1. At its peak, it held 101,239 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,936 MB. Players feel lag when fps drops and entities pile up.
What Rust version is build on?
Rust network protocol 2635 and build 168909 on Linux is what build runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does build wipe its map?
The force wipe each month is the only wipe build takes. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 27 days 5 hours.
What happens on build when wipe day arrives?
Recent wipes have peaked at 0 players on average. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does build place in the wider field of Rust servers?
Over the last seven days, build has #14,680 for player hours, in the top 66% of all ranked servers.
How many players does build usually have?
With 5 slots available, build currently has 0 players. Averaging 0 players over seven days, it peaked at 1. The busiest time in the last 48 hours was 16:00 UTC, with an average of 0 players.
Tags
What is meant by the tags on build?
You'll see build tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): 5 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does build appear in the Rust Server Score lists and filters?
These Rust Server Score lists count build among them: Rust build and creative servers and 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.
Server rules
What settings and rules apply on build?
The name of build gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on build?
build runs a game-generated procedural map at size 4,250, seed 2665. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to build?
To connect, start Rust, press F1, and type client.connect 151.80.25.50:28011. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max players5 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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 uptime (A+); population is the one to work on (F).