RUST METRICSFlight deck · live data
Data live Servers11,736 Players72,836 Populated3,680 Fresh wipes 3 h131 Scan5 min
‹ All servers91.79.41.68:28015
Offline Full Queue Fresh wipe Wipe due No query

Nebula Local Test

Offline 91.79.41.68: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,101top 70%
Last wipe12d 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
15k10k15k20k16 Oct17 Oct18 Oct20 Oct21 Oct22 Oct

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

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

Reset cycle

What wipe timing does Nebula Local Test follow?

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

Lists and filters

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): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; 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, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

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

Population

Where does Nebula Local Test sit in the rankings?

Player hours over seven days put Nebula Local Test at #15,101, in the top 70% of all ranked servers.

What is the population on Nebula Local Test?

Nebula Local Test is not responding; status offline, last seen 12 days 15 hours ago.

Server details

Which location does Nebula Local Test run from?

No region tag on Nebula Local Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 91.79.41.68:28015.

What Rust version is Nebula Local Test on?

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

How reliable is Nebula Local Test, and is it online now?

Reading: offline. Nebula Local Test last answered 12 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on Nebula Local Test?

Reading the name gives no gather rate for Nebula Local Test. 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 under Community. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on Nebula Local Test?

Procedural map on Nebula Local Test, made by the game's generator.

Join

How do you connect to Nebula Local Test?

Check: join. Open Rust, press F1, then enter client.connect 91.79.41.68:28015. Alternatively, use Launch Rust on this page: Steam opens Rust 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 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
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.