This server publishes no banner

Exhibit no. 11,484Acc. 2026.11484

213 Test

Rust server · in the archive since 7 October 2026

Offline 195.93.149.246:28015 checked 11d ago

To visit

Launch Rust and join

Players now 2/ 10

20% full

7-day average0peak –

Rank#11,484top 53%

Last wipe12d agoFri 16 Oct, 15:17 UTC · no schedule published

Next wipe–no rhythm it keeps

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

In the archive
7 Oct Last seen 7 Oct19:12 12 Oct09:23 13 Oct22:57 14 Oct13:44 15 Oct07:37 16 Oct15:17

a wipe on recordthe monthly force wipeexpectedlast seen, 17 Oct 2026, 08:50 UTCAll times UTC.

The record of each wipe

Fri 16 Oct 202615:17 UTC12d ago

Peak
2

Crowd
–

Lasted
running

Players before
1
Thu 15 Oct 202607:37 UTC13d ago

Peak
2

Crowd
–

Lasted
1.3 days

Players before
1
Wed 14 Oct 202613:44 UTC14d ago

Peak
2

Crowd
–

Lasted
0.7 days

Players before
0
Tue 13 Oct 202622:57 UTC15d ago

Peak
2

Crowd
–

Lasted
0.6 days

Players before
0
Mon 12 Oct 202609:23 UTC16d ago

Peak
2

Crowd
–

Lasted
1.6 days

Players before
0
Wed 7 Oct 202619:12 UTC21d ago

Peak
1

Crowd
–

Lasted
4.6 days

Players before
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.

The rhythm

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.

1.3 daysusual gapbetween real wipes

20%on rhythmof its recent wipes

2wipe-day peakplayers, last three wipes

The first 48 hours of its last wipes

Fri 16 OctThu 15 OctWed 14 Oct

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

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Folder 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.

Folder 3

Rank

RankRank in region

Top 53% of all ranked servers. Ranked on player hours over the last seven days.

Related exhibits

Similar servers

The same kind of game, then region, group limit, rate and wipes.

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags, lists

What do the server tags on 213 Test mean?

The game's server browser reads these tags published by 213 Test: gmrust (Game mode): This server runs standard Rust survival; mp10 (Max players): Slot count: 10; v2556 (Protocol): To join, your game has to be on protocol 2556; cs104071 (Build): Build number: 104071; ptrak (Networking): RakNet handles the network layer, as standard for the game; $rger (Region code): ger is the server's region code. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.

Which Rust Server History lists and filters include 213 Test?

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

Server record

Which version of Rust does 213 Test run?

Rust network protocol 2556 and build 104071 is the build 213 Test runs, on Windows. The protocol must match to join, and Steam handles that update.

Is 213 Test online, and how reliable is it?

213 Test was last seen 11 days 19 hours ago and is offline right now. Of 168 hours in the last 7 full days, 0 were up: 0% of the time. First seen by Rust Server History on 7 October 2026.

Where is 213 Test located?

You will find no region published by 213 Test, and its region code is ger. Where a server says it is is shown on Rust Server History; where the machine stands is not looked up. You will find it at 195.93.149.246:28015.

Wipe history

What does wipe day look like on 213 Test?

An average peak of 2 players was drawn by its recent wipes. 2 hours into the latest wipe the crowd peaked.

What is the wipe schedule on 213 Test?

There is no next wipe to predict on 213 Test, which wipes at irregular times. Next on Thursday 5 November at 19:00 UTC is the monthly force wipe, when every Rust server wipes. Made 12 days 12 hours ago, the current world is what it runs now.

Population

How does 213 Test rank against other Rust servers?

Player hours over the last seven days put 213 Test at #11,484: a place in the top 53% of all ranked servers.

How busy is 213 Test?

No current count exists for 213 Test; it was last seen 11 days 19 hours ago.

Rules and settings

What are the rules and settings on 213 Test?

You will not find a gather rate in the name of 213 Test. No figure for group size is published. Recorded as survival, with this note: gather, build, raid: the standard game. Fighting and raiding between players are permitted. The Community section of the server browser carries it. The anti-cheat VAC from Valve is disabled.

Which map does 213 Test run?

The game generates the map on 213 Test, which is procedural.

Join record

How do I join 213 Test?

Enter client.connect 195.93.149.246:28015 in the console, opened with F1 in Rust. Launch Rust and join on this page also works: it opens Rust through Steam and connects you.

The label explained

Server tags

What each tag this server publishes means.

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

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.