Rust Server TrendsSeismic network · station log
Recording Stations11,749 Players55,156 Active3,381 Wipes · 3 h134 48 h

Station XX-13488 · no signal

Solo Sandbox

Offline 85.250.22.140:28015 checked 17d ago

moddedcarbon
Connect
Players now
1/ 500
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,488
top 61%
Last wipe
17d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-13488 · 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 500 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
15k10k15k20k11 Oct12 Oct14 Oct15 Oct17 Oct18 Oct

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

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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
162/ 999
186/ 999
42/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 37 on average
22/ 100
AQRUX RUST BUILD | CREATIVE | SANDBOX EU · groups of 8+ · monthly · 24 on average
8/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Solo Sandbox?

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

Which settings and rules apply on Solo Sandbox?

You will find no gather rate in the name of Solo Sandbox. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on Solo Sandbox?

A reading taken now finds Solo Sandbox offline; the most recent activity was 17 days ago.

How does Solo Sandbox rank against other Rust servers?

The last seven days of player hours place Solo Sandbox at #13,488, in the top 61% of all ranked servers.

Server details

How reliably does Solo Sandbox stay online?

Solo Sandbox is down at the moment; the last recorded contact was 17 days ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 11 October 2026 is when Rust Server Trends first recorded it.

Where in the world is Solo Sandbox hosted?

Nothing about a region comes from Solo Sandbox. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 85.250.22.140:28015.

What build of Rust does Solo Sandbox use?

On Windows, Solo Sandbox runs Rust network protocol 2634 and build 167398. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

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

Too few wipes of Solo Sandbox are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 17 days 7 hours is how long the current world has been running.

Lists and tags

What do the server tags on Solo Sandbox mean?

The game's server browser reads the tags Solo Sandbox publishes: gmrust (Game mode): Survival in standard Rust; mp500 (Max players): The server has 500 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167398 (Build): Game build: 167398; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. 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 Solo Sandbox appear?

These Rust Server Trends lists include Solo Sandbox: 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 Carbon ^y; Group limit: 5 or more.

Connecting

What steps get you onto Solo Sandbox?

Enter client.connect 85.250.22.140:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs167398,ts8,^z,^y

Game

gmrust
Game mode Survival in standard Rust.
mp500
Max players The server has 500 slots.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167398
Build Game build: 167398.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.