TEST
Offline 31.61.226.232:28015 checked 10d 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 70% 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- 468/575
- 295/400
- 41/250
- 34/250
- 83/150
- 101/200
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. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 10 days 13 hours ago the current world was made.
Lists and filters
Which tags does TEST carry, and what do they mean?
These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is 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?
These Rust Metrics lists carry 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.
Player count
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #15,319, in the top 70% of all ranked servers.
How full does TEST get?
Reading for TEST: offline at this moment; last seen 10 days 12 hours ago.
Server
Which location does TEST run from?
No region tag on TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 31.61.226.232:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by TEST. Matching protocol is required to join. Let Steam update your game.
Is TEST up, and how often does it stay up?
TEST reports offline. The last reading came 10 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 18 October 2026.
Rules and settings
What settings and rules apply on TEST?
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. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is TEST on?
The game generates a procedural map for TEST.
How to join
How do you connect to TEST?
Press F1 in Rust and enter client.connect 31.61.226.232:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.