Test
Offline 104.28.201.98:28015 checked 21d 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 71% 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- 616/700
- 41/250
- 76/250
- 316/400
- 140/200
- 138/225
Quick answers
from the figures on this pageWipe schedule
When does Test wipe?
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. 21 days 3 hours ago the current world was made.
Tag meanings
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; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is 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?
These Rust Metrics lists carry 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.
Population
Where does Test sit in the rankings?
Ranking for Test: #15,986 on seven-day player hours, top 71% of all ranked servers.
What player count does Test carry?
Status for Test: offline. Last seen 21 days 2 hours ago.
Operator and location
Where does Test sit?
No region comes from Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 104.28.201.98:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 166652, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is Test up, and how often does it stay up?
Check: connection. Test is offline at this moment. Last contact was 21 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 6 October 2026.
Rules and settings
What settings and rules apply on Test?
No gather rate appears in the name: Test. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
What map is Test on?
The game generates a procedural map for Test.
How to join
How do you connect to Test?
Check: join. Open Rust, press F1, then enter client.connect 104.28.201.98:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.