RUST METRICSFlight deck · live data
Data live Servers11,691 Players58,743 Populated3,438 Fresh wipes 3 h103 Scan5 min
‹ All servers136.158.40.123:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust Solo (Local)

Offline 136.158.40.123:28015 checked 17h ago

moddedoxide
COM 1 · connect

Server instruments

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

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 average1peak 1
Rank#5,568top 25%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Memory–48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75112:0015:0019:0022:0014:0017:00Wiped Mon 26 Oct, 22:12 UTCWIPE

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
15k10k15k20k28 Sep3 Oct14 Oct18 Oct23 Oct28 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.5 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 13 OctTue 13 OctMon 12 Oct
00.250.50.751+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
Mon 26 Oct, 22:12 UTC1d ago – – running 1
Tue 13 Oct, 12:45 UTC14d ago 1 held half 13.4 days 1
Tue 13 Oct, 04:57 UTC15d ago 1 – 0.3 days 0
Mon 12 Oct, 17:40 UTC15d ago 1 – 0.5 days 0

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 (Local)?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

When does Rust Solo (Local) wipe?

No next wipe can be predicted for Rust Solo (Local), which wipes at irregular times. 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 it runs now was made 36 hours ago.

Tags

How should you read the tags on Rust Solo (Local)?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from Rust Solo (Local). 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 Rust Solo (Local)?

These Rust Metrics lists carry Rust Solo (Local): 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; Last wipe: In the last 3 days.

Player count

What position does Rust Solo (Local) hold among Rust servers?

Player hours over seven days put Rust Solo (Local) at #5,568, in the top 25% of all ranked servers.

What is the population on Rust Solo (Local)?

Status for Rust Solo (Local): offline. Last seen 17 hours ago. Seven-day check: 1 players on average. Peak reading: 1. Check: 48-hour peak. 13:00 UTC, 1 players on average.

Server details

Where does Rust Solo (Local) sit?

Reading: location. Rust Solo (Local) gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 136.158.40.123:28015.

What Rust version is Rust Solo (Local) on?

Reading: Rust Solo (Local), Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

Is Rust Solo (Local) up, and how often does it stay up?

Rust Solo (Local) reports offline. The last reading came 17 hours ago. Uptime for the last 7 full days: 43 of 168 hours, or 26%. Reading: first seen 28 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does Rust Solo (Local) enforce, and what are its settings?

Check: gather rate. The name Rust Solo (Local) does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is off.

What map is Rust Solo (Local) on?

Check: map. Procedural, generated by the game, on Rust Solo (Local).

Join

How do you connect to Rust Solo (Local)?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.