Station XX-9460 · no signal
BuildLab
Offline 157.173.25.164:47831 checked 1d ago
- Players now
- 1/ 4
- 25% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 1
- Rank
- #9,460
- top 42%
- Last wipe
- 7d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 4 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +0into Tue 14:00 UTC
- Peak · 48 h
- 1most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 42% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 19.1 daysbetween real wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | 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. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on BuildLab?
BuildLab uses a procedural map, which the game generates.
Which settings and rules apply on BuildLab?
You will find no gather rate in the name of BuildLab. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on BuildLab?
A reading taken now finds BuildLab offline; the most recent activity was 38 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 1. Averaged over the last 48 hours, the busiest hour was 14:00 UTC at 1 players.
How does BuildLab rank against other Rust servers?
Over the last seven days, BuildLab recorded enough player hours to reach #9,460 worldwide, placing it in the top 42% of all ranked servers.
Server facts
How reliably does BuildLab stay online?
As recorded now, BuildLab is not reachable, the last contact having been 38 hours ago. It was up 3% of the time across the last 7 full days: 5 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 30 September 2026.
Which region does BuildLab run from?
Nothing about a region comes from BuildLab. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 157.173.25.164:47831.
Which Rust version is BuildLab running?
On Windows, BuildLab runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
How often does BuildLab wipe, and on which days?
The rhythm of BuildLab cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 7 days 11 hours.
Tags
What do the server tags on BuildLab mean?
Tags published by BuildLab and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp4 (Max players): 4 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does BuildLab appear?
The Rust Server Trends lists that take in BuildLab are: Modded Rust servers, tracked live and Rust build and creative servers, live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Join the server
How do you connect to BuildLab?
Enter client.connect 157.173.25.164:47831 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.