Offline 159.26.105.78:28015 checked 24d ago
Build System Dev
Connect
srv = rust.server("159.26.105.78:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 20:09 UTC24d ago | 1 | NaN | 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 159.26.105.78:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 23:38 UTC
- hostname
- –
- first seen
- 1 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | EU · groups of 8+ · 112 on average | 38/999 |
| 1 | [NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | NA · groups of 8+ · 89 on average | 117/999 |
| 2 | [AU] Rusticated.com - Creative Sandbox | Build | Never Wipes | OC · groups of 8+ · 51 on average | 65/150 |
| 3 | Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA | EU · groups of 30+ · weekly · 35 on average | 18/100 |
| 4 | AQRUX RUST BUILD | CREATIVE | SANDBOX | EU · groups of 8+ · monthly · 23 on average | 8/100 |
| 5 | KoalaKopters - Minicopter / Helicopter Training|Arena|Dogfight | groups of 8+ · 23 on average | 15/100 |
Quick answers
From the figures on this page.
Population data
How does Build System Dev compare in the rankings?
Rank #13,887 on seven-day player hours for Build System Dev, within the top 61% of all ranked servers.
How many players does Build System Dev hold at once?
Offline now for Build System Dev, with the last sample 24 days 4 hours ago.
Server facts
Which Rust version is Build System Dev on?
The build is Rust network protocol 2634 and build 166652 on Windows, run by Build System Dev. The protocol has to match before you can join, and Steam does the updating.
Is Build System Dev up, and what does its uptime show?
Build System Dev is offline at this refresh; the last response came 24 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 1 October 2026.
Where does Build System Dev sit?
No region is published by Build System Dev. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 159.26.105.78:28015 is its address.
Map and rules
Which rules apply on Build System Dev, and what settings?
The name Build System Dev carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
What is the map on Build System Dev?
The game generates its map: procedural, on Build System Dev.
Wipes and dates
On what schedule does Build System Dev wipe?
Too few wipes are on record for Build System Dev to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 24 days 5 hours ago.
What is wipe day on Build System Dev like?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does Build System Dev appear among Rust Data lists and filters?
On Rust Data, Build System Dev appears in these lists: Modded Rust servers and Servers with build or creative tags. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Build System Dev hold?
The game's server browser reads these tags from Build System Dev: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): The server runs build 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join Build System Dev?
Enter client.connect 159.26.105.78:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.