Test
Offline 178.68.125.179:28015 checked 26d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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 61% 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- 476/575
- 441/475
- 739/250
- 64/100
- 458/250
- 26/250
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Test follow?
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. 26 days 17 hours ago the current world was made.
Tag meanings
Which tags does Test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): Build 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Test appear in Rust Metrics lists and filters?
On Rust Metrics, Test sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does Test sit in the rankings?
Ranking for Test: #13,842 on seven-day player hours, top 61% of all ranked servers.
How full does Test get?
Status for Test: offline. Last seen 26 days 17 hours ago.
Server
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 178.68.125.179:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 166586, Windows. 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 26 days 17 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 2 October 2026.
Settings and map
What settings and rules apply on Test?
Reading the name gives no gather rate for Test. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is Test on?
The game generates a procedural map for Test.
Connection
How can you get onto Test?
Press F1 in Rust and enter client.connect 178.68.125.179:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.