A quiet classroom so far: 1 of 4 on average. Plenty of space to grow.
Standingrank on player hours
58/ 100
C−
Working its way up from the back of the class: #9,443 on player hours.
Uptimehours on the list, last 48
10/ 100
F
Attendance needs work: on the list only 5 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (C−); uptime 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 42% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
··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.
usual gap19.1 daysbetween real wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 21 Oct, 20:02 UTC7d ago
–
–
running
0
Fri 2 Oct, 17:05 UTC26d ago
–
–
19.1 days
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 BuildLab. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 157.173.25.164:47831.
Is BuildLab up, and how steady is its uptime?
At this moment, BuildLab is offline; the last time it was seen was 39 hours ago. For the last 7 full days, it was up 5 of 168 hours, or 3% of the time. The first sighting by Rust Server Score was on 30 September 2026.
What Rust version is BuildLab on?
The server BuildLab is on Rust network protocol 2635 and build 168909 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does BuildLab wipe, and how often?
There are too few wipes on record for BuildLab 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 7 days 13 hours.
Population
Where does BuildLab sit among Rust servers?
Over the last seven days, BuildLab has #9,443 for player hours, in the top 42% of all ranked servers.
What does the population on BuildLab look like?
It has been 39 hours since BuildLab was last seen, and it is offline right now. Averaging 1 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 14:00 UTC, averaging 1 players.
Tags
What is meant by the tags on BuildLab?
The game's browser takes its cue from the tags BuildLab has set: gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): 4 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): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Where does BuildLab appear in the Rust Server Score lists and filters?
These Rust Server Score lists count BuildLab among them: Modded Rust servers, graded and Rust build and creative servers. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
What settings and rules apply on BuildLab?
The name of BuildLab gives no gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on BuildLab?
BuildLab runs a procedural map, which the game generates.
Getting in
How do you get onto BuildLab?
Enter client.connect 157.173.25.164:47831 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 asmp4,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp4
Max players4 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
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 standing (C−); uptime is the one to work on (F).