Test
Offline 92.124.161.7:28015 checked 34d 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- 440/525
- 25/250
- 45/250
- 201/275
- 76/200
- 88/150
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Test follow?
Its rhythm cannot be told from the wipes of Test 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 34 days 9 hours ago.
Lists and filters
Which tags does Test carry, and what do they mean?
Tags published by Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
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.
Population
Where does Test sit in the rankings?
Player hours over seven days put Test at #15,460, in the top 71% of all ranked servers.
What player count does Test carry?
Reading for Test: offline at this moment; last seen 34 days 8 hours ago.
Operator and location
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. Connect using 92.124.161.7:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Test, and is it online?
Reading: offline. Test last answered 34 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 23 September 2026.
Map and rules
What settings and rules apply on Test?
No gather rate appears in the name: Test. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Test?
The game generates a procedural map for Test.
Join
How do you connect to Test?
Press F1 in Rust and enter client.connect 92.124.161.7:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.