TEST
Offline 185.244.37.5:28015 checked 20d 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 70% 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- 53/500
- 124/100
- 41/225
- 52/700
- 8/200
- 7/1000
Quick answers
from the figures on this pageWipe schedule
How often does TEST wipe, and when?
Its rhythm cannot be told from the wipes of TEST on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 21 days 10 hours ago the current world was made.
Tags
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): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server from TEST. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does TEST appear in Rust Metrics lists and filters?
Rust Metrics lists featuring TEST: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #15,429, in the top 70% of all ranked servers.
How full does TEST get?
TEST is not responding; status offline, last seen 20 days 18 hours ago.
Server
Which location does TEST run from?
No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 185.244.37.5:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2634 and build 166652 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.
Is TEST up, and how often does it stay up?
TEST reports offline. The last reading came 20 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 8 October 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on TEST?
Check: gather rate. The name TEST does not state one. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
What map is TEST on?
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 185.244.37.5:28015. Or press Launch Rust here and Steam opens the game and connects you.