TEST
Offline 109.252.56.141:28015 checked 23d 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 61% 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- 4/200
- 0/400
- 3/75
- 0/100
- 5/400
- 0/150
Quick answers
from the figures on this pageReset cycle
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 it runs now was made 27 days 3 hours ago.
Tag meanings
How should you read the tags on TEST?
These are the tags TEST publishes, and the server browser reads them: gmhardcore (Game mode): A harsher set of rules: hardcore; mp10 (Max players): Slots: 10; ts0 (Group limit): Teams are off on this server; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166494 (Build): Game build reading: 166494; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none 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?
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; Game mode: Hardcore.
Player count
Where does TEST sit in the rankings?
Player hours over seven days put TEST at #13,798, in the top 61% of all ranked servers.
What player count does TEST carry?
TEST is not responding; status offline, last seen 23 days 9 hours ago.
Server
Which location does TEST run from?
Reading: location. TEST gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 109.252.56.141: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.
Is TEST up, and how often does it stay up?
Reading: offline. TEST last answered 23 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 5 October 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on TEST?
Check: gather rate. The name TEST does not state one. No group limit is published. The mode is hardcore. Note the following: Facepunch's most punishing mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TEST?
Procedural map on TEST, made by the game's generator.
How to join
How can you get onto TEST?
Check: join. Open Rust, press F1, then enter client.connect 109.252.56.141:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.