Rust Server TrendsSeismic network · station log
Recording Stations11,768 Players60,085 Active3,517 Wipes · 3 h135 48 h

Station GE-11484 · no signal

213 Test

Offline 195.93.149.246:28015 checked 11d ago

Connect
Players now
2/ 10
20% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#11,484
top 53%
Last wipe
12d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station GE-11484 · 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
2of 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
15k10k15k20k7 Oct10 Oct14 Oct17 Oct21 Oct24 Oct

Top 53% 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.3 daysbetween real wipes
on rhythm
20%of its recent wipes
wipe-day peak
2players, last three wipes

The first 48 hours of its last wipes

Fri 16 OctThu 15 OctWed 14 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 16 Oct, 15:17 UTC12d ago M0.0rising 2 – running 1
Thu 15 Oct, 07:37 UTC13d ago M0.0rising 2 – 1.3 days 1
Wed 14 Oct, 13:44 UTC14d ago M0.3rising 2 – 0.7 days 0
Tue 13 Oct, 22:57 UTC14d ago M0.3rising 2 – 0.6 days 0
Mon 12 Oct, 09:23 UTC16d ago M0.3rising 2 – 1.6 days 0
Wed 7 Oct, 19:12 UTC21d ago M0.0rising 1 – 4.6 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 · 554 on average
410/ 500
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
274/ 300
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 295 on average
40/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 294 on average
35/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 273 on average
76/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 252 on average
92/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on 213 Test?

The map on 213 Test is procedural, produced by the game.

Which settings and rules apply on 213 Test?

You will find no gather rate in the name of 213 Test. It gives no group limit in its listing. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. Anti-cheat is off: VAC, from Valve.

Live population

How many players are recorded on 213 Test right now?

A reading taken now finds 213 Test offline; the most recent activity was 11 days 13 hours ago.

How does 213 Test rank against other Rust servers?

On player hours for the past week, 213 Test sits at #11,484, which puts it inside the top 53% of every ranked server.

Server facts

How reliably does 213 Test stay online?

No contact with 213 Test right now, and the last recorded contact was 11 days 13 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 7 October 2026 is when Rust Server Trends first recorded it.

Where in the world is 213 Test hosted?

Its region code is ger, and 213 Test publishes no region. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 195.93.149.246:28015 is the address it uses.

What build of Rust does 213 Test use?

On Windows, 213 Test runs Rust network protocol 2556 and build 104071. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on 213 Test?

The recent wipes averaged a busiest count of 2 players. 2 hours after the latest wipe, the crowd peaked.

How often does 213 Test wipe, and on which days?

No next wipe can be predicted for 213 Test, which wipes 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. It has run its current world for 12 days 7 hours.

Server tags

What do the server tags on 213 Test mean?

These are the tags 213 Test publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; v2556 (Protocol): Game protocol 2556: to join, your game must match this version; cs104071 (Build): Game build: 104071; ptrak (Networking): Network layer: RakNet, the standard for Rust; $rger (Region code): You'll see it listed with the region code ger. 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 213 Test appear?

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

Join the server

How do you connect to 213 Test?

You can connect by pressing F1 in Rust and typing client.connect 195.93.149.246: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 mp10,ptrak,$rger,v2556,gmrust,cs104071

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
v2556
Protocol Game protocol 2556: to join, your game must match this version.
cs104071
Build Game build: 104071.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$rger
Region code You'll see it listed with the region code ger.

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.