TEST
Offline 13.140.30.18:28015 checked 8d 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 59% 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- 421/400
- 339/350
- 34/250
- 29/250
- 51/100
- 145/200
Quick answers
from the figures on this pageWipe timing
How often does TEST wipe, and when?
Its rhythm cannot be told from the wipes of TEST on record: there are too few. 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 8 days 9 hours ago.
Tag meanings
How should you read the tags on TEST?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty 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. 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; Last wipe: In the last 2 weeks.
Population
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #13,134, in the top 59% of all ranked servers.
How full does TEST get?
TEST is not responding; status offline, last seen 8 days 7 hours ago.
Server details
What location is TEST hosted in?
No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 13.140.30.18: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.
Is TEST up, and how often does it stay up?
Check: connection. TEST is offline at this moment. Last contact was 8 days 7 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 21 October 2026, recorded by Rust Metrics.
Rules and settings
How is TEST configured, and what rules are in force?
No gather rate appears in the name: TEST. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.
What map is TEST on?
Check: map. Procedural, generated by the game, on TEST.
How to join
How can you get onto TEST?
To join: start Rust, press F1 and type client.connect 13.140.30.18:28015. Or press Launch Rust here and Steam opens the game and connects you.