TEST
Offline 5.44.169.105:28015 checked 40d 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.
Rules and settings
On TEST, which rules and settings apply?
No gather rate appears in the name TEST. The default group limit of 8 players applies. 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. VAC, Valve's anti-cheat, is enabled.
Which map is in use on TEST?
TEST runs a procedural map, which the game generates.
Tags and filters
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?
These are the tags TEST publishes; the game's server browser reads this list: gmrust (Game mode): Rust survival, as standard; mp5 (Max players): Player cap: 5; ts8 (Group limit): Game default applies: teams of up to 8; v2633 (Protocol): Joining needs you on game protocol 2633; cs164530 (Build): The game build here is 164530; ptrak (Networking): RakNet is the network layer, as standard for Rust; $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
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 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 40 days 23 hours is when its current world was made.
Player counts
How is TEST ranked compared with the rest?
On player hours over seven days, TEST takes #15,383, within the top – of ranked servers.
How many players are on TEST at the moment?
Filed under offline: TEST, last seen 40 days 11 hours ago.
Server details
What version does TEST use?
Rust network protocol 2633 and build 164530 on Windows is what you will find on TEST. The protocol must match before you can join, and Steam takes care of updating it.
Is TEST reachable, and does it stay up?
The server is down at this moment; the last sighting of TEST was 40 days 11 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 18 September 2026.
Where in the world is TEST hosted?
No region is published by TEST. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 5.44.169.105:28015.
Connecting
What steps lead onto TEST?
If you would rather use the console, press F1 in Rust and enter client.connect 5.44.169.105: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 mp5,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp5
ts8
v2633
cs164530
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.