RUST METRICSFlight deck · live data
Data live Servers11,662 Players33,506 Populated2,814 Fresh wipes 3 h80 Scan5 min
‹ All servers37.67.194.228:28015
Offline Full Queue Fresh wipe Wipe due No query

LOCAL_MAIN

Offline 37.67.194.228:28015 checked 6d ago

moddedoxide
COM 1 · connect

Server instruments

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

Players now

0% full 7-day avg7-day peak
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 1
Rank#13,086top 59%
Last wipe6d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

Top 59% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 11:19 UTC6d ago 1 – running 1

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 should you expect from wipe day on LOCAL_MAIN?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

When does LOCAL_MAIN wipe?

To tell the rhythm of LOCAL_MAIN, too few of its wipes 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 it runs now was made 6 days 16 hours ago.

Lists and filters

How should you read the tags on LOCAL_MAIN?

Tags published by LOCAL_MAIN, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show LOCAL_MAIN?

These Rust Metrics lists carry LOCAL_MAIN: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Population

What position does LOCAL_MAIN hold among Rust servers?

Player hours over seven days put LOCAL_MAIN at #13,086, in the top 59% of all ranked servers.

What is the population on LOCAL_MAIN?

Reading for LOCAL_MAIN: offline at this moment; last seen 6 days 14 hours ago. Check: players over seven days. Average 0, peak 1.

Server

Where does LOCAL_MAIN sit?

No region comes from LOCAL_MAIN. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 37.67.194.228:28015.

What Rust version is LOCAL_MAIN on?

Reading: LOCAL_MAIN, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is LOCAL_MAIN, and is it online now?

Check: connection. LOCAL_MAIN is offline at this moment. Last contact was 6 days 14 hours ago. Reading: 0% uptime over the last 6 full days. It was up 0 of 144 hours. The first sighting on Rust Metrics was 22 October 2026.

Rules and settings

What settings and rules apply on LOCAL_MAIN?

No gather rate appears in the name: LOCAL_MAIN. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Join

How do you connect to LOCAL_MAIN?

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players Slots: 5.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^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.