RUST METRICSFlight deck · live data
Data live Servers11,700 Players38,808 Populated2,943 Fresh wipes 3 h91 Scan5 min
‹ All servers195.93.149.246:28015
Offline Full Queue Fresh wipe Wipe due No query

213 Test

Offline 195.93.149.246:28015 checked 11d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 2 /10

Players now

20% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#11,484top 53%
Last wipe12d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

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.

LOG

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on 213 Test?

An average of 2 players came at the busiest on its recent wipes. 2 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does 213 Test follow?

There is no next wipe to predict: 213 Test wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 12 days 10 hours ago the current world was made.

Tags

Which tags does 213 Test carry, and what do they mean?

Tags published by 213 Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; v2556 (Protocol): Match the game version: protocol 2556 is required; cs104071 (Build): Game build reading: 104071; ptrak (Networking): Network layer: RakNet, the standard for the game; $rger (Region code): ger is the region code on record. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does 213 Test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry 213 Test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks.

Occupancy

Where does 213 Test sit in the rankings?

Ranking for 213 Test: #11,484 on seven-day player hours, top 53% of all ranked servers.

How full does 213 Test get?

213 Test is not responding; status offline, last seen 11 days 17 hours ago.

Server

What location is 213 Test hosted in?

Reading: location. 213 Test gives no region, with region code ger. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 195.93.149.246:28015.

What Rust version is 213 Test on?

Rust network protocol 2556 and build 104071 on Windows is the build 213 Test runs. Matching protocol is required to join. Let Steam update your game.

Is 213 Test up, and how often does it stay up?

213 Test reports offline. The last reading came 11 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 7 October 2026.

Map and rules

What settings and rules apply on 213 Test?

No gather rate appears in the name: 213 Test. No group limit is published. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC off, Valve's system.

What map is 213 Test on?

Check: map. Procedural, generated by the game, on 213 Test.

Connection

What do you do to join 213 Test?

Press F1 in Rust and enter client.connect 195.93.149.246:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
v2556
Protocol Match the game version: protocol 2556 is required.
cs104071
Build Game build reading: 104071.
ptrak
Networking Network layer: RakNet, the standard for the game.
$rger
Region code ger is the region code on record.

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.