TEST
Offline 104.28.212.76:28015 checked 39d 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 bestWipe 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- 63/500
- 129/100
- 75/225
- 18/200
- 67/700
- 15/1000
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 monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 40 days 6 hours ago.
Tags
Which tags does TEST carry, and what do they mean?
These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): The server runs game build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show TEST?
On Rust Metrics, TEST sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
What position does TEST hold among Rust servers?
Ranking for TEST: #15,398 on seven-day player hours, top – of all ranked servers.
How full does TEST get?
Status for TEST: offline. Last seen 39 days 10 hours ago.
Server details
Which location does TEST run from?
Reading: location. TEST gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 104.28.212.76:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 164530, 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 39 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 18 September 2026, recorded by Rust Metrics.
Settings and map
How is TEST configured, and what rules are in force?
Check: gather rate. The name TEST does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
What map is TEST on?
The game generates a procedural map for TEST.
Join
What do you do to join TEST?
To join: start Rust, press F1 and type client.connect 104.28.212.76:28015. Or press Launch Rust here and Steam opens the game and connects you.