Test
Offline 159.195.112.128:28015 checked 39d 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 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- 441/475
- 348/375
- 42/250
- 33/250
- 46/100
- 147/200
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
Its rhythm cannot be told from the wipes of Test on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 55 days 13 hours ago.
Tag meanings
How should you read the tags on Test?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163493 (Build): Build 163493; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from Test. 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?
Rust Metrics lists featuring Test: 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.
Population
Where does Test sit in the rankings?
Ranking for Test: #13,268 on seven-day player hours, top – of all ranked servers.
What player count does Test carry?
Reading for Test: offline at this moment; last seen 39 days 10 hours ago.
Server
Where does Test sit?
Reading: location. Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 159.195.112.128: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.
What is the uptime on Test, and is it online?
Reading: offline. Test last answered 39 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 19 September 2026, recorded by Rust Metrics.
Settings and map
How is Test configured, and what rules are in force?
Check: gather rate. The name Test does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. 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?
Check: join. Open Rust, press F1, then enter client.connect 159.195.112.128:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.