Rust Server TrendsSeismic network · station log
Recording Stations11,722 Players56,412 Active3,390 Wipes · 3 h135 48 h

Station XX-12923 · no signal

TEST1

Offline 94.41.131.190:28015 checked 10d ago

Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#12,923
top 59%
Last wipe
11d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-12923 · 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
15k10k15k20k1 Oct5 Oct11 Oct15 Oct20 Oct24 Oct

Top 59% 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

00.250.50.751+0h+9h+19h+28h+38h+47h

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, 14:11 UTC11d ago M0.0rising 1 – running 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 · 515 on average
484/ 525
Rustoria.co - EU Main EU · groups of 16+ · weekly · 338 on average
27/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 335 on average
50/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 317 on average
234/ 275
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 279 on average
86/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 262 on average
94/ 150
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on TEST1?

TEST1 uses a procedural map, which the game generates.

Which settings and rules apply on TEST1?

No gather rate appears in the name of TEST1. At the game's default, groups can have up to 8 players. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on TEST1 right now?

A reading taken now finds TEST1 offline; the most recent activity was 10 days 5 hours ago.

How does TEST1 rank against other Rust servers?

The last seven days of player hours place TEST1 at #12,923, in the top 59% of all ranked servers.

Operator and location

How reliably does TEST1 stay online?

As recorded now, TEST1 is not reachable, the last contact having been 10 days 5 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 1 October 2026.

Which region does TEST1 run from?

Nothing about a region comes from TEST1. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 94.41.131.190:28015.

What build of Rust does TEST1 use?

TEST1 is running Rust network protocol 2634 and build 167781 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 TEST1?

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

How often does TEST1 wipe, and on which days?

The rhythm of TEST1 cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 11 days 9 hours.

Server tags

What do the server tags on TEST1 mean?

The game's server browser reads the tags TEST1 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; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $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 TEST1 appear?

These Rust Server Trends lists include TEST1: 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.

Join the server

What steps get you onto TEST1?

To join, enter client.connect 94.41.131.190: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,cs167781,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.
cs167781
Build The game build is 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$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.