TEST
Offline 188.19.173.245:28015 checked 44d 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- 166/250
- 119/200
- 19/250
- 15/250
- 18/100
- 25/200
Quick answers
from the figures on this pageWipe schedule
When does TEST wipe?
Its rhythm cannot be told from the wipes of TEST on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 44 days 17 hours ago the current world was made.
Tag meanings
How should you read the tags on TEST?
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): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does TEST appear in Rust Metrics lists and filters?
These Rust Metrics lists carry TEST: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #15,050, in the top – of all ranked servers.
What player count does TEST carry?
TEST is not responding; status offline, last seen 44 days 16 hours ago.
Operator and location
Where does TEST sit?
No region comes from TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 188.19.173.245:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 163794 on Windows is the build TEST runs. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on TEST, and is it online?
TEST reports offline. The last reading came 44 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 14 September 2026, recorded by Rust Metrics.
Rules and settings
How is TEST configured, and what rules are in force?
Check: gather rate. The name TEST does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TEST?
Procedural map on TEST, made by the game's generator.
Join
How can you get onto TEST?
Check: join. Open Rust, press F1, then enter client.connect 188.19.173.245:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.