testserv
Offline 176.60.71.114:28015 checked 8d 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 bestTop 70% 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- 677/725
- 438/475
- 38/250
- 52/250
- 218/250
- 144/175
Quick answers
from the figures on this pageWipe timing
When does testserv wipe?
The rhythm of testserv'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 in play was created 15 days 3 hours ago.
Tag meanings
How should you read the tags on testserv?
Tags published by testserv, read by the game's server browser: 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; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Build 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does testserv appear in Rust Metrics lists and filters?
Rust Metrics lists featuring testserv: 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 testserv sit in the rankings?
Ranking for testserv: #15,346 on seven-day player hours, top 70% of all ranked servers.
How full does testserv get?
Status for testserv: offline. Last seen 8 days 6 hours ago.
Server
Where does testserv sit?
No region tag on testserv. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 176.60.71.114:28015.
What Rust version is testserv on?
Version check: Rust network protocol 2634 and build 167584 on Windows, run by testserv. Matching protocol is required to join. Let Steam update your game.
What is the uptime on testserv, and is it online?
testserv reports offline. The last reading came 8 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 20 October 2026.
Rules and settings
What rules does testserv enforce, and what are its settings?
Check: gather rate. The name testserv does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.
Which map is live on testserv?
Procedural map on testserv, made by the game's generator.
Connection
What do you do to join testserv?
To join: start Rust, press F1 and type client.connect 176.60.71.114:28015. Or press Launch Rust here and Steam opens the game and connects you.