TEST
Offline 193.27.19.240:28015 checked 44d 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- 34/500
- 120/100
- 57/225
- 10/700
- 42/700
- 43/200
Quick answers
from the figures on this pageWipe timing
When does TEST wipe?
To tell the rhythm of TEST, too few of its wipes 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 in play was created 44 days 17 hours ago.
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): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
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
What position does TEST hold among Rust servers?
Ranking for TEST: #13,258 on seven-day player hours, top – of all ranked servers.
What is the population on TEST?
Status for TEST: offline. Last seen 44 days 14 hours ago.
Server
What location is TEST hosted in?
No region tag on TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 193.27.19.240:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 163794, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is TEST, and is it online now?
TEST reports offline. The last reading came 44 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 15 September 2026.
Settings and map
What settings and rules apply on TEST?
No gather rate appears in the name: TEST. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TEST?
Check: map. Procedural, generated by the game, on TEST.
How to join
What do you do to join TEST?
Press F1 in Rust and enter client.connect 193.27.19.240:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.