RUST METRICSFlight deck · live data
Data live Servers11,808 Players73,203 Populated3,760 Fresh wipes 3 h138 Scan5 min
‹ All servers176.241.26.3:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST SERVER STAGING

Offline 176.241.26.3:28015 checked 30d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

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

Players now

100% 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#14,545top 61%
Last wipe32d 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
15k10k15k20k25 Sep27 Sep29 Sep30 Sep2 Oct4 Oct

Top 61% 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

How often does TEST SERVER STAGING wipe, and when?

To tell the rhythm of TEST SERVER STAGING, too few of its wipes are on record. 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 32 days 3 hours ago.

Tags

How should you read the tags on TEST SERVER STAGING?

Tags published by TEST SERVER STAGING, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; 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; cs165964 (Build): The server runs game build 165964; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TEST SERVER STAGING?

Rust Metrics lists featuring TEST SERVER STAGING: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does TEST SERVER STAGING hold among Rust servers?

Player hours over seven days put TEST SERVER STAGING at #14,545, in the top 61% of all ranked servers.

How full does TEST SERVER STAGING get?

Reading for TEST SERVER STAGING: offline at this moment; last seen 30 days 6 hours ago.

Operator and location

What location is TEST SERVER STAGING hosted in?

No region comes from TEST SERVER STAGING. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 176.241.26.3:28015.

What Rust version is TEST SERVER STAGING on?

Reading: TEST SERVER STAGING, Rust network protocol 2634 and build 165964, Windows. To get in, your game needs the same protocol; Steam applies the update.

How reliable is TEST SERVER STAGING, and is it online now?

Reading: offline. TEST SERVER STAGING last answered 30 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 25 September 2026.

Rules and settings

What settings and rules apply on TEST SERVER STAGING?

No gather rate appears in the name: TEST SERVER STAGING. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. VAC is off. That is Valve's anti-cheat.

What map is TEST SERVER STAGING on?

The game generates a procedural map for TEST SERVER STAGING.

How to join

How do you connect to TEST SERVER STAGING?

Press F1 in Rust and enter client.connect 176.241.26.3:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmvanilla,cs165964,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
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.
cs165964
Build The server runs game build 165964.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the 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.