Test
Offline 188.92.22.146:28015 checked 43d 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- 86/500
- 121/100
- 79/225
- 70/700
- 23/200
- 12/1000
Quick answers
from the figures on this pageWipe timing
What wipe timing does Test follow?
The rhythm of Test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 45 days 9 hours ago the current world was made.
Lists and filters
How should you read the tags on Test?
Tags published by Test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): The server runs game build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. 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. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does Test sit in the rankings?
Player hours over seven days put Test at #13,334, in the top – of all ranked servers.
What player count does Test carry?
Status for Test: offline. Last seen 43 days ago.
Server
Where does Test sit?
No region comes from Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 188.92.22.146:28015.
What Rust version is Test on?
Version check: Rust network protocol 2633 and build 163794 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?
Test reports offline. The last reading came 43 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
How is Test configured, and what rules are in force?
Check: gather rate. The name Test does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. 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 do you connect to Test?
To join: start Rust, press F1 and type client.connect 188.92.22.146:28015. Or press Launch Rust here and Steam opens the game and connects you.