TEST
Offline 46.41.65.46:28015 checked 38d 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- 51/500
- 125/100
- 39/225
- 52/700
- 9/200
- 6/1000
Quick answers
from the figures on this pageWipe schedule
How often does TEST wipe, and when?
The rhythm of TEST's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 38 days 12 hours ago the current world was made.
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): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Game build reading: 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does TEST appear in Rust Metrics lists and filters?
These Rust Metrics lists carry TEST: 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.
Population
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #15,515, in the top – of all ranked servers.
How full does TEST get?
Status for TEST: offline. Last seen 38 days 7 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 46.41.65.46:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2633 and build 164530 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.
Is TEST up, and how often does it stay up?
TEST reports offline. The last reading came 38 days 7 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 20 September 2026.
Rules and settings
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. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TEST?
Procedural map on TEST, made by the game's generator.
Connection
How can you get onto TEST?
Check: join. Open Rust, press F1, then enter client.connect 46.41.65.46:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.