Rust Server TrendsSeismic network · station log
Recording Stations11,811 Players86,563 Active3,948 Wipes · 3 h165 48 h

Station XX-14428 · no signal

My Solo Test Server

Offline 5.140.233.21:28015 checked 12d ago

Connect
Players now
1/ 5
20% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,428
top 67%
Last wipe
12d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-14428 · 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 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
15k10k15k20k9 Oct12 Oct15 Oct17 Oct20 Oct23 Oct

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

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

No hourly players around its wipes yet.

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 16 Oct, 10:03 UTC12d ago M0.0steady 1 – – running 1

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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 547 on average
647/ 725
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
500/ 525
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 303 on average
64/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 303 on average
43/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 268 on average
158/ 225
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 261 on average
233/ 250
Readings, in words

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on My Solo Test Server?

You will find no gather rate in the name of My Solo Test Server. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on My Solo Test Server?

No players are recorded on My Solo Test Server at this moment; it is offline, and the last sighting was 12 days 5 hours ago.

How does My Solo Test Server rank against other Rust servers?

On player hours for the past week, My Solo Test Server sits at #14,428, which puts it inside the top 67% of every ranked server.

Operator and location

How reliably does My Solo Test Server stay online?

As recorded now, My Solo Test Server is not reachable, the last contact having been 12 days 5 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 9 October 2026 is when Rust Server Trends first recorded it.

Which region does My Solo Test Server run from?

Nothing about a region comes from My Solo Test Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 5.140.233.21:28015 is the address it uses.

Which Rust version is My Solo Test Server running?

My Solo Test Server is running Rust network protocol 2634 and build 167231 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on My Solo Test Server?

The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 0 hours after the wipe.

On what timetable does My Solo Test Server run its wipes?

The rhythm of My Solo Test Server 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 5 November at 19:00 UTC. The present world dates from 12 days 6 hours.

Server tags

What do the server tags on My Solo Test Server mean?

These are the tags My Solo Test Server publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp5 (Max players): The server has 5 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; cs167231 (Build): Game build: 167231; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code. 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 My Solo Test Server appear?

These Rust Server Trends lists include My Solo Test Server: 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; Last wipe: In the last 2 weeks.

Connecting

What steps get you onto My Solo Test Server?

You can connect by pressing F1 in Rust and typing client.connect 5.140.233.21: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 mp5,ptrak,$r?,v2634,gmrust,cs167231,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp5
Max players The server has 5 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.
cs167231
Build Game build: 167231.
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.