Rust Server Analytics 46,298 players11,701 servers
All servers
Drill-through Server detail

213 Test

Offline 195.93.149.246:28015 checked 11d ago

Drill-through
FilterServeris 213 Test
Attributes
Last refreshed
Players now 2/ 10
7-day average 0 peak –
Rank #11,484 top 53%
Last wipe 12d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 20% full

Players

average and peak, with its wipes marked
No hourly history yet.

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
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.

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.

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 gap1.3 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak2players, 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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 15:17 UTC12d ago 2 – running 1
Thu 15 Oct, 07:37 UTC13d ago 2 – 1.3 days 1
Wed 14 Oct, 13:44 UTC14d ago 2 – 0.7 days 0
Tue 13 Oct, 22:57 UTC15d ago 2 – 0.6 days 0
Mon 12 Oct, 09:23 UTC16d ago 2 – 1.6 days 0
Wed 7 Oct, 19:12 UTC21d ago 1 – 4.6 days 0

Peak: the most players in the first 48 hours. 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 560 on average 238 / 275
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 159 / 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 292 on average 27 / 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 291 on average 16 / 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average 32 / 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 251 on average 45 / 200

Quick answers

from the figures on this page

Wipe cycle

When does 213 Test wipe?

The next wipe on 213 Test cannot be predicted, because it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. 12 days 9 hours ago the current world was made.

On 213 Test, what happens on wipe day?

The average busiest count over recent wipes is 2 players. Peak population for the latest wipe came 2 hours after it began.

Server details

Which location hosts 213 Test?

The region code of 213 Test is ger, but no region is published. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 195.93.149.246:28015.

What Rust build does 213 Test run?

On Windows, 213 Test runs Rust network protocol 2556 and build 104071. Your game must match the protocol to join, and Steam applies that update.

What uptime does 213 Test show, and is it up?

Last seen 11 days 15 hours ago, 213 Test now reports offline. 0% uptime over the last 7 full days, equal to 0 of 168 hours. It entered Rust Server Analytics records on 7 October 2026.

Tags

How should the tags on 213 Test be read?

gmrust (Game mode): Rust survival, standard ruleset; mp10 (Max players): Player slots: 10; v2556 (Protocol): Joining needs your game on protocol 2556; cs104071 (Build): Game build: 104071; ptrak (Networking): It uses RakNet, the standard network layer for the game; $rger (Region code): Its region code is ger are the tags 213 Test publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does 213 Test appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include 213 Test: Community Rust servers, live. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks.

Population

Against other Rust servers, how does 213 Test compare?

Player hours for the last seven days place 213 Test at #11,484, in the top 53% of the ranked field.

At what level does 213 Test run its population?

213 Test is offline at this refresh; the last contact was 11 days 15 hours ago.

Map and rules

What settings and rules does 213 Test use?

No gather rate is given in the name of 213 Test. Group limits are not published. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser, it appears under Community. The server runs with VAC, Valve's anti-cheat, disabled.

What is the map for 213 Test?

A procedural map, generated by the game, runs on 213 Test.

How to join

What is the way onto 213 Test?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 195.93.149.246:28015.

Server tags

what each one means

Published as mp10,ptrak,$rger,v2556,gmrust,cs104071

Game

gmrust
Game mode Rust survival, standard ruleset.
mp10
Max players Player slots: 10.
v2556
Protocol Joining needs your game on protocol 2556.
cs104071
Build Game build: 104071.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$rger
Region code Its region code is 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.