TEST
Offline 176.113.247.141:28015 checked 39d 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 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- 165/500
- 131/100
- 188/225
- 94/700
- 235/700
- 350/350
Quick answers
from the figures on this pageReset cycle
When does TEST wipe?
Its rhythm cannot be told from the wipes of TEST on record: there are too few. 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 53 days 5 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; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163207 (Build): The server runs game build 163207; 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 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?
Rust Metrics lists featuring 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?
Ranking for TEST: #13,272 on seven-day player hours, top – of all ranked servers.
How full does TEST get?
Status for TEST: offline. Last seen 39 days 4 hours ago.
Server details
What location is TEST hosted in?
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 176.113.247.141:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2633 and build 163207 on Windows, run by TEST. To get in, your game needs the same protocol; Steam applies the update.
How reliable is TEST, and is it online now?
TEST reports offline. The last reading came 39 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 20 September 2026.
Settings and map
What rules does TEST enforce, and what are its settings?
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. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
Which map is live on TEST?
Check: map. Procedural, generated by the game, on TEST.
How to join
How do you connect to TEST?
To join: start Rust, press F1 and type client.connect 176.113.247.141:28015. Or press Launch Rust here and Steam opens the game and connects you.