Rust Server TrendsSeismic network · station log
Recording Stations11,793 Players79,700 Active3,567 Wipes · 3 h247 48 h

Station XX-15541 · no signal

Solo PVE

Offline 107.136.237.168:28015 checked 21d ago

moddedcarbonpve
Connect
Players now
1/ 2
50% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,541
top 70%
Last wipe
21d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15541 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 2 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 Oct

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

Expected events

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.

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 8 Oct, 16:20 UTC21d ago M0.0rising 1 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 252 on average
263/ 2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 243 on average
236/ 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 105 on average
83/ 200
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 59 on average
17/ 200
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl groups of 30+ · monthly · 54 on average
63/ 300
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 49 on average
0/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Solo PVE?

The map on Solo PVE is procedural, produced by the game.

Which settings and rules apply on Solo PVE?

The name of Solo PVE gives no gather rate. At the game's default, groups can have up to 8 players. In pve mode, no combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. Anti-cheat is on: VAC, from Valve.

Population

How many players are recorded on Solo PVE right now?

Solo PVE is not responding at this moment and is offline, last seen 21 days ago.

How does Solo PVE rank against other Rust servers?

On player hours for the past week, Solo PVE sits at #15,541, which puts it inside the top 70% of every ranked server.

Server facts

How reliably does Solo PVE stay online?

Solo PVE is down at the moment; the last recorded contact was 21 days ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 8 October 2026 is when Rust Server Trends first recorded it.

Where in the world is Solo PVE hosted?

A region is not published by Solo PVE. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 107.136.237.168:28015 is the address it uses.

What build of Rust does Solo PVE use?

Solo PVE is running Rust network protocol 2634 and build 167231 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Solo PVE?

1 players, on average, was the busiest crowd at its recent wipes. 2 hours into the latest wipe, the crowd reached its peak.

On what timetable does Solo PVE run its wipes?

On record so far are too few of Solo PVE's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 21 days 1 hours.

Lists and tags

What do the server tags on Solo PVE mean?

These are the tags Solo PVE publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp2 (Max players): The server has 2 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167231 (Build): It runs game build 167231; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^p (PvE): You won't fight other players here; the world is what threatens you; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Solo PVE appear?

These Rust Server Trends lists include Solo PVE: Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.

How to join

What steps get you onto Solo PVE?

To join, enter client.connect 107.136.237.168:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,^z,^y,^p,gmrust,cs167231,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp2
Max players The server has 2 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167231
Build It runs game build 167231.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Gameplay

^p
PvE You won't fight other players here; the world is what threatens you.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon Carbon is the plugin framework running here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.