Test
Offline 183.192.134.24:28015 checked 9d ago
Server instruments
no direct query in 48 hoursPlayers now
12% 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 63% 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 next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 9 days 4 hours ago.
Tags
How should you read the tags on Test?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp8 (Max players): Slots: 8; 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): No region code is set 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?
Rust Metrics lists featuring Test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Occupancy
Where does Test sit in the rankings?
Player hours over seven days put Test at #13,780, in the top 63% of all ranked servers.
What player count does Test carry?
Test is not responding; status offline, last seen 9 days 3 hours ago.
Server details
Where does Test sit?
No region comes from Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 183.192.134.24:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 167781, Linux. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Test, and is it online now?
Test reports offline. The last reading came 9 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 19 October 2026.
Map and rules
What settings and rules apply on Test?
Check: gather rate. The name Test does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. 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?
Check: map. Procedural, generated by the game, on Test.
How to join
What do you do to join Test?
To join: start Rust, press F1 and type client.connect 183.192.134.24:28015. Or press Launch Rust here and Steam opens the game and connects you.