TEST
Offline 95.170.182.48: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?
The name of TEST does not state a gather rate. The default group limit of 8 players applies. Filed under survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. It is listed under Community in the server browser and is a community server. VAC is on: Valve's anti-cheat is enabled.
Which map is in use on TEST?
TEST runs a procedural map, which the game generates.
Tags
On Rust Server Index, which lists and filters carry TEST?
Filed under these Rust Server Index lists is TEST: Community Rust servers, indexed. Filed under these filters on the server list: 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): Survival on standard Rust rules; mp10 (Max players): The queue ceiling sits at 10; ts8 (Group limit): The team limit is 8, as in the standard game; v2633 (Protocol): Joining needs you on game protocol 2633; cs164530 (Build): It runs build 164530; 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.
Wipes and resets
When does TEST wipe?
The record holds too few of TEST's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 40 days 11 hours is when its current world was made.
Players and ranking
How is TEST ranked compared with the rest?
On player hours over seven days, TEST takes #13,285, within the top – of ranked servers.
How many players are on TEST at the moment?
At present TEST is offline; its last sighting was 40 days 10 hours ago.
Operator and status
What Rust version is TEST on?
Rust network protocol 2633 and build 164530, 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 40 days 10 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 17 September 2026.
Which region is TEST in?
TEST gives no region at all. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 95.170.182.48:28015.
Connecting
How can you connect to TEST?
Enter client.connect 95.170.182.48: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,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp10
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.