Test Server
Offline 85.238.79.200:28088 checked 17d 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 72% 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- 611/575
- 395/400
- 39/250
- 48/250
- 154/200
- 90/100
Quick answers
from the figures on this pageReset cycle
How often does Test Server wipe, and when?
Its rhythm cannot be told from the wipes of Test Server on record: there are too few. 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 52 days 18 hours ago.
Tag meanings
Which tags does Test Server carry, and what do they mean?
Tags published by Test Server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163207 (Build): Game build reading: 163207; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Test Server appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Test Server: 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.
Occupancy
Where does Test Server sit in the rankings?
Player hours over seven days put Test Server at #15,883, in the top 72% of all ranked servers.
What player count does Test Server carry?
Reading for Test Server: offline at this moment; last seen 17 days 17 hours ago.
Server
Where does Test Server sit?
Reading: location. Test Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 85.238.79.200:28088.
What Rust version is Test Server on?
Reading: Test Server, Rust network protocol 2633 and build 163207, Linux. 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 17 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 3 October 2026, recorded by Rust Metrics.
Map and rules
How is Test Server configured, and what rules are in force?
Reading the name gives no gather rate for Test Server. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
Join
How do you connect to Test Server?
To join: start Rust, press F1 and type client.connect 85.238.79.200:28088. Or press Launch Rust here and Steam opens the game and connects you.