RUST METRICSFlight deck · live data
Data live Servers11,667 Players48,316 Populated3,167 Fresh wipes 3 h118 Scan5 min
‹ All servers188.24.7.107:28015
Offline Full Queue Fresh wipe Wipe due No query

Solo Build Sandbox

Offline 188.24.7.107:28015 checked 40d ago

pve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,427no region published
Last wipe40d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep
PLAN

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 peak1players, 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 18 Sep, 14:23 UTC40d ago 1 – 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Solo Build Sandbox?

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

When does Solo Build Sandbox wipe?

To tell the rhythm of Solo Build Sandbox, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 40 days 18 hours ago the current world was made.

Lists and filters

How should you read the tags on Solo Build Sandbox?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Game build reading: 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players from Solo Build Sandbox. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Solo Build Sandbox appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Solo Build Sandbox: Build and creative servers, Rust community servers: live readings and Rust PvE servers. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.

Population

Where does Solo Build Sandbox sit in the rankings?

Player hours over seven days put Solo Build Sandbox at #15,427, in the top – of all ranked servers.

What is the population on Solo Build Sandbox?

Status for Solo Build Sandbox: offline. Last seen 40 days 12 hours ago.

Operator and location

Where does Solo Build Sandbox sit?

No region tag on Solo Build Sandbox. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 188.24.7.107:28015.

What Rust version is Solo Build Sandbox on?

Reading: Solo Build Sandbox, Rust network protocol 2633 and build 164530, Linux. Matching protocol is required to join. Let Steam update your game.

How reliable is Solo Build Sandbox, and is it online now?

Check: connection. Solo Build Sandbox is offline at this moment. Last contact was 40 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 September 2026.

Map and rules

What settings and rules apply on Solo Build Sandbox?

Check: gather rate. The name Solo Build Sandbox does not state one. 8 players per group, the default value. The mode is pve. Note the following: no combat against other players. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is Solo Build Sandbox on?

Procedural map on Solo Build Sandbox, made by the game's generator.

Connection

What do you do to join Solo Build Sandbox?

To join: start Rust, press F1 and type client.connect 188.24.7.107:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,^p,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players The server holds 5 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build Game build reading: 164530.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not 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.