Test
Offline 95.98.79.89:28015 checked 14d 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- 636/675
- 485/525
- 59/250
- 36/250
- 138/200
- 255/300
Quick answers
from the figures on this pageReset cycle
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 in play was created 14 days 4 hours ago.
Tags
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; mp500 (Max players): Slots: 500; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Test?
Rust Metrics lists featuring Test: 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
Where does Test sit in the rankings?
Player hours over seven days put Test at #15,247, in the top 70% of all ranked servers.
What player count does Test carry?
Test is not responding; status offline, last seen 14 days 4 hours ago.
Server
Where does Test sit?
Reading: location. Test 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 95.98.79.89:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.
How reliable is Test, and is it online now?
Test reports offline. The last reading came 14 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 14 October 2026.
Rules and settings
What rules does Test enforce, and what are its settings?
Reading the name gives no gather rate for Test. 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. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Test?
Procedural map on Test, made by the game's generator.
Connection
How do you connect to Test?
Press F1 in Rust and enter client.connect 95.98.79.89:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.