Test
Offline 31.41.67.89:28015 checked 36d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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 58% 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- 551/625
- 33/250
- 57/250
- 289/325
- 112/200
- 120/150
Quick answers
from the figures on this pageReset cycle
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. 38 days 14 hours ago the current world was made.
Tags
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): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164924 (Build): The server runs game build 164924; ptrak (Networking): This is RakNet, Rust's usual network layer; $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?
On Rust Metrics, Test sits in these lists: 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
What position does Test hold among Rust servers?
Player hours over seven days put Test at #13,288, in the top 58% of all ranked servers.
What is the population on Test?
Status for Test: offline. Last seen 36 days 13 hours ago.
Operator and location
What location is Test hosted in?
No region comes from Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 31.41.67.89:28015.
What Rust version is Test on?
Rust network protocol 2633 and build 164924 on Windows is the build Test runs. 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 36 days 13 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on Test?
Reading the name gives no gather rate for Test. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is Test on?
Check: map. Procedural, generated by the game, on Test.
Connection
What do you do to join Test?
To join: start Rust, press F1 and type client.connect 31.41.67.89:28015. Or press Launch Rust here and Steam opens the game and connects you.