TEST
Offline 138.124.15.73:28015 checked 11d 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 65% 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- 9/200
- 1/400
- 2/75
- 1/100
- 4/400
- 4/150
Quick answers
from the figures on this pageWipe schedule
What wipe timing does TEST follow?
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 26 days 23 hours ago.
Tags
Which tags does TEST carry, and what do they mean?
These are the tags TEST publishes, and the server browser reads them: gmhardcore (Game mode): Check: ruleset. Hardcore, the harsher option; mp10 (Max players): The server holds 10 slots; ts0 (Group limit): No teams here: the setting is switched off; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): Game build reading: 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. 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?
On Rust Metrics, TEST sits in these lists: 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.
Occupancy
What position does TEST hold among Rust servers?
Ranking for TEST: #14,137 on seven-day player hours, top 65% of all ranked servers.
How full does TEST get?
Reading for TEST: offline at this moment; last seen 11 days 20 hours ago.
Operator and location
Where does TEST sit?
No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 138.124.15.73:28015.
What Rust version is TEST on?
Rust network protocol 2634 and build 166494 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.
Is TEST up, and how often does it stay up?
TEST reports offline. The last reading came 11 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 17 October 2026.
Settings and map
What rules does TEST enforce, and what are its settings?
Check: gather rate. The name TEST does not state one. No group limit is published. Mode check gives hardcore; Facepunch's most punishing mode. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
Which map is live on TEST?
The game generates a procedural map for TEST.
Join
How do you connect to TEST?
Press F1 in Rust and enter client.connect 138.124.15.73:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.