Rust Server TrendsSeismic network · station log
Recording Stations11,858 Players85,113 Active3,958 Wipes · 3 h170 48 h

Station XX-13887 · no signal

Build System Dev

Offline 159.26.105.78:28015 checked 23d ago

moddedoxide
Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,887
top 61%
Last wipe
23d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-13887 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct3 Oct5 Oct6 Oct8 Oct10 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

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.

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 3 Oct, 20:09 UTC24d ago M0.0rising 1 – running 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
191/ 999
99/ 999
24/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 35 on average
12/ 100
AQRUX RUST BUILD | CREATIVE | SANDBOX EU · groups of 8+ · monthly · 23 on average
25/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Build System Dev?

The map on Build System Dev is procedural, produced by the game.

Which settings and rules apply on Build System Dev?

No gather rate appears in the name of Build System Dev. At the game's default, groups can have up to 8 players. survival is the game mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Player counts

How many players are recorded on Build System Dev right now?

Build System Dev is not responding at this moment and is offline, last seen 23 days 19 hours ago.

How does Build System Dev rank against other Rust servers?

Over the last seven days, Build System Dev recorded enough player hours to reach #13,887 worldwide, placing it in the top 61% of all ranked servers.

Server facts

How reliably does Build System Dev stay online?

As recorded now, Build System Dev is not reachable, the last contact having been 23 days 19 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 1 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is Build System Dev hosted?

Nothing about a region comes from Build System Dev. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 159.26.105.78:28015 is the address it uses.

Which Rust version is Build System Dev running?

On Windows, Build System Dev runs Rust network protocol 2634 and build 166652. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Build System Dev?

On average, the busiest point of its recent wipes drew 1 players. 0 hours after the latest wipe, the crowd peaked.

On what timetable does Build System Dev run its wipes?

On record so far are too few of Build System Dev's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 23 days 20 hours.

Tags

What do the server tags on Build System Dev mean?

These are the tags Build System Dev publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166652 (Build): The game build is 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running 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 Build System Dev appear?

These Rust Server Trends lists include Build System Dev: Modded Rust servers, tracked live and Rust build and creative servers, live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

What steps get you onto Build System Dev?

To join, enter client.connect 159.26.105.78:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players Slots: 10.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs166652
Build The game build is 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed 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.

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.