TEST
Offline 85.172.90.26:28015 checked 39d ago
Server instruments
no direct query in 48 hoursPlayers now
40% 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- 30/500
- 127/100
- 43/225
- 33/700
- 9/200
- 0/500
Quick answers
from the figures on this pageWipe timing
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 41 days 9 hours ago.
Lists and filters
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; mp5 (Max players): 5 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; 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. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does TEST appear in Rust Metrics lists and filters?
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
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #11,696, in the top – of all ranked servers.
What player count does TEST carry?
Status for TEST: offline. Last seen 39 days 10 hours ago.
Operator and location
Which location does TEST run from?
No region comes from TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 85.172.90.26:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 163794, Windows. 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 39 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 17 September 2026, recorded by Rust Metrics.
Map and rules
How is TEST configured, and what rules are in force?
Reading the name gives no gather rate for TEST. The group cap is 8 players, which is the default in the game. 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. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TEST?
Check: map. Procedural, generated by the game, on TEST.
Join
How can you get onto TEST?
To join: start Rust, press F1 and type client.connect 85.172.90.26:28015. Or press Launch Rust here and Steam opens the game and connects you.