test
Offline 99.6.242.173:28015 checked 12d 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
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
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. The server does not publish a group limit. The server runs survival, gather, build and raid: the standard game. PvP and raiding are allowed. It is listed under Community in the server browser and is a community server. The server has VAC, Valve's anti-cheat, turned on.
Which map is in use on test?
test runs a procedural map, which the game generates.
Tags
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. Filed under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks.
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; mp10 (Max players): The queue ceiling sits at 10; v2564 (Protocol): The protocol is 2564; older or newer clients cannot join; cs105864 (Build): It runs build 105864; ptrak (Networking): The standard RakNet layer carries the connection; $rus1 (Region code): us1 is the region code recorded here. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipe schedule
How often is test wiped, and on what schedule?
test's rhythm cannot be told yet: too few of its wipes are on record. On Thursday 3 December at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The world it runs now was made 12 days 22 hours.
Players and ranking
Where does test sit in the rankings?
Filed under rankings: #15,589 for test on seven-day player hours, top 71% overall.
What does the player count on test look like?
At present test is offline; its last sighting was 12 days 20 hours ago.
Server facts
What version does test use?
Rust network protocol 2564 and build 105864 on Windows is what you will find on test. Steam keeps your game updated, but the protocol must match for you to join.
How reliable is test, and is it online now?
Last seen 12 days 20 hours ago, test is offline right now. Uptime for the last 7 full days came to 0%, 0 hours out of 168. On 6 November 2026 it was first seen by Rust Server Index.
What is the location of test?
There is no region on record for test; the region code is us1. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 99.6.242.173:28015.
Connecting
What steps lead onto test?
Enter client.connect 99.6.242.173: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 mp10,ptrak,$rus1,v2564,gmrust,cs105864
Game
gmrust
mp10
v2564
cs105864
ptrak
$rus1
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.