TEST
Offline 104.28.246.232:28015 checked 23d 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 71% 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- 636/675
- 485/525
- 59/250
- 36/250
- 138/200
- 255/300
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. 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 23 days 23 hours ago.
Tag meanings
Which tags does TEST carry, and what do they mean?
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): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from TEST. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show TEST?
On Rust Metrics, TEST sits in these lists: 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
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #15,961, in the top 71% of all ranked servers.
What is the population on TEST?
TEST is not responding; status offline, last seen 23 days 20 hours ago.
Operator and location
Where does TEST sit?
No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 104.28.246.232:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2634 and build 166652, Windows. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is TEST, and is it online now?
Check: connection. TEST is offline at this moment. Last contact was 23 days 20 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 4 October 2026.
Settings and map
What rules does TEST enforce, and what are its settings?
Reading the name gives no gather rate for TEST. 8 players per group, the default value. Mode check gives survival; 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.
Join
How can you get onto TEST?
To join: start Rust, press F1 and type client.connect 104.28.246.232:28015. Or press Launch Rust here and Steam opens the game and connects you.