TST15505
Test
Offline 109.163.220.218:28015 checked 43d 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 316/375
-
02COMPlayers 433/475
-
03COMPlayers 959/1000
-
04COMPlayers 48/100
-
05COMPlayers 0/8
-
06COMPlayers 984/1000
Quick answers
From the figures on this page.
Tags
Which lists and filters on Rust Tracker show Test?
Community servers, no tags — the Rust Tracker lists that include Test. 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): Standard survival mode for Rust; mp2 (Max players): Slots: 2; ts8 (Group limit): Team limit is 8, the game default; v2633 (Protocol): Join only if your game is on protocol 2633; cs163493 (Build): The game build is 163493; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.
Wipe Times
On what schedule does Test wipe?
Too few wipes on record for Test to show its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. This world has been running 48 days 10 hours.
Location and Status
How reliable is Test, and is it online now?
Offline now, Test was last seen 43 days 8 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. First contact for Rust Tracker: 16 September 2026.
Which Rust build is Test running?
Rust network protocol 2633 and build 163493 is the build on Test; the platform is Windows. To join, your game must be on the same protocol; Steam handles the update.
Which location is Test in?
No region is published by Test. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 109.163.220.218:28015.
Player Count
What is the player count on Test?
Offline now for Test, last seen 43 days 8 hours ago.
How does Test compare in the rankings?
Seven-day player hours put Test at #15,505, within the top – of all ranked servers.
Map and Rules
Which settings and rules are confirmed on Test?
The name of Test carries no gather rate. 8 players per group is the game's default, and the cap holds. It runs survival, gather, build and raid: the standard game. Players can raid and fight each other here. Listed under Community in the server browser, it is a community server. VAC is on, Valve's anti-cheat.
How to Join
How do you get onto Test?
To connect: start Rust, press F1, enter client.connect 109.163.220.218:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.
Server tags
What each one means.
Published as mp2,ptrak,$r?,v2633,gmrust,cs163493,ts8
Game
gmrust
mp2
ts8
v2633
cs163493
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.