TEST
Offline 78.177.141.11:28015 checked 8d 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 bestTop 59% 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- 67/250
- 90/200
- 196/250
- 5/100
- 244/250
- 375/375
Quick answers
from the figures on this pageWipe schedule
How often does TEST wipe, and when?
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. 15 days 19 hours ago the current world was made.
Tags
How should you read the tags on TEST?
Check: tags. The game's server browser reads 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; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from TEST. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show TEST?
These Rust Metrics lists carry 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.
Player count
Where does TEST sit in the rankings?
Ranking for TEST: #13,160 on seven-day player hours, top 59% of all ranked servers.
How full does TEST get?
TEST is not responding; status offline, last seen 8 days 14 hours ago.
Server details
Where does TEST sit?
No region tag on TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 78.177.141.11:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.
What is the uptime on TEST, and is it online?
Reading: offline. TEST last answered 8 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 14 October 2026.
Settings and map
How is TEST configured, and what rules are in force?
Reading the name gives no gather rate for TEST. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: 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?
Check: map. Procedural, generated by the game, on TEST.
Join
What do you do to join TEST?
Press F1 in Rust and enter client.connect 78.177.141.11:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.