Test
Offline 5.42.211.127:28015 checked 2d 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 69% 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- 221/275
- 136/200
- 26/250
- 16/250
- 28/100
- 13/200
Quick answers
from the figures on this pageWipe timing
When does Test wipe?
The rhythm of Test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 36 days 19 hours ago.
Lists and filters
Which tags does Test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from Test. 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. 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?
Ranking for Test: #15,349 on seven-day player hours, top 69% of all ranked servers.
How full does Test get?
Reading for Test: offline at this moment; last seen 2 days 8 hours ago. A seven-day average of 0 players is the reading.
Server details
Where does Test sit?
No region tag on Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 5.42.211.127:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2633 and build 164530, Windows. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on Test, and is it online?
Reading: offline. Test last answered 2 days 8 hours ago. Reading: 1% uptime over the last 7 full days. It was up 1 of 168 hours. Reading: first seen 22 September 2026, recorded by Rust Metrics.
Settings and map
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. survival, standard play of gathering, building and raiding — 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.
What map is Test on?
The game generates a procedural map for Test.
Connection
How do you connect to Test?
Press F1 in Rust and enter client.connect 5.42.211.127:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.