RUST METRICSFlight deck · live data
Data live Servers11,875 Players97,136 Populated3,915 Fresh wipes 3 h398 Scan5 min
‹ All servers203.23.179.213:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalServer

Offline 203.23.179.213:28015 checked 46d ago

moddedoxide
COM 1 · connect

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–score 0
Last wipe46d 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 LocalServer follow?

Its rhythm cannot be told from the wipes of LocalServer 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. 46 days 7 hours ago the current world was made.

Tags

How should you read the tags on LocalServer?

These are the tags LocalServer 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): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does LocalServer appear in Rust Metrics lists and filters?

On Rust Metrics, LocalServer sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

How full does LocalServer get?

LocalServer is not responding; status offline, last seen 46 days 4 hours ago.

Operator and location

Where does LocalServer sit?

Reading: location. LocalServer gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 203.23.179.213:28015.

What Rust version is LocalServer on?

Rust network protocol 2633 and build 163794 on Windows is the build LocalServer runs. Check: protocol. To join, your game must match; Steam handles the update.

Is LocalServer up, and how often does it stay up?

LocalServer reports offline. The last reading came 46 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does LocalServer enforce, and what are its settings?

Reading the name gives no gather rate for LocalServer. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on LocalServer?

Check: map. Procedural, generated by the game, on LocalServer.

Connection

How can you get onto LocalServer?

Check: join. Open Rust, press F1, then enter client.connect 203.23.179.213: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?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build Build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.