Rust Server TrendsSeismic network · station log
Recording Stations11,658 Players32,604 Active2,794 Wipes · 3 h75 48 h

Station XX-15427 · no signal

Solo Build Sandbox

Offline 188.24.7.107:28015 checked 40d ago

pve
Connect
Players now
0/ 5
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,427
no region published
Last wipe
40d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15427 · 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
0of 5 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep
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
Fri 18 Sep, 14:23 UTC40d 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
VajasKifli groups of 8+ · monthly · 1 on average
0/ 30
|PvE| RUSTTRAVKA [Zombie|SkillsRPG|RaidBases|Events|Loot+] groups of 10+ · monthly · 14 on average
10/ 200
CZ/EU Farming Industry PVE EU · groups of 8+ · monthly · 4 on average
0/ 50
CZ/SK PVE!! No raid_No kill :-) RUSTUJ groups of 8+ · 3 on average
1/ 30
BroinRust [PVE CLASSIC EU/EA] EU · groups of 8+ · monthly · 3 on average
2/ 200
BroinRust [PVE MOD EU/EA] EU · groups of 10+ · biweekly · 3 on average
3/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Solo Build Sandbox?

A procedural map runs on Solo Build Sandbox, generated by the game.

Which settings and rules apply on Solo Build Sandbox?

You will find no gather rate in the name of Solo Build Sandbox. At the game's default, groups can have up to 8 players. pve is the game mode, no combat against other players. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on Solo Build Sandbox right now?

A reading taken now finds Solo Build Sandbox offline; the most recent activity was 40 days 7 hours ago.

How does Solo Build Sandbox rank against other Rust servers?

Over the last seven days, Solo Build Sandbox recorded enough player hours to reach #15,427 worldwide, placing it in the top – of all ranked servers.

Operator and location

How reliably does Solo Build Sandbox stay online?

Solo Build Sandbox is down at the moment; the last recorded contact was 40 days 7 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 16 September 2026.

Which region does Solo Build Sandbox run from?

A region is not published by Solo Build Sandbox. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 188.24.7.107:28015.

What build of Rust does Solo Build Sandbox use?

Solo Build Sandbox is running Rust network protocol 2633 and build 164530 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on Solo Build Sandbox?

On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 0 hours after the wipe.

How often does Solo Build Sandbox wipe, and on which days?

The rhythm of Solo Build Sandbox cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 40 days 14 hours.

Lists and tags

What do the server tags on Solo Build Sandbox mean?

These are the tags Solo Build Sandbox publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp5 (Max players): 5 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^p (PvE): The danger comes from the world, not from other players. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Solo Build Sandbox appear?

The Rust Server Trends lists that take in Solo Build Sandbox are: Rust build and creative servers, live, Rust community servers without the side modes and Rust PvE servers. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.

Join the server

How do you connect to Solo Build Sandbox?

To join, enter client.connect 188.24.7.107: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 mp5,ptrak,$r?,v2633,^p,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp5
Max players 5 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs164530
Build The game build is 164530.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Gameplay

^p
PvE The danger comes from the world, not from other players.

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.