Test
Offline 152.53.158.88:28015 checked 36d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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 bestTop 64% 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
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- 680/725
- 452/500
- 39/250
- 53/250
- 153/175
- 209/250
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
To tell the rhythm of Test, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 54 days 17 hours ago the current world was made.
Tag meanings
How should you read the tags on Test?
These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163493 (Build): The server runs game build 163493; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Test appear in Rust Metrics lists and filters?
On Rust Metrics, Test sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does Test sit in the rankings?
Ranking for Test: #14,692 on seven-day player hours, top 64% of all ranked servers.
What is the population on Test?
Test is not responding; status offline, last seen 36 days 16 hours ago.
Server
Where does Test sit?
No region tag on Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 152.53.158.88:28015.
What Rust version is Test on?
Rust network protocol 2633 and build 163493 on Windows is the build Test runs. 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 36 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 21 September 2026.
Rules and settings
What rules does Test enforce, and what are its settings?
Check: gather rate. The name Test does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is Test on?
The game generates a procedural map for Test.
Connection
How can you get onto Test?
Press F1 in Rust and enter client.connect 152.53.158.88:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.