RUST METRICSFlight deck · live data
Data live Servers11,659 Players48,364 Populated3,165 Fresh wipes 3 h117 Scan5 min
‹ All servers5.18.144.106:28015
Offline Full Queue Fresh wipe Wipe due No query

Local PVE | Closed test

Offline 5.18.144.106:28015 checked 9d ago

moddedoxidepve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 0 /4

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,308top 70%
Last wipe9d 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
15k10k15k20k19 Oct20 Oct22 Oct23 Oct25 Oct26 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

Wipe timing

What wipe timing does Local PVE | Closed test follow?

To tell the rhythm of Local PVE | Closed test, too few of its wipes are on record. 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 it runs now was made 9 days 22 hours ago.

Lists and filters

How should you read the tags on Local PVE | Closed test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from Local PVE | Closed test. 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 Local PVE | Closed test?

Rust Metrics lists featuring Local PVE | Closed test: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

What position does Local PVE | Closed test hold among Rust servers?

Ranking for Local PVE | Closed test: #15,308 on seven-day player hours, top 70% of all ranked servers.

What player count does Local PVE | Closed test carry?

Status for Local PVE | Closed test: offline. Last seen 9 days 22 hours ago.

Operator and location

Where does Local PVE | Closed test sit?

No region tag on Local PVE | Closed test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 5.18.144.106:28015.

What Rust version is Local PVE | Closed test on?

Reading: Local PVE | Closed test, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Local PVE | Closed test, and is it online?

Local PVE | Closed test reports offline. The last reading came 9 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 October 2026, recorded by Rust Metrics.

Settings and map

How is Local PVE | Closed test configured, and what rules are in force?

Reading the name gives no gather rate for Local PVE | Closed test. The group cap is 8 players, which is the default in the game. pve, no combat against other players — that is the game mode. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Local PVE | Closed test?

The game generates a procedural map for Local PVE | Closed test.

Connection

How can you get onto Local PVE | Closed test?

Press F1 in Rust and enter client.connect 5.18.144.106: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 mp4,ptrak,$r?,v2634,^p,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players The server holds 4 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

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.