RUST METRICSFlight deck · live data
Data live Servers11,801 Players73,164 Populated3,682 Fresh wipes 3 h113 Scan5 min
‹ All servers37.67.192.175:28015
Offline Full Queue Fresh wipe Wipe due No query

LOCAL_MAIN

Offline 37.67.192.175:28015 checked 43d ago

moddedoxide
COM 1 · connect
Launch Rust and join

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 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,404no region published
Last wipe44d 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
15k10k15k20k20 Sep21 Sep22 Sep
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

How often does LOCAL_MAIN wipe, and when?

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 44 days 12 hours ago.

Lists and filters

How should you read the tags on LOCAL_MAIN?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; 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; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from LOCAL_MAIN. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show LOCAL_MAIN?

Rust Metrics lists featuring LOCAL_MAIN: 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

Where does LOCAL_MAIN sit in the rankings?

Ranking for LOCAL_MAIN: #15,404 on seven-day player hours, top – of all ranked servers.

What player count does LOCAL_MAIN carry?

LOCAL_MAIN is not responding; status offline, last seen 43 days 3 hours ago.

Operator and location

Which location does LOCAL_MAIN run from?

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

What Rust version is LOCAL_MAIN on?

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

How reliable is LOCAL_MAIN, and is it online now?

Reading: offline. LOCAL_MAIN last answered 43 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 14 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on LOCAL_MAIN?

Reading the name gives no gather rate for LOCAL_MAIN. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. 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. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is LOCAL_MAIN on?

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

Connection

How do you connect to LOCAL_MAIN?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
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.
cs163794
Build The server runs game build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

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