TEST
Offline 94.243.13.111:28015 checked 6d 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- 187/250
- 120/200
- 19/250
- 11/250
- 20/100
- 28/225
Quick answers
from the figures on this pageWipe schedule
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. The world in play was created 6 days 15 hours ago.
Tag meanings
How should you read the tags on TEST?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp250 (Max players): The server holds 250 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from TEST. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show TEST?
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; Last wipe: In the last week.
Player count
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 6 days 15 hours ago. Seven-day reading: 0 players on average.
Operator and location
Where does TEST sit?
Reading: location. TEST gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 94.243.13.111:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.
Is TEST up, and how often does it stay up?
TEST reports offline. The last reading came 6 days 15 hours ago. Uptime for the last 6 full days: 0 of 144 hours, or 0%. The first sighting on Rust Metrics was 22 October 2026.
Map and rules
What settings and rules apply on TEST?
Reading the name gives no gather rate for TEST. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
Which map is live on TEST?
The game generates a procedural map for TEST.
How to join
How can you get onto TEST?
To join: start Rust, press F1 and type client.connect 94.243.13.111:28015. Or press Launch Rust here and Steam opens the game and connects you.