TEST
Offline 213.109.141.52:28015 checked 44d 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 bestWipe 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- 145/250
- 131/200
- 15/250
- 19/250
- 16/100
- 46/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. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 44 days 17 hours ago.
Tags
How should you read the tags on TEST?
These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does TEST appear in Rust Metrics lists and filters?
On Rust Metrics, TEST sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #15,049, in the top – of all ranked servers.
What player count does TEST carry?
Reading for TEST: offline at this moment; last seen 44 days 17 hours ago.
Operator and location
What location is TEST hosted in?
Reading: location. TEST gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 213.109.141.52:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 163794 on Windows is the build TEST runs. Check: protocol. To join, your game must match; Steam handles the update.
Is TEST up, and how often does it stay up?
Reading: offline. TEST last answered 44 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 14 September 2026, recorded by Rust Metrics.
Settings and map
How is TEST configured, and what rules are in force?
Check: gather rate. The name TEST does not state one. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.
Which map is live on TEST?
Procedural map on TEST, made by the game's generator.
How to join
How can you get onto TEST?
Check: join. Open Rust, press F1, then enter client.connect 213.109.141.52:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.