RUST METRICSFlight deck · live data
Data live Servers11,691 Players35,842 Populated2,916 Fresh wipes 3 h97 Scan5 min
‹ All servers108.237.91.203:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust Solo PvE - Local

Offline 108.237.91.203:28015 checked 15d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 238 /4

Players now

5950% 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#2,733top 13%
Last wipe16d 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
12.5k5k7.5k10k3 Oct6 Oct10 Oct13 Oct17 Oct20 Oct

Top 13% 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.

usual gap2.3 daysbetween real wipes
wipe-day peak300players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Mon 12 OctSat 10 Oct
0100200300400+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 06:24 UTC16d ago 300 – running 232
Sat 10 Oct, 00:12 UTC19d ago 301 held half 2.3 days 193

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 should you expect from wipe day on Rust Solo PvE - Local?

At their busiest, its recent wipes drew 300 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 100% of its recent wipes.

What wipe timing does Rust Solo PvE - Local follow?

The rhythm of Rust Solo PvE - Local's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 16 days 20 hours ago.

Tag meanings

How should you read the tags on Rust Solo PvE - Local?

These are the tags Rust Solo PvE - Local publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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.

Where does Rust Solo PvE - Local appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Rust Solo PvE - Local: 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; Players now: At least 200.

Occupancy

Where does Rust Solo PvE - Local sit in the rankings?

Player hours over seven days put Rust Solo PvE - Local at #2,733, in the top 13% of all ranked servers.

What is the population on Rust Solo PvE - Local?

Reading for Rust Solo PvE - Local: offline at this moment; last seen 15 days 23 hours ago.

Server

Where does Rust Solo PvE - Local sit?

No region comes from Rust Solo PvE - Local. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 108.237.91.203:28015.

What Rust version is Rust Solo PvE - Local on?

Reading: Rust Solo PvE - Local, Rust network protocol 2634 and build 166652, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is Rust Solo PvE - Local up, and how often does it stay up?

Check: connection. Rust Solo PvE - Local is offline at this moment. Last contact was 15 days 23 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 3 October 2026.

Map and rules

How is Rust Solo PvE - Local configured, and what rules are in force?

Check: gather rate. The name Rust Solo PvE - Local does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is Rust Solo PvE - Local on?

The game generates a procedural map for Rust Solo PvE - Local.

Join

What do you do to join Rust Solo PvE - Local?

Check: join. Open Rust, press F1, then enter client.connect 108.237.91.203:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp4
Max players The server holds 4 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Build 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.