RUST METRICSFlight deck · live data
Data live Servers11,676 Players50,302 Populated3,170 Fresh wipes 3 h121 Scan5 min
‹ All servers46.147.144.13:28015
Offline Full Queue Fresh wipe Wipe due No query

LOCAL SERVER

Offline 46.147.144.13:28015 checked 30d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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#16,970top 71%
Last wipe51d 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 Sep1 Oct3 Oct5 Oct

Top 71% 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 LOCAL SERVER follow?

Its rhythm cannot be told from the wipes of LOCAL SERVER 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 51 days 17 hours ago.

Tag meanings

How should you read the tags on LOCAL SERVER?

Check: tags. The game's server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163207 (Build): Game build reading: 163207; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from LOCAL 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 SERVER?

On Rust Metrics, LOCAL SERVER sits in these lists: 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.

Player count

What position does LOCAL SERVER hold among Rust servers?

Player hours over seven days put LOCAL SERVER at #16,970, in the top 71% of all ranked servers.

How full does LOCAL SERVER get?

LOCAL SERVER is not responding; status offline, last seen 30 days 17 hours ago.

Operator and location

Which location does LOCAL SERVER run from?

No region comes from LOCAL SERVER. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 46.147.144.13:28015.

What Rust version is LOCAL SERVER on?

Version check: Rust network protocol 2633 and build 163207 on Windows, run by LOCAL SERVER. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is LOCAL SERVER, and is it online now?

LOCAL SERVER reports offline. The last reading came 30 days 17 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 LOCAL SERVER?

Check: gather rate. The name LOCAL SERVER does not state one. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on LOCAL SERVER?

Procedural map on LOCAL SERVER, made by the game's generator.

Connection

How can you get onto LOCAL SERVER?

To join: start Rust, press F1 and type client.connect 46.147.144.13:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmvanilla,cs163207,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp100
Max players The server holds 100 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163207
Build Game build reading: 163207.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.