TEST
Offline 104.28.225.185:28015 checked 28d 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 60% 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- 154/250
- 127/200
- 15/250
- 17/250
- 13/100
- 43/200
Quick answers
from the figures on this pageWipe timing
When does TEST wipe?
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 it runs now was made 28 days 14 hours ago.
Tags
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; mp10 (Max players): 10 slots in total; 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): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. 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?
Rust Metrics lists featuring 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
Where does TEST sit in the rankings?
Player hours over seven days put TEST at #14,389, in the top 60% of all ranked servers.
How full does TEST get?
TEST is not responding; status offline, last seen 28 days 12 hours ago.
Server
Which location does TEST run from?
No region tag on TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 104.28.225.185:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.
How reliable is TEST, and is it online now?
Reading: offline. TEST last answered 28 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 30 September 2026.
Map and rules
How is TEST configured, and what rules are in force?
Check: gather rate. The name TEST does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is TEST on?
Check: map. Procedural, generated by the game, on TEST.
Join
How do you connect to TEST?
Check: join. Open Rust, press F1, then enter client.connect 104.28.225.185:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.