Test
Offline 84.32.100.102:28015 checked 23d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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 61% 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- 261/275
- 20/250
- 17/250
- 162/200
- 67/200
- 39/100
Quick answers
from the figures on this pageWipe timing
What wipe timing does Test follow?
To tell the rhythm of Test, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 31 days 15 hours ago the current world was made.
Lists and filters
How should you read the tags on Test?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Test appear in Rust Metrics lists and filters?
On Rust Metrics, Test 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.
Player count
What position does Test hold among Rust servers?
Player hours over seven days put Test at #13,783, in the top 61% of all ranked servers.
What is the population on Test?
Test is not responding; status offline, last seen 23 days 8 hours ago.
Operator and location
What location is Test hosted in?
No region tag on Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 84.32.100.102:28015.
What Rust version is Test on?
Rust network protocol 2633 and build 165217 on Windows is the build Test runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on Test, and is it online?
Test reports offline. The last reading came 23 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 4 October 2026, recorded by Rust Metrics.
Rules and settings
How is Test configured, and what rules are in force?
Check: gather rate. The name Test does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC off, Valve's system.
Which map is live on Test?
The game generates a procedural map for Test.
How to join
What do you do to join Test?
Press F1 in Rust and enter client.connect 84.32.100.102:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.