Test
Offline 188.68.94.244:28015 checked 19d 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 bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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- 140/250
- 112/200
- 14/250
- 18/250
- 11/100
- 15/200
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
To tell the rhythm of Test, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 19 days 13 hours ago.
Tag meanings
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; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. 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?
Rust Metrics lists featuring Test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
What position does Test hold among Rust servers?
Player hours over seven days put Test at #15,863, in the top 72% of all ranked servers.
How full does Test get?
Status for Test: offline. Last seen 19 days 13 hours ago.
Server details
Where does Test sit?
Reading: location. Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 188.68.94.244:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 167398, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Test, and is it online now?
Reading: offline. Test last answered 19 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 9 October 2026, recorded by Rust Metrics.
Settings and map
What rules does Test enforce, and what are its settings?
Reading the name gives no gather rate for Test. 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. Under Community in the server browser you will find it. Anti-cheat reading: VAC off, Valve's system.
Which map is live on Test?
The game generates a procedural map for Test.
Connection
How do you connect to Test?
Check: join. Open Rust, press F1, then enter client.connect 188.68.94.244:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.