Test Server
Offline 5.186.52.179:28015 checked 27d 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 bestTop 63% 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- 166/250
- 119/200
- 19/250
- 15/250
- 18/100
- 25/200
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test Server follow?
The rhythm of Test Server's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 27 days 11 hours ago.
Tag meanings
How should you read the tags on Test Server?
Tags published by Test Server, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166493 (Build): Game build reading: 166493; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. 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. 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 Server hold among Rust servers?
Player hours over seven days put Test Server at #14,848, in the top 63% of all ranked servers.
What player count does Test Server carry?
Test Server is not responding; status offline, last seen 27 days 10 hours ago.
Server
Which location does Test Server run from?
Reading: location. Test Server gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 5.186.52.179:28015.
What Rust version is Test Server on?
Version check: Rust network protocol 2634 and build 166493 on Windows, run by Test Server. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on Test Server, and is it online?
Test Server reports offline. The last reading came 27 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 1 October 2026.
Settings and map
How is Test Server configured, and what rules are in force?
Check: gather rate. The name Test Server does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.
How to join
What do you do to join Test Server?
To join: start Rust, press F1 and type client.connect 5.186.52.179:28015. Or press Launch Rust here and Steam opens the game and connects you.