TEST
Offline 85.175.199.2:28015 checked 3d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avg7-day peakServer 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 55% 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- 784/825
- 50/250
- 125/250
- 463/500
- 268/300
- 196/300
Quick answers
from the figures on this pageWipe schedule
When does TEST wipe?
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 3 days 22 hours ago.
Lists and filters
How should you read the tags on TEST?
These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show TEST?
Rust Metrics lists featuring TEST: 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; Last wipe: In the last week.
Player count
Where does TEST sit in the rankings?
Ranking for TEST: #12,118 on seven-day player hours, top 55% of all ranked servers.
What player count does TEST carry?
TEST is not responding; status offline, last seen 3 days 21 hours ago. Check: players over seven days. Average 1, peak 1.
Server
Where does TEST sit?
No region tag on TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 85.175.199.2:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is TEST, and is it online now?
Check: connection. TEST is offline at this moment. Last contact was 3 days 21 hours ago. Uptime for the last 3 full days: 0 of 72 hours, or 0%. Reading: first seen 23 October 2026, recorded by Rust Metrics.
Settings and map
What settings and rules apply on TEST?
No gather rate appears in the name: TEST. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is TEST on?
Check: map. Procedural, generated by the game, on TEST.
Join
What do you do to join TEST?
Press F1 in Rust and enter client.connect 85.175.199.2:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.