RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h14 Scan5 min
‹ All servers104.28.201.88:28015
Offline Full Queue Fresh wipe Wipe due No query

Nexusking Test Server

Offline 104.28.201.88:28015 checked 44d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,015no region published
Last wipe54d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep
PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

How often does Nexusking Test Server wipe, and when?

Its rhythm cannot be told from the wipes of Nexusking Test Server 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. 54 days 15 hours ago the current world was made.

Tags

How should you read the tags on Nexusking Test Server?

These are the tags Nexusking Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs162929 (Build): The server runs game build 162929; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. 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 Nexusking Test Server?

These Rust Metrics lists carry Nexusking Test Server: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does Nexusking Test Server hold among Rust servers?

Player hours over seven days put Nexusking Test Server at #15,015, in the top – of all ranked servers.

What is the population on Nexusking Test Server?

Reading for Nexusking Test Server: offline at this moment; last seen 44 days 4 hours ago.

Server details

Which location does Nexusking Test Server run from?

Reading: location. Nexusking Test Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 104.28.201.88:28015.

What Rust version is Nexusking Test Server on?

Rust network protocol 2633 and build 162929 on Windows is the build Nexusking Test Server runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Nexusking Test Server, and is it online now?

Nexusking Test Server reports offline. The last reading came 44 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 14 September 2026, recorded by Rust Metrics.

Settings and map

What rules does Nexusking Test Server enforce, and what are its settings?

No gather rate appears in the name: Nexusking Test Server. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is Nexusking Test Server on?

Procedural map on Nexusking Test Server, made by the game's generator.

How to join

What do you do to join Nexusking Test Server?

Check: join. Open Rust, press F1, then enter client.connect 104.28.201.88:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs162929
Build The server runs game build 162929.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.