RUST METRICSFlight deck · live data
Data live Servers11,670 Players57,098 Populated3,402 Fresh wipes 3 h100 Scan5 min
‹ All servers67.60.51.136:28015
Online Full Queue Fresh wipe Wipe due No query

WD-41 | Roleplay | PvE

Online 67.60.51.136:28015 checked 10m ago

moddedcarbonpve
COM 1 · connect

Server instruments

last reading Wed 09:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

48 h low 78 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 72,358 ×1000

Entities

48 h range 72,358–93,765 · memory 1,969 MB
1239 ET SINCE RESTART 00:03

Uptime

0 h 3 min since its last restart, at the last reading
7-day average1peak 2
Rank#5,221top 23%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Memory1,969MB48 h peak 2 players
REC 1

Players

AveragePeakWipe
00.511.5211:0021:0006:0015:0000:0009:00Wiped Mon 26 Oct, 21:39 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
010020030040011:0021:0006:0015:0000:0009:00Wiped Mon 26 Oct, 21:39 UTCWIPE

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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct9 Oct13 Oct18 Oct22 Oct28 Oct

Top 23% 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 gap9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 5

The first 48 hours of its last wipes

Sun 25 OctThu 8 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 21:39 UTC1d ago – – running 1
Sun 25 Oct, 22:20 UTC2d ago 2 – 1 days 0
Thu 8 Oct, 22:36 UTC19d ago 2 halved by day 5 17 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 happens on WD-41 | Roleplay | PvE when wipe day comes?

An average of 2 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 26 hours. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. When it didn't hold, by day 5 it fell below half.

How often does WD-41 | Roleplay | PvE wipe, and when?

No next wipe can be predicted for WD-41 | Roleplay | PvE, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 36 hours ago.

Lists and filters

Which tags does WD-41 | Roleplay | PvE carry, and what do they mean?

These are the tags WD-41 | Roleplay | PvE publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts128 (Group limit): Team cap: 128; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^r (Roleplay): Check: mode. Roleplay; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Check: framework. Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show WD-41 | Roleplay | PvE?

On Rust Metrics, WD-41 | Roleplay | PvE sits in these lists: Modded Rust servers, checked live, Rust PvE servers and Rust roleplay servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Roleplay ^r, Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

Population

Where does WD-41 | Roleplay | PvE sit in the rankings?

Ranking for WD-41 | Roleplay | PvE: #5,221 on seven-day player hours, top 23% of all ranked servers.

How full does WD-41 | Roleplay | PvE get?

0 of 100 slots are filled on WD-41 | Roleplay | PvE right now. Check: players over seven days. Average 1, peak 2. Check: 48-hour peak. 00:00 UTC, 2 players on average.

Server

Which location does WD-41 | Roleplay | PvE run from?

No region comes from WD-41 | Roleplay | PvE. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 67.60.51.136:28015.

What Rust version is WD-41 | Roleplay | PvE on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by WD-41 | Roleplay | PvE. Check: protocol. To join, your game must match; Steam handles the update.

How does WD-41 | Roleplay | PvE perform?

Over the last 48 hours the average was 114 server fps; the floor was 78. Check: entities. The peak was 93,765, counting buildings, deployables and the rest of the world. Reading: 3,090 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.

Is WD-41 | Roleplay | PvE up, and how often does it stay up?

WD-41 | Roleplay | PvE reports online. Status: normal. Reading: uptime. About 3 minutes ago it restarted, on its own count. Uptime for the last 7 full days: 49 of 168 hours, or 29%. The first sighting on Rust Metrics was 4 October 2026.

Map and rules

What rules does WD-41 | Roleplay | PvE enforce, and what are its settings?

Check: gather rate. The name WD-41 | Roleplay | PvE does not state one. Check: group limit. Up to 128 players. Mode check gives roleplay; roleplay rules, jobs and towns. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is WD-41 | Roleplay | PvE on?

Size 4,000 and seed 1776: the game generates the procedural map on WD-41 | Roleplay | PvE from them. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

What do you do to join WD-41 | Roleplay | PvE?

To join: start Rust, press F1 and type client.connect 67.60.51.136:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^z,^y,^r,^p,gmrust,cs168909,ts128

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts128
Group limit Team cap: 128.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Gameplay

^r
Roleplay Check: mode. Roleplay.
^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Check: framework. Carbon.

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.