TestServer
Offline 85.112.61.39:28015 checked 25d 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- 156/250
- 290/325
- 35/250
- 13/250
- 146/200
- 64/100
Quick answers
from the figures on this pageReset cycle
What wipe timing does TestServer follow?
Its rhythm cannot be told from the wipes of TestServer 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 in play was created 25 days 22 hours ago.
Tags
Which tags does TestServer carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166586 (Build): Build 166586; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from TestServer. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show TestServer?
On Rust Metrics, TestServer 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
What position does TestServer hold among Rust servers?
Ranking for TestServer: #15,895 on seven-day player hours, top 70% of all ranked servers.
What is the population on TestServer?
Reading for TestServer: offline at this moment; last seen 25 days 20 hours ago.
Server
Where does TestServer sit?
Reading: location. TestServer gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 85.112.61.39:28015.
What Rust version is TestServer on?
Version check: Rust network protocol 2634 and build 166586 on Windows, run by TestServer. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on TestServer, and is it online?
Reading: offline. TestServer last answered 25 days 20 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 2 October 2026.
Map and rules
How is TestServer configured, and what rules are in force?
No gather rate appears in the name: TestServer. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Join
How can you get onto TestServer?
Check: join. Open Rust, press F1, then enter client.connect 85.112.61.39:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.