RUST METRICSFlight deck · live data
Data live Servers11,608 Players34,356 Populated2,818 Fresh wipes 3 h71 Scan5 min
‹ All servers78.29.13.139:28015
Online Full Queue Fresh wipe Wipe due No query

Vanilla PvE, but...

Online 78.29.13.139:28015 checked 8m ago

biweekly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 05:00 UTC
0 3 6 10 13 PAX 0 /13

Players now

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

Server fps

48 h low 79 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 136,179 ×1000

Entities

48 h range 129,394–137,863 · memory 2,878 MB
1239 ET SINCE RESTART 02:30

Uptime

2 h 30 min since its last restart, at the last reading
7-day average1peak 7
Rank#3,000top 13%
Last wipe13d agobiweekly schedule
Next wipe10hThu 29 Oct, 16:45 UTC
Memory2,878MB48 h peak 6 players
REC 1

Players

AveragePeak
0246807:0015:0023:0007:0021:0005:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020007:0015:0023:0007:0021:0005: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 21 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
15k10k15k20k21 Sep29 Sep6 Oct14 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 29 October, 16:45 UTC, in 10h. Its biweekly schedule tag · low confidence

usual gap12 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak10players, last three wipes
crowd held0%else halves by day 3.5

Coming wipes

  1. WPT 1Thu 29 Oct, 16:45 UTC10h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 12hFW
  3. WPT 3Thu 12 Nov, 16:45 UTC14d 10h
  4. WPT 4Thu 26 Nov, 16:45 UTC28d 10h
  5. WPT 5Thu 3 Dec, 19:00 UTC35d 12hFW
  6. WPT 6Thu 10 Dec, 16:45 UTC42d 10h

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctMon 21 Sep
02.557.510+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 11, 47 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 16:45 UTC13d ago 11 – running 0
Thu 1 Oct, 17:48 UTC FW27d ago 9+1 queue halved by day 4 14 days 0
Mon 21 Sep, 17:51 UTC37d ago 10 halved by day 3 10 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 Vanilla PvE, but...?

The busiest point of its recent wipes drew 10 players on average. Peak crowd on the latest wipe: 47 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 3.5 when it didn't.

What wipe timing does Vanilla PvE, but... follow?

Its tag guides the prediction: too few of Vanilla PvE, but...'s wipes are on record to confirm its schedule. On Thursday 29 October at 16:45 UTC its next wipe is due. The world in play was created 13 days 13 hours ago. A wipe schedule of every two weeks is published in its tags.

Tags

Which tags does Vanilla PvE, but... carry, and what do they mean?

Tags published by Vanilla PvE, but..., read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp13 (Max players): Slots: 13; ts8 (Group limit): The game default applies: teams of up to 8; 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): No region code is set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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 Vanilla PvE, but...?

These Rust Metrics lists carry Vanilla PvE, but...: Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Occupancy

What position does Vanilla PvE, but... hold among Rust servers?

Player hours over seven days put Vanilla PvE, but... at #3,000, in the top 13% of all ranked servers.

How full does Vanilla PvE, but... get?

Current headcount on Vanilla PvE, but...: 0 players, 13 slots available. Check: players over seven days. Average 1, peak 7. Check: 48-hour peak. 16:00 UTC, 5 players on average.

Server

Which location does Vanilla PvE, but... run from?

No region comes from Vanilla PvE, but.... Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 78.29.13.139:28015.

What Rust version is Vanilla PvE, but... on?

Reading: Vanilla PvE, but..., Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for Vanilla PvE, but...?

Over the last 48 hours the average was 118 server fps; the floor was 79. Reading: 137,863 entities at the highest. That covers buildings, deployables and everything else. Reading: 4,196 MB of memory at the highest. Expect lag when fps falls and entities climb.

Is Vanilla PvE, but... up, and how often does it stay up?

Reading: online. Vanilla PvE, but... answers right now. By its reported uptime, the last restart was roughly 2 hours ago. Reading: 96% uptime over the last 7 full days. It was up 162 of 168 hours. The first sighting on Rust Metrics was 21 September 2026.

Rules and settings

What settings and rules apply on Vanilla PvE, but...?

Reading the name gives no gather rate for Vanilla PvE, but.... The group cap is 8 players, which is the default in the game. pve, other players are not fought — that is the game mode. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Vanilla PvE, but...?

Check: map. Procedural, size 4,500, seed 27051999, generated by the game on Vanilla PvE, but.... The map repeats when size and seed match. Open it on RustMaps from this page.

Join

What do you do to join Vanilla PvE, but...?

To join: start Rust, press F1 and type client.connect 78.29.13.139:28015. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://discord.com/invite/khgSbbBgEW.

PLACARDS

Server tags

what each one means

Published as mp13,ptrak,$r?,v2635,^b,^p,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp13
Max players Slots: 13.
ts8
Group limit The game default applies: teams of up to 8.
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 No region code is set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the 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.