RUST METRICSFlight deck · live data
Data live Servers11,615 Players38,895 Populated2,943 Fresh wipes 3 h85 Scan5 min
‹ All servers93.90.111.26:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalServer

Offline 93.90.111.26:28015 checked 42d 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#13,349no region published
Last wipe45d 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 Sep23 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

Wipe timing

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. 45 days 22 hours ago the current world was made.

Tag meanings

How should you read the tags on LocalServer?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server from LocalServer. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does LocalServer appear in Rust Metrics lists and filters?

These Rust Metrics lists carry LocalServer: 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.

Population

What position does LocalServer hold among Rust servers?

Player hours over seven days put LocalServer at #13,349, in the top – of all ranked servers.

What is the population on LocalServer?

Status for LocalServer: offline. Last seen 42 days 20 hours ago.

Server details

Which location does LocalServer run from?

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

What Rust version is LocalServer on?

Version check: Rust network protocol 2633 and build 163794 on Windows, run by LocalServer. To get in, your game needs the same protocol; Steam applies the update.

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

LocalServer reports offline. The last reading came 42 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 16 September 2026.

Settings and map

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

Reading the name gives no gather rate for LocalServer. 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. Check: PvP. Fighting and raiding between players are allowed. 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.

Which map is live on LocalServer?

The game generates a procedural map for LocalServer.

Join

What do you do to join LocalServer?

Press F1 in Rust and enter client.connect 93.90.111.26:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

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 The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Game build reading: 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.