Rust Server TrendsSeismic network · station log
Recording Stations11,525 Players85,836 Active3,992 Wipes · 3 h134 48 h

Station XX-17030 · no signal

My Solo Sandbox

Offline 46.138.70.136:28015 checked 19d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#17,030
top 70%
Last wipe
19d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-17030 · 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 1 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
15k10k15k20k2 Nov3 Nov5 Nov6 Nov8 Nov9 Nov

Top 70% 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
Thu 5 Nov, 19:00 UTC FW15d ago – – – – running –

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
【南瓜】Build-Test EA · groups of 8+ · 11 on average
15/ 101
Raichu Staging | F1 Spawn | Noclip | DLC Unlocked EU · groups of 8+ · 2 on average
6/ 25
Local Sandbox groups of 8+ · 1 on average
1/ 2
119/ 999
40/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 29 on average
21/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on My Solo Sandbox?

My Solo Sandbox uses a procedural map, which the game generates.

Which settings and rules apply on My Solo Sandbox?

The name of My Solo Sandbox gives no gather rate. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Under Community in the server browser, it runs as a community server. The server has VAC on, Valve's anti-cheat.

Population

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

No players are recorded on My Solo Sandbox at this moment; it is offline, and the last sighting was 19 days 6 hours ago.

How does My Solo Sandbox rank against other Rust servers?

Over the last seven days, My Solo Sandbox recorded enough player hours to reach #17,030 worldwide, placing it in the top 70% of all ranked servers.

Operator and location

How reliably does My Solo Sandbox stay online?

My Solo Sandbox is down at the moment; the last recorded contact was 19 days 6 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 2 November 2026.

Where in the world is My Solo Sandbox hosted?

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

What build of Rust does My Solo Sandbox use?

My Solo Sandbox is running Rust network protocol 2635 and build 168909 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

On what timetable does My Solo Sandbox run its wipes?

The rhythm of My Solo Sandbox cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. The present world dates from 19 days 6 hours.

Server tags

What do the server tags on My Solo Sandbox mean?

These are the tags My Solo Sandbox publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): The server has 1 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

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

These Rust Server Trends lists include My Solo Sandbox: Rust build and creative servers, live and Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

How do you connect to My Solo Sandbox?

You can connect by pressing F1 in Rust and typing client.connect 46.138.70.136:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp1
Max players The server has 1 slots.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

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.