TEST
Offline 188.47.5.97:28015 checked 31d ago
Server instruments
no direct query in 48 hoursPlayers now
10% 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 67% 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- 322/375
- 210/250
- 34/250
- 28/250
- 54/100
- 73/200
Quick answers
from the figures on this pageReset cycle
How often does TEST wipe, and when?
To tell the rhythm of TEST, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 31 days 13 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): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does TEST appear in Rust Metrics lists and filters?
On Rust Metrics, TEST sits in these lists: 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.
Population
Where does TEST sit in the rankings?
Player hours over seven days put TEST at #15,922, in the top 67% of all ranked servers.
How full does TEST get?
TEST is not responding; status offline, last seen 31 days 11 hours ago.
Server details
Which location does TEST run from?
Reading: location. TEST gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 188.47.5.97:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 165217 on Windows is the build TEST runs. To get in, your game needs the same protocol; Steam applies the update.
How reliable is TEST, and is it online now?
Reading: offline. TEST last answered 31 days 11 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 27 September 2026.
Map and rules
What settings and rules apply on TEST?
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; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TEST?
The game generates a procedural map for TEST.
Join
What do you do to join TEST?
Press F1 in Rust and enter client.connect 188.47.5.97:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.