TEST
Offline 95.167.183.164:28015 checked 37d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| 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- 487/525
- 28/250
- 49/250
- 238/275
- 91/200
- 98/150
Quick answers
from the figures on this pageWipe schedule
What wipe timing does TEST follow?
To tell the rhythm of TEST, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 37 days 12 hours ago the current world was made.
Tags
Which tags does TEST carry, and what do they mean?
Tags published by TEST, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does TEST appear in Rust Metrics lists and filters?
On Rust Metrics, TEST sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #15,515, in the top – of all ranked servers.
What player count does TEST carry?
Reading for TEST: offline at this moment; last seen 37 days 8 hours ago.
Server details
What location is TEST hosted in?
No region comes from TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 95.167.183.164:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 164530, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is TEST up, and how often does it stay up?
Check: connection. TEST is offline at this moment. Last contact was 37 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 20 September 2026, recorded by Rust Metrics.
Settings and map
How is TEST configured, and what rules are in force?
Reading the name gives no gather rate for TEST. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.
What map is TEST on?
The game generates a procedural map for TEST.
Connection
How can you get onto TEST?
To join: start Rust, press F1 and type client.connect 95.167.183.164:28015. Or press Launch Rust here and Steam opens the game and connects you.