TEST
Offline 13.140.30.221:28015 checked 9d ago
Server instruments
no direct query in 48 hoursPlayers now
10% 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 63% 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- 176/250
- 120/200
- 18/250
- 14/250
- 20/100
- 25/200
Quick answers
from the figures on this pageWipe schedule
What wipe timing does TEST follow?
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 9 days 4 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): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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?
These Rust Metrics lists carry TEST: 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; Last wipe: In the last 2 weeks.
Population
What position does TEST hold among Rust servers?
Ranking for TEST: #13,957 on seven-day player hours, top 63% of all ranked servers.
What player count does TEST carry?
Reading for TEST: offline at this moment; last seen 9 days 3 hours ago.
Server
What location is TEST hosted in?
Reading: location. TEST gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 13.140.30.221:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.
How reliable is TEST, and is it online now?
TEST reports offline. The last reading came 9 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 19 October 2026.
Settings and map
How is TEST configured, and what rules are in force?
Reading the name gives no gather rate for TEST. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
Which map is live on TEST?
Check: map. Procedural, generated by the game, on TEST.
Connection
How can you get onto TEST?
To join: start Rust, press F1 and type client.connect 13.140.30.221:28015. Or press Launch Rust here and Steam opens the game and connects you.