Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h0 48 h

Station XX-13894 · no signal

TEST

Offline 178.66.0.10:28015 checked 26d ago

Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,894
top 60%
Last wipe
27d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-13894 · 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
15k10k15k20k21 Sep24 Sep28 Sep1 Oct5 Oct8 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.1 daysbetween real wipes
on rhythm
60%of its recent wipes
wipe-day peak
5players, last three wipes

The first 48 hours of its last wipes

Thu 1 OctWed 30 SepTue 29 Sep
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 3 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 17:09 UTC FW27d ago M0.0rising 5 – running 4
Wed 30 Sep, 19:24 UTC28d ago M0.3rising 5 – 0.9 days 3
Tue 29 Sep, 16:50 UTC29d ago M0.7rising 5 – 1.1 days 0
Mon 28 Sep, 14:23 UTC30d ago M0.5rising 4 – 1.1 days 1
Sun 27 Sep, 13:22 UTC31d ago M0.5rising 5 – 1 days 2
Sat 26 Sep, 05:34 UTC32d ago M0.7rising 5 – 1.3 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 · 552 on average
636/ 675
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
485/ 525
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 299 on average
59/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 298 on average
36/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 271 on average
138/ 200
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 254 on average
255/ 300
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on TEST?

A procedural map runs on TEST, generated by the game.

Which settings and rules apply on TEST?

No gather rate appears in the name of TEST. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. 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 TEST right now?

TEST is not responding at this moment and is offline, last seen 26 days 22 hours ago.

How does TEST rank against other Rust servers?

The last seven days of player hours place TEST at #13,894, in the top 60% of all ranked servers.

Server facts

How reliably does TEST stay online?

No contact with TEST right now, and the last recorded contact was 26 days 22 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 21 September 2026 is when Rust Server Trends first recorded it.

Where in the world is TEST hosted?

A region is not published by TEST. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 178.66.0.10:28015.

What build of Rust does TEST use?

TEST is running Rust network protocol 2634 and build 166494 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on TEST?

5 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 3 hours after the wipe.

How often does TEST wipe, and on which days?

There is no next wipe to predict at TEST, 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. 27 days is how long the current world has been running.

Server tags

What do the server tags on TEST mean?

The game's server browser reads the tags TEST publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): The game build is 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $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 TEST appear?

The Rust Server Trends lists that take in TEST are: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

How do you connect to TEST?

Enter client.connect 178.66.0.10: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 mp10,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players Slots: 10.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166494
Build The game build is 166494.
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.