RUST METRICSFlight deck · live data
Data live Servers11,582 Players33,161 Populated2,855 Fresh wipes 3 h65 Scan5 min
‹ All servers5.251.252.232:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 5.251.252.232:28015 checked 13d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,229top 70%
Last wipe13d 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
15k10k15k20k14 Oct15 Oct17 Oct18 Oct20 Oct21 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 schedule

What wipe timing does LocalRustServer1337 follow?

The rhythm of LocalRustServer1337's wipes cannot be told yet: too few 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 in play was created 13 days 12 hours ago.

Tag meanings

How should you read the tags on LocalRustServer1337?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; 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): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from LocalRustServer1337. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does LocalRustServer1337 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring LocalRustServer1337: 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; Last wipe: In the last 2 weeks.

Player count

Where does LocalRustServer1337 sit in the rankings?

Player hours over seven days put LocalRustServer1337 at #15,229, in the top 70% of all ranked servers.

What is the population on LocalRustServer1337?

Status for LocalRustServer1337: offline. Last seen 13 days 11 hours ago.

Server

Which location does LocalRustServer1337 run from?

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

What Rust version is LocalRustServer1337 on?

Rust network protocol 2634 and build 167781 on Windows is the build LocalRustServer1337 runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is LocalRustServer1337, and is it online now?

LocalRustServer1337 reports offline. The last reading came 13 days 11 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 14 October 2026, recorded by Rust Metrics.

Rules and settings

How is LocalRustServer1337 configured, and what rules are in force?

No gather rate appears in the name: LocalRustServer1337. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is off.

What map is LocalRustServer1337 on?

The game generates a procedural map for LocalRustServer1337.

Join

What do you do to join LocalRustServer1337?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
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 The server runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock 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.