RUST METRICSFlight deck · live data
Data live Servers11,692 Players37,024 Populated2,928 Fresh wipes 3 h87 Scan5 min
‹ All servers185.65.133.26:28015
Offline Full Queue Fresh wipe Wipe due No query

Nebula Local Test

Offline 185.65.133.26:28015 checked 12d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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,180top 70%
Last wipe13d 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
15k10k15k20k14 Oct16 Oct18 Oct19 Oct21 Oct23 Oct

Top 70% 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 peak1players, 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 1, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 16:02 UTC13d ago 1 – 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

Wipe timing

What should you expect from wipe day on Nebula Local Test?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

When does Nebula Local Test wipe?

Its rhythm cannot be told from the wipes of Nebula Local Test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 13 days 10 hours ago.

Tag meanings

Which tags does Nebula Local Test carry, and what do they mean?

These are the tags Nebula Local Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Nebula Local Test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Nebula Local Test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

Where does Nebula Local Test sit in the rankings?

Ranking for Nebula Local Test: #15,180 on seven-day player hours, top 70% of all ranked servers.

What is the population on Nebula Local Test?

Reading for Nebula Local Test: offline at this moment; last seen 12 days 6 hours ago.

Server details

Which location does Nebula Local Test run from?

No region tag on Nebula Local Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 185.65.133.26:28015.

What Rust version is Nebula Local Test on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by Nebula Local Test. Check: protocol. To join, your game must match; Steam handles the update.

Is Nebula Local Test up, and how often does it stay up?

Nebula Local Test reports offline. The last reading came 12 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 14 October 2026.

Map and rules

What rules does Nebula Local Test enforce, and what are its settings?

Check: gather rate. The name Nebula Local Test does not state one. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is off. That is Valve's anti-cheat.

What map is Nebula Local Test on?

Check: map. Procedural, generated by the game, on Nebula Local Test.

Connection

How can you get onto Nebula Local Test?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build The server runs game build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

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.