TEST
Offline 84.244.19.136:28015 checked 43d 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- 205/500
- 121/100
- 183/225
- 126/700
- 19/200
- 50/1000
Quick answers
from the figures on this pageReset cycle
What wipe timing does TEST follow?
Its rhythm cannot be told from the wipes of TEST on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 66 days 3 hours ago.
Tag meanings
How should you read the tags on TEST?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2632 (Protocol): Protocol 2632: join only on the same game version; cs160556 (Build): Game build reading: 160556; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as 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.
Which lists and filters on Rust Metrics show TEST?
Rust Metrics lists featuring TEST: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
Where does TEST sit in the rankings?
Ranking for TEST: #15,416 on seven-day player hours, top – of all ranked servers.
What player count does TEST carry?
Reading for TEST: offline at this moment; last seen 43 days 5 hours ago.
Server
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. Connect using 84.244.19.136:28015.
What Rust version is TEST on?
Rust network protocol 2632 and build 160556 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 43 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 September 2026, recorded by Rust Metrics.
Settings and map
How is TEST configured, and what rules are in force?
Check: gather rate. The name TEST does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.
What map is TEST on?
Check: map. Procedural, generated by the game, on TEST.
Connection
How can you get onto TEST?
Check: join. Open Rust, press F1, then enter client.connect 84.244.19.136:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.