TEST
Offline 5.44.169.105:28015 checked 40d 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 bestWipe 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- 221/275
- 136/200
- 26/250
- 16/250
- 28/100
- 13/200
Quick answers
from the figures on this pageWipe schedule
What wipe timing does TEST follow?
To tell the rhythm of TEST, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 40 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: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does TEST appear in Rust Metrics lists and filters?
On Rust Metrics, TEST sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does TEST sit in the rankings?
Player hours over seven days put TEST at #15,383, in the top – of all ranked servers.
How full does TEST get?
TEST is not responding; status offline, last seen 40 days 11 hours ago.
Server details
Which location does TEST run from?
Reading: location. TEST gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 5.44.169.105:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2633 and build 164530 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is TEST, and is it online now?
Reading: offline. TEST last answered 40 days 11 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 18 September 2026.
Settings and map
What rules does TEST enforce, and what are its settings?
Check: gather rate. The name TEST does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TEST?
The game generates a procedural map for TEST.
How to join
What do you do to join TEST?
To join: start Rust, press F1 and type client.connect 5.44.169.105:28015. Or press Launch Rust here and Steam opens the game and connects you.