TEST
Offline 94.180.151.184:28015 checked 30d 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 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- 555/625
- 411/450
- 175/250
- 53/100
- 178/250
- 346/225
Quick answers
from the figures on this pageReset cycle
What wipe timing does TEST follow?
The rhythm of TEST's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 47 days ago.
Tag meanings
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): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from TEST. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
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: #14,546 on seven-day player hours, top 61% of all ranked servers.
What is the population on TEST?
TEST is not responding; status offline, last seen 30 days 16 hours ago.
Operator and location
Where does TEST sit?
Reading: location. TEST gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 94.180.151.184:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 165217, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is TEST, and is it online now?
Check: connection. TEST is offline at this moment. Last contact was 30 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 28 September 2026, recorded by Rust Metrics.
Settings and map
How is TEST configured, and what rules are in force?
No gather rate appears in the name: TEST. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
What map is TEST on?
Procedural map on TEST, made by the game's generator.
Connection
How do you connect to TEST?
Check: join. Open Rust, press F1, then enter client.connect 94.180.151.184:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.