TEST
Offline 92.208.15.18:28015 checked 45d 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 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- 102/500
- 121/100
- 120/225
- 46/700
- 3/200
- 20/1000
Quick answers
from the figures on this pageWipe schedule
When does TEST wipe?
The rhythm of TEST's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 53 days 14 hours ago.
Lists and filters
Which tags does TEST carry, and what do they mean?
Tags published by TEST, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163207 (Build): Game build reading: 163207; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. 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?
These Rust Metrics lists carry 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.
Player count
What is the population on TEST?
Reading for TEST: offline at this moment; last seen 45 days 20 hours ago.
Server
What location is TEST hosted in?
No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 92.208.15.18:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 163207, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is TEST up, and how often does it stay up?
TEST reports offline. The last reading came 45 days 20 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What rules does TEST enforce, and what are its settings?
Check: gather rate. The name TEST does not state one. No limit is set beyond the default. Groups take up to 8 players. 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. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is off.
What map is TEST on?
Procedural map on TEST, made by the game's generator.
How to join
What do you do to join TEST?
Press F1 in Rust and enter client.connect 92.208.15.18:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.