Rust Server TrendsSeismic network · station log
Recording Stations11,719 Players48,039 Active3,199 Wipes · 3 h104 48 h

Station XX-13302 · no signal

My Rust Sandbox

Offline 144.124.192.121:28015 checked 16d ago

Connect
Players now
1/ 1
100% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,302
top 61%
Last wipe
21d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-13302 · 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 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
15k10k15k20k12 Oct13 Oct15 Oct16 Oct18 Oct19 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
【南瓜】Build-Test EA · groups of 8+ · 10 on average
4/ 101
Raichu Staging | F1 Spawn | Noclip | DLC Unlocked EU · groups of 8+ · 2 on average
0/ 25
155/ 999
194/ 999
49/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 37 on average
18/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on My Rust Sandbox?

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

Which settings and rules apply on My Rust Sandbox?

No gather rate appears in the name of My Rust Sandbox. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.

Live population

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

A reading taken now finds My Rust Sandbox offline; the most recent activity was 16 days 4 hours ago.

How does My Rust Sandbox rank against other Rust servers?

On player hours for the past week, My Rust Sandbox sits at #13,302, which puts it inside the top 61% of every ranked server.

Operator and location

How reliably does My Rust Sandbox stay online?

No contact with My Rust Sandbox right now, and the last recorded contact was 16 days 4 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 12 October 2026 is when Rust Server Trends first recorded it.

Which region does My Rust Sandbox run from?

Nothing about a region comes from My Rust 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 144.124.192.121:28015.

What build of Rust does My Rust Sandbox use?

Rust network protocol 2634 and build 166652 on Windows is what My Rust Sandbox runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

How often does My Rust Sandbox wipe, and on which days?

On record so far are too few of My Rust Sandbox's wipes to tell its rhythm. 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 21 days 19 hours.

Server tags

What do the server tags on My Rust Sandbox mean?

These are the tags My Rust Sandbox publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): Game build: 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code. 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 My Rust Sandbox appear?

You will find My Rust Sandbox on the following Rust Server Trends lists: Rust build and creative servers, live and Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

What steps get you onto My Rust Sandbox?

Enter client.connect 144.124.192.121: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 mp1,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp1
Max players 1 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs166652
Build Game build: 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

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.