Statistical profileOnline
BuildLab
193.141.60.250:47831 checked 7m ago
Connect to this server
1. Main points
Players now
1/ 4
25% full
7-day average
1
peak 1
Rank
#9,789
top 44%
Last wipe
7d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- There were 1 players on it, 25% of its 4 slots.
- Over the last seven days it averaged 1 players, with a peak of 1.
- It ranks #9,789 of all ranked servers, the top 44%, on player hours over the last seven days.
- Its current map went up 7d ago.
2. Players
Figure 1: Players on BuildLab
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 44% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo 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 gap
19.1 days
between real wipes
Wipe-day peak
1
players, last three wipes
Crowd held
100%
of its cycles kept half the crowd
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 21 Oct, 19:57 UTC7d ago | 1 | – | running | 1 |
| Fri 2 Oct, 16:57 UTC27d ago | 1 | held half | 19.1 days | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of BuildLab
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of BuildLab
What the server publishes and what was recorded
| Address | 193.141.60.250:47831 |
|---|---|
| Region | – |
| Max players | 4 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 21 Oct 2026, 20:02 UTC |
| Hostname | – |
| First seen | 27 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| [EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | EU · groups of 8+ · 116 on average | 170 / 999 |
| [NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | NA · groups of 8+ · 90 on average | 151 / 999 |
| [AU] Rusticated.com - Creative Sandbox | Build | Never Wipes | OC · groups of 8+ · 53 on average | 30 / 150 |
| Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA | EU · groups of 30+ · weekly · 37 on average | 1 / 100 |
| AQRUX RUST BUILD | CREATIVE | SANDBOX | EU · groups of 8+ · monthly · 24 on average | 41 / 100 |
| KoalaKopters - Minicopter / Helicopter Training|Arena|Dogfight | groups of 8+ · 23 on average | 29 / 100 |
10. Quick answers
From the figures on this page.
Wipe schedule
When does BuildLab wipe, and how often?
The rhythm of BuildLab's wipes cannot yet be told: too few are on record. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. 7 days 22 hours have passed since this world was made.
On BuildLab, what happens on wipe day?
The average busiest point of its recent wipes drew 1 players. The peak of the latest wipe's crowd came 0 hours after it began. Half that peak was held until the next wipe in 100% of its recent wipes.
Server record
What does the record show for the uptime and current status of BuildLab?
BuildLab is online at the time of this release. A total of 6 of 168 hours were up over 7 full days, which is 4% of the time. First recorded by Rust Census on 27 September 2026.
What location has been recorded for BuildLab?
A region is not published by BuildLab. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. 193.141.60.250:47831 is its address.
Which Rust version is BuildLab running?
This release lists BuildLab on Rust network protocol 2635 and build 168909, running on Windows. The same protocol is required for your game to join, and Steam updates it for you.
Player figures
What are the current player figures for BuildLab?
At counting time BuildLab recorded 1 players across 4 slots. This release records a seven-day average of 1 players and a peak of 1. The busiest hour in the last 48 hours was 13:00 UTC, with an average of 1 players.
In the rankings of Rust servers, where is BuildLab placed?
The rank for BuildLab is #9,789 on seven-day player hours, in the top 44% of ranked servers.
Lists and tags
Which Rust Census filters and lists cover BuildLab?
Included in these Rust Census lists is BuildLab: Modded Rust servers, counted and Rust build servers: listed. It appears under these 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.
The tags on BuildLab: what do they indicate?
These are the tags BuildLab publishes for the game's server browser to read: gmrust (Game mode): Survival play, in the standard Rust format; mp4 (Max players): Slots: 4; ts8 (Group limit): This is the game default: 8 to a team; v2635 (Protocol): To connect, your game version must match protocol 2635; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): Plugins or settings alter the game on this modded server. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Rules, map
Which map has been recorded for BuildLab?
A procedural map runs on BuildLab, generated by the game.
How is BuildLab configured, and what rules does it keep?
No gather rate is given in the name of BuildLab. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Modded is its section in the server browser, because plugins or settings change the game. Oxide plugins are recorded on it. The server runs VAC, Valve's anti-cheat.
How to join
How can you connect to BuildLab?
You can open the console in Rust with F1 and enter client.connect 193.141.60.250:47831; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp4,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp4 | Max players Slots: 4. |
ts8 | Group limit This is the game default: 8 to a team. |
v2635 | Protocol To connect, your game version must match protocol 2635. |
cs168909 | Build The server runs game build 168909. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide Plugins are handled by Oxide (uMod) on this server. |
|---|---|
^z | Modded Plugins or settings alter the game on this modded server. |
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.