Test
Offline 159.195.112.128:28015 checked 39d 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.
Settings and map
On Test, which rules and settings apply?
You will find no gather rate in the name of Test. 8 players per group is the default limit. The server runs survival, gather, build and raid: the standard game. Combat and raiding between players are possible. Filed under Community in the server browser, it is a community server. VAC, Valve's anti-cheat, is enabled.
What is the map on Test?
Test runs a procedural map, which the game generates.
Tags
Which lists and filters on Rust Server Index is Test filed under?
These lists on Rust Server Index take Test: 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?
Filed under these tags, as published by Test and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp2 (Max players): The queue ceiling sits at 2; ts8 (Group limit): Game default applies: teams of up to 8; v2633 (Protocol): Joining needs you on game protocol 2633; cs163493 (Build): It runs build 163493; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region code has been set. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipe schedule
Which wipe timetable does Test follow?
Its rhythm is not yet clear, since the record holds too few of Test's wipes. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 55 days 15 hours is when its current world was made.
Players and ranking
Where does Test sit in the rankings?
Filed under rankings: #13,268 for Test on seven-day player hours, top – overall.
How many players are on Test at the moment?
The last check found Test offline, last seen 39 days 12 hours ago.
Server details
What version does Test use?
Rust network protocol 2633 and build 163493, on Windows, is what Test runs. To join you need the same protocol; Steam handles the update.
Is Test reachable, and does it stay up?
The server is down at this moment; the last sighting of Test was 39 days 12 hours ago. Uptime for the last 7 full days came to 0%, 0 hours out of 168. It was first recorded by Rust Server Index on 19 September 2026.
Where in the world is Test hosted?
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. You will reach it at 159.195.112.128:28015.
Connecting
What steps lead onto Test?
Enter client.connect 159.195.112.128:28015 in the console, opened with F1. Or join on this page with Launch Rust, 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.