Test
Offline 89.208.22.43:28015 checked 45d 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
On Test, which rules and settings apply?
The name of Test does not state a gather rate. 8 players per group is the default limit. Filed under survival, gather, build and raid: the standard game. Combat and raiding between players are possible. The server browser lists it under Community; it is a community server. VAC, Valve's anti-cheat, is enabled.
Which map is in use on Test?
Generated by the game, the map is procedural on Test.
Lists and filters
Where does Test appear among the Rust Server Index lists and filters?
The Rust Server Index lists that include Test are Community Rust servers, indexed. These filters on the server list bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags listed for Test?
The server's own tags are listed here, and the game's server browser reads them: Test gives gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams cap at 8, the default setting; v2633 (Protocol): Your client must run protocol 2633 to connect; cs163794 (Build): It runs build 163794; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region code has been set. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe dates
When does Test wipe?
Its rhythm is not yet clear, since the record holds too few of Test's wipes. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 45 days 6 hours.
Player counts
What does the player count on Test look like?
At present Test is offline; its last sighting was 45 days 5 hours ago.
Server details
Which Rust build is Test running?
Rust network protocol 2633 and build 163794, on Windows, is what Test runs. The protocol must match before you can join, and Steam takes care of updating it.
What is the uptime and current status of Test?
As of now Test is offline, with its last appearance 45 days 5 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. The earliest sighting at Rust Server Index is 13 September 2026.
What is the location of Test?
There is no region on record for Test; it publishes none. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 89.208.22.43:28015.
Connecting
How can you connect to Test?
If you would rather use the console, press F1 in Rust and enter client.connect 89.208.22.43:28015. You can also choose Launch Rust and join here; that opens Rust through 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.