test
Offline 95.160.182.126:28015 checked 42d 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. The group limit is 8 players, the game's default. The server runs 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 disabled.
Which map is in use on test?
A procedural map, generated by the game, is what test runs.
Lists and filters
Which lists and filters on Rust Server Index is test filed under?
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?
These are the tags test publishes; the game's server browser reads this list: gmrust (Game mode): Rust survival, as standard; mp500 (Max players): 500 slots are available; ts8 (Group limit): Teams cap at 8, the default setting; v2633 (Protocol): Joining needs you on game protocol 2633; cs163794 (Build): Build on file: 163794; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): The region code field is left empty. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipe dates
Which wipe timetable does test follow?
test's rhythm cannot be told yet: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The world it runs now was made 55 days 17 hours.
Player counts
How is test ranked compared with the rest?
Filed under rankings: #14,437 for test on seven-day player hours, top – overall.
How many players are on test at the moment?
Filed under offline: test, last seen 42 days 23 hours ago.
Operator and status
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 42 days 23 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 15 September 2026.
What is the location of test?
There is no region on record for test; it publishes none. Rust Server Index takes the server's word for its location and does not look up the machine's position. You will reach it at 95.160.182.126:28015.
Connecting
What steps lead onto test?
Two ways in. Type client.connect 95.160.182.126: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 mp500,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp500
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.