RUST METRICSFlight deck · live data
Data live Servers11,791 Players67,584 Populated3,634 Fresh wipes 3 h129 Scan5 min
‹ All servers138.248.55.209:25566
Offline Full Queue Fresh wipe Wipe due No query

Nexus Rust Test

Offline 138.248.55.209:25566 checked 24d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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#16,003top 71%
Last wipe25d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k27 Sep30 Sep3 Oct5 Oct8 Oct11 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 02:23 UTC25d ago 0 – running 0

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

Reset cycle

What happens on Nexus Rust Test when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does Nexus Rust Test follow?

Its rhythm cannot be told from the wipes of Nexus Rust 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 in play was created 25 days 19 hours ago.

Tags

How should you read the tags on Nexus Rust Test?

These are the tags Nexus Rust Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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 Nexus Rust Test?

These Rust Metrics lists carry Nexus Rust Test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does Nexus Rust Test sit in the rankings?

Ranking for Nexus Rust Test: #16,003 on seven-day player hours, top 71% of all ranked servers.

How full does Nexus Rust Test get?

Reading for Nexus Rust Test: offline at this moment; last seen 24 days 15 hours ago.

Server

Which location does Nexus Rust Test run from?

No region tag on Nexus Rust Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 138.248.55.209:25566.

What Rust version is Nexus Rust Test on?

Rust network protocol 2634 and build 166652 on Linux is the build Nexus Rust Test runs. To get in, your game needs the same protocol; Steam applies the update.

Is Nexus Rust Test up, and how often does it stay up?

Reading: offline. Nexus Rust Test last answered 24 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 27 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Nexus Rust Test?

Reading the name gives no gather rate for Nexus Rust Test. 8 players per group, the default value. 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. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is Nexus Rust Test on?

The game generates a procedural map for Nexus Rust Test.

Connection

How can you get onto Nexus Rust Test?

To join: start Rust, press F1 and type client.connect 138.248.55.209:25566. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.