Station XX-9118 · no signal
BuildLab
Offline 193.141.60.250:47831 checked 5d ago
- Players now
- 1/ 4
- 25% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #9,118
- top 41%
- 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
- M –not enough readings
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 41% 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
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 21 Oct, 19:57 UTC7d ago | M0.0■steady | 1 | – | running | 1 | |
| Fri 2 Oct, 16:57 UTC26d ago | M0.0▲rising | 1 | held half | 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?
A procedural map runs on BuildLab, generated by the game.
Which settings and rules apply on BuildLab?
You will find no gather rate in the name of BuildLab. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on BuildLab right now?
A reading taken now finds BuildLab offline; the most recent activity was 5 days 22 hours ago. The seven-day average is 1 players, with a peak of 1.
How does BuildLab rank against other Rust servers?
Over the last seven days, BuildLab recorded enough player hours to reach #9,118 worldwide, placing it in the top 41% of all ranked servers.
Server facts
How reliably does BuildLab stay online?
As recorded now, BuildLab is not reachable, the last contact having been 5 days 22 hours ago. Of the 168 hours in the last 7 full days, it was up for 6, or 4% of the time. 27 September 2026 is when Rust Server Trends first recorded it.
Which region does BuildLab run from?
A region is not published by BuildLab. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 193.141.60.250:47831 is the address it uses.
Which Rust version is BuildLab running?
On Windows, BuildLab runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on BuildLab?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
On what timetable does BuildLab run its wipes?
On record so far are too few of BuildLab's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 7 days 14 hours.
Tags
What do the server tags on BuildLab mean?
The game's server browser reads the tags BuildLab publishes: gmrust (Game mode): The game mode is standard Rust survival; mp4 (Max players): Slots: 4; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed 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?
You will find BuildLab on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust build and creative servers, live. These filters bring it up 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.
Join the server
What steps get you onto BuildLab?
Enter client.connect 193.141.60.250: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.