Rust Server TrendsSeismic network · station log
Recording Stations11,739 Players61,775 Active3,380 Wipes · 3 h186 48 h

Station XX-13816 · no signal

Name of Server as Shown on the Client Server List

Offline 125.253.50.15:28015 checked 27d ago

Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,816
top 60%
Last wipe
29d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-13816 · 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 10 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
15k10k15k20k20 Sep24 Sep28 Sep1 Oct5 Oct9 Oct

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

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
1.4 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

Tue 29 SepTue 29 SepFri 25 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 8 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 29 Sep, 15:39 UTC29d ago M0.0rising 1 – running 0
Tue 29 Sep, 01:29 UTC30d ago M0.0rising 1 – 0.6 days 0
Fri 25 Sep, 03:05 UTC34d ago M0.0steady 1 – 3.9 days 1
Thu 24 Sep, 00:48 UTC35d ago M0.0rising 1 – 1.1 days 0
Tue 22 Sep, 06:29 UTC37d ago M0.0rising 1 – 1.8 days 0

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 · 516 on average
446/ 475
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
386/ 375
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
48/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average
30/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average
49/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 243 on average
147/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Name of Server as Shown on the Client Server List?

Name of Server as Shown on the Client Server List uses a procedural map, which the game generates.

Which settings and rules apply on Name of Server as Shown on the Client Server List?

You will find no gather rate in the name of Name of Server as Shown on the Client Server List. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on Name of Server as Shown on the Client Server List?

No players are recorded on Name of Server as Shown on the Client Server List at this moment; it is offline, and the last sighting was 27 days 4 hours ago.

How does Name of Server as Shown on the Client Server List rank against other Rust servers?

Over the last seven days, Name of Server as Shown on the Client Server List recorded enough player hours to reach #13,816 worldwide, placing it in the top 60% of all ranked servers.

Operator and location

How reliably does Name of Server as Shown on the Client Server List stay online?

Name of Server as Shown on the Client Server List is down at the moment; the last recorded contact was 27 days 4 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 17 September 2026.

Where in the world is Name of Server as Shown on the Client Server List hosted?

Nothing about a region comes from Name of Server as Shown on the Client Server List. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 125.253.50.15:28015.

What build of Rust does Name of Server as Shown on the Client Server List use?

Rust network protocol 2634 and build 166569 on Windows is what Name of Server as Shown on the Client Server List runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on Name of Server as Shown on the Client Server List?

1 players, on average, was the busiest crowd at its recent wipes. 8 hours after the latest wipe, the crowd peaked.

On what timetable does Name of Server as Shown on the Client Server List run its wipes?

There is no next wipe to predict at Name of Server as Shown on the Client Server List, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 29 days 15 hours is how long the current world has been running.

Tags

What do the server tags on Name of Server as Shown on the Client Server List mean?

These are the tags Name of Server as Shown on the Client Server List publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166569 (Build): Game build: 166569; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set. 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 Name of Server as Shown on the Client Server List appear?

These Rust Server Trends lists include Name of Server as Shown on the Client Server List: 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.

How to join

What steps get you onto Name of Server as Shown on the Client Server List?

To join, enter client.connect 125.253.50.15:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166569,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players 10 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs166569
Build Game build: 166569.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$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.