TEST
Offline 31.144.153.6:28015 checked 18d 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 62% 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- 171/250
- 177/200
- 18/250
- 14/250
- 16/100
- 87/200
Quick answers
from the figures on this pageWipe schedule
When does TEST wipe?
The rhythm of TEST's wipes cannot be told yet: too few 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 19 days 17 hours ago.
Tag meanings
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; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; 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.
Population
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #13,595, in the top 62% of all ranked servers.
What player count does TEST carry?
TEST is not responding; status offline, last seen 18 days 22 hours ago.
Server details
Which location does TEST run from?
No region comes from TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 31.144.153.6:28015.
What Rust version is TEST on?
Rust network protocol 2634 and build 167398 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.
How reliable is TEST, and is it online now?
Check: connection. TEST is offline at this moment. Last contact was 18 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 10 October 2026.
Rules and settings
What rules does TEST enforce, and what are its settings?
Check: gather rate. The name TEST does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
What map is TEST on?
The game generates a procedural map for TEST.
Join
What do you do to join TEST?
Press F1 in Rust and enter client.connect 31.144.153.6:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.