TEST
Offline 188.92.193.226:28015 checked 40d 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- 151/500
- 129/100
- 184/225
- 94/700
- 237/700
- 348/350
Quick answers
from the figures on this pageReset cycle
When does TEST wipe?
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 40 days 4 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): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2632 (Protocol): Your game must run protocol 2632 to get in; cs160556 (Build): Build 160556; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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?
On Rust Metrics, TEST sits in these lists: 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,415 on seven-day player hours, top – of all ranked servers.
How full does TEST get?
TEST is not responding; status offline, last seen 40 days 4 hours ago.
Server details
What location is TEST hosted in?
No region tag on TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 188.92.193.226:28015.
What Rust version is TEST on?
Rust network protocol 2632 and build 160556 on Windows is the build TEST runs. 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 40 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 19 September 2026.
Rules and settings
What settings and rules apply on TEST?
No gather rate appears in the name: TEST. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; 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. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
Which map is live on TEST?
Procedural map on TEST, made by the game's generator.
Join
How do you connect to TEST?
Press F1 in Rust and enter client.connect 188.92.193.226:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.