TST15049
TEST
Offline 213.109.141.52:28015 checked 44d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
-
01COMPlayers 187/250
-
02COMPlayers 120/200
-
03COMPlayers 19/250
-
04COMPlayers 11/250
-
05COMPlayers 20/100
-
06COMPlayers 28/225
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry TEST?
These Rust Tracker lists carry TEST: Community servers, no tags. These filters surface it on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on TEST?
Listed for the server browser to read, TEST publishes these tags: gmrust (Game mode): Rust survival, standard mode; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams cap at 8; this is the game default; v2633 (Protocol): Join only if your game is on protocol 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Times
On what schedule does TEST wipe?
TEST's rhythm cannot be told yet: too few wipes on record. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. This world has been running 44 days 14 hours.
Server Details
How reliable is TEST, and is it online now?
Offline: TEST confirmed offline, last seen 44 days 14 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. The first sighting by Rust Tracker was 14 September 2026.
Which Rust build is TEST running?
Rust network protocol 2633 and build 163794 on Windows is what TEST runs. The same protocol is required to join, and Steam updates it for you.
Which location is TEST in?
Region: none published by TEST. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 213.109.141.52:28015.
Player Count
Is TEST busy?
Offline: TEST, last seen 44 days 14 hours ago.
Where does TEST sit in the server rankings?
On player hours over seven days, TEST ranks #15,049, inside the top – of all ranked servers.
Settings
Which settings and rules are confirmed on TEST?
The name of TEST carries no gather rate. The game's default applies: groups can have up to 8 players. It runs survival, gather, build and raid: the standard game. Raiding and PvP are permitted between players. A community server: the server browser lists it under Community. VAC is on, Valve's anti-cheat.
Which map is confirmed for TEST?
A procedural map runs on TEST, generated by the game.
Connect
How do you get onto TEST?
Open the console in Rust with F1 after starting the game, then type client.connect 213.109.141.52:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp10
ts8
v2633
cs163794
ptrak
$r?
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.