Test Server
Offline 172.59.64.188:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
10% 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- 412/525
- 25/250
- 44/250
- 192/275
- 72/200
- 81/150
Quick answers
from the figures on this pageWipe timing
What wipe timing does Test Server follow?
The rhythm of Test Server's wipes cannot be told yet: too few 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. The world it runs now was made 44 days 10 hours ago.
Tags
How should you read the tags on Test Server?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from Test Server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Test Server appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Test Server: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
How full does Test Server get?
Test Server is not responding; status offline, last seen 44 days 10 hours ago.
Operator and location
Which location does Test Server run from?
Reading: location. Test Server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 172.59.64.188:28015.
What Rust version is Test Server on?
Version check: Rust network protocol 2633 and build 163794 on Windows, run by Test Server. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Test Server, and is it online?
Reading: offline. Test Server last answered 44 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Settings and map
What rules does Test Server enforce, and what are its settings?
Check: gather rate. The name Test Server does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is Test Server on?
Procedural map on Test Server, made by the game's generator.
Connection
What do you do to join Test Server?
Check: join. Open Rust, press F1, then enter client.connect 172.59.64.188:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.