RUST METRICSFlight deck · live data
Data live Servers11,837 Players92,814 Populated3,817 Fresh wipes 3 h496 Scan5 min
‹ All servers15.235.181.126:28020
Online Full Queue Fresh wipe Wipe due No query

[SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23

Online 15.235.181.126:28020 checked 9m ago

2x oxide
COM 1 · connect

Server instruments

last reading Thu 19:00 UTC
0 15 30 45 60 PAX 1 /60

Players now

2% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 80 SERVER FPS

Server fps

48 h low 58 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 75,388 ×1000

Entities

48 h range 75,208–78,686 · memory 2,704 MB
1239 ET SINCE RESTART 18:30

Uptime

18 h 30 min since its last restart, at the last reading
7-day average3peak 10
Rank#1,898top 9%
Last wipe6d agono schedule published
Next wipe–no rhythm it keeps
Memory2,704MB48 h peak 9 players
REC 1

Players

AveragePeak
02.557.51022:0007:0016:0001:0010:0019:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020022:0007:0016:0001:0010:0019:00

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 9% 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 gap7 daysbetween real wipes
on rhythm60%of its recent wipes
wipe-day peak7players, last three wipes
crowd held20%else halves by day 6

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctMon 5 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 9, 41 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 12:29 UTC6d ago 9 – running 0
Fri 16 Oct, 12:29 UTC13d ago 7 halved by day 6 7 days 0
Mon 5 Oct, 12:50 UTC24d ago 6 halved by day 6 11 days 2
Thu 1 Oct, 18:13 UTC FW28d ago 10 held half 3.8 days 3
Thu 24 Sep, 12:27 UTC35d ago 13 halved by day 4 7.2 days 0
Thu 17 Sep, 12:35 UTC42d ago 9 halved by day 6 7 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

Wipe timing

What happens on [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 when wipe day comes?

The busiest point of its recent wipes drew 7 players on average. After the latest wipe, numbers topped out at 41 hours. Above half that peak the crowd stayed until the next wipe in 20% of recent wipes. It fell below half by day 6 when it didn't.

What wipe timing does [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 follow?

There is no next wipe to predict: [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 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 6 days 8 hours ago.

Tag meanings

How should you read the tags on [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23?

These are the tags [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp60 (Max players): 60 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod). Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23: 2x Rust servers, checked live and Rust community servers: live readings. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 2x.

Player count

Where does [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 sit in the rankings?

Player hours over seven days put [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 at #1,898, in the top 9% of all ranked servers.

What is the population on [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23?

Current headcount on [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23: 1 players, 60 slots available. Check: players over seven days. Average 3, peak 10. Check: 48-hour peak. 13:00 UTC, 7 players on average.

Operator and location

What location is [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 hosted in?

Reading: location. Nothing in the tags, but the name of [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 15.235.181.126:28020.

What Rust version is [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 on?

Rust network protocol 2635 and build 168909 on Linux is the build [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 runs. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23?

Check: fps. Average 91 server fps over the last 48 hours, low of 58. Within range. Peak entity count: 78,686. Buildings, deployables and all else included. Memory peak: 3,483 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23, and is it online now?

Check: connection. [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 is online at this moment. Reading: uptime. About 18 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

How is [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 configured, and what rules are in force?

The name carries the rate: 2x gather on [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23?

Size 3,300 and seed 1337: the game generates the procedural map on [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Map name, as listed: Custom Map.

Join

How can you get onto [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23?

Check: join. Open Rust, press F1, then enter client.connect 15.235.181.126:28020. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://www.lonesurvivor.online/ is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp60
Max players 60 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).

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.