RUST METRICSFlight deck · live data
Data live Servers11,597 Players47,678 Populated3,062 Fresh wipes 3 h111 Scan5 min
‹ All servers77.73.135.51:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Rust Custom Map Test

Offline 77.73.135.51:28015 checked 46d ago

moddedoxidepve
COM 1 · connect

Server instruments

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

Players now

20% 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–score 0
Last wipe47d 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
No rank history yet.
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 schedule

What wipe timing does Local Rust Custom Map Test follow?

To tell the rhythm of Local Rust Custom Map 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 in play was created 47 days 21 hours ago.

Tag meanings

How should you read the tags on Local Rust Custom Map Test?

These are the tags Local Rust Custom Map Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs162929 (Build): Game build reading: 162929; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. 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 Rust Custom Map Test?

These Rust Metrics lists carry Local Rust Custom Map Test: Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What is the population on Local Rust Custom Map Test?

Local Rust Custom Map Test is not responding; status offline, last seen 46 days 19 hours ago.

Server details

Which location does Local Rust Custom Map Test run from?

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

What Rust version is Local Rust Custom Map Test on?

Reading: Local Rust Custom Map Test, Rust network protocol 2633 and build 162929, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Local Rust Custom Map Test, and is it online?

Reading: offline. Local Rust Custom Map Test last answered 46 days 19 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 13 September 2026.

Settings and map

What settings and rules apply on Local Rust Custom Map Test?

No gather rate appears in the name: Local Rust Custom Map Test. The group cap is 8 players, which is the default in the game. Mode check gives pve; other players are not fought. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Connection

What do you do to join Local Rust Custom Map Test?

Check: join. Open Rust, press F1, then enter client.connect 77.73.135.51:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,^p,gmrust,cs162929,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs162929
Build Game build reading: 162929.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.