TEST
Offline 144.31.103.201:28015 checked 21d 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 66% 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- 3/200
- 1/400
- 2/75
- 3/100
- 4/400
- 0/150
Quick answers
from the figures on this pageWipe schedule
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 27 days 4 hours ago.
Tag meanings
Which tags does TEST carry, and what do they mean?
Tags published by TEST, read by the game's server browser: gmhardcore (Game mode): Check: ruleset. Hardcore, the harsher option; mp10 (Max players): 10 slots in total; ts0 (Group limit): Team play is disabled; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): The server runs game build 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show TEST?
These Rust Metrics lists carry 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; Game mode: Hardcore.
Player count
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #14,551, in the top 66% of all ranked servers.
What is the population on TEST?
Status for TEST: offline. Last seen 21 days 1 hours ago.
Operator and location
Which location does TEST run from?
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 144.31.103.201:28015.
What Rust version is TEST on?
Rust network protocol 2634 and build 166494 on Windows is the build TEST runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on TEST, and is it online?
TEST reports offline. The last reading came 21 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 8 October 2026.
Rules and settings
How is TEST configured, and what rules are in force?
Reading the name gives no gather rate for TEST. The group limit is not published. Mode check gives hardcore; Facepunch's most punishing mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is TEST on?
Check: map. Procedural, generated by the game, on TEST.
Connection
What do you do to join TEST?
Press F1 in Rust and enter client.connect 144.31.103.201:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.