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
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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.
Quick answers
From the figures on this page.
Map and rules
What settings and rules does Test run?
You will find no gather rate in the name of Test. 8 players per group is the default limit. Filed under survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. The server browser lists it under Community; it is a community server. VAC, Valve's anti-cheat, is enabled.
Tags and filters
Where does Test appear among the Rust Server Index lists and filters?
Filed under these Rust Server Index lists is Test: Community Rust servers, indexed. Filed under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What is meant by the tags on Test?
These are the tags Test publishes; the game's server browser reads this list: gmrust (Game mode): Rust survival, as standard; mp2 (Max players): The queue ceiling sits at 2; ts8 (Group limit): The team limit is 8, as in the standard game; v2633 (Protocol): The protocol is 2633; older or newer clients cannot join; cs163493 (Build): Build on file: 163493; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipe schedule
When does Test wipe?
Test's rhythm cannot be told yet: too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The world it runs now was made 48 days 16 hours.
Players and ranking
How is Test ranked compared with the rest?
On player hours over seven days, Test takes #15,505, within the top – of ranked servers.
Is Test quiet or crowded?
At present Test is offline; its last sighting was 43 days 13 hours ago.
Server details
What version does Test use?
Rust network protocol 2633 and build 163493 on Windows is what you will find on Test. The protocol must match before you can join, and Steam takes care of updating it.
What is the uptime and current status of Test?
The server is down at this moment; the last sighting of Test was 43 days 13 hours ago. Of the last 7 full days, 0 of 168 hours were up, 0% of the time. The earliest sighting at Rust Server Index is 16 September 2026.
Which region is Test in?
Test gives no region at all. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 109.163.220.218:28015.
Connecting
What steps lead onto Test?
Two ways in. Type client.connect 109.163.220.218:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
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.