NX_Server
Offline 151.238.96.20:28015 checked 45d ago
Server instruments
no direct query in 48 hoursPlayers now
5% 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
Next wipe Thursday 5 November, 19:00 UTC, in 8d 1h. The 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- 126/700
- 50/1000
- 453/700
- 178/1000
- 24/1000
- 580/1000
Quick answers
from the figures on this pageWipe timing
How often does NX_Server wipe, and when?
The estimate for NX_Server's next wipe comes from the force wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 45 days 10 hours ago. Its tags carry a monthly wipe schedule.
Tags
Which tags does NX_Server carry, and what do they mean?
Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp19 (Max players): 19 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; cs163794 (Build): Build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from NX_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 NX_Server?
Rust Metrics lists featuring NX_Server: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Occupancy
How full does NX_Server get?
Status for NX_Server: offline. Last seen 45 days 10 hours ago.
Operator and location
Which location does NX_Server run from?
No region tag on NX_Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 151.238.96.20:28015.
What Rust version is NX_Server on?
Rust network protocol 2633 and build 163794 on Windows is the build NX_Server runs. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on NX_Server, and is it online?
Reading: offline. NX_Server last answered 45 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Settings and map
What settings and rules apply on NX_Server?
Check: gather rate. The name NX_Server does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
Join
How can you get onto NX_Server?
Press F1 in Rust and enter client.connect 151.238.96.20:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.