Rust Data

rustdata.spaceservers5.39.17.35:28016.ipynb

Run all rust-data · live

‹ All servers

Online 5.39.17.35:28015 checked 10m ago

Westerwald PVE

pve

Connect

srv = rust.server("5.39.17.35:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/5 # 0% full
7-day average 0 # peak 1
rank #10,074 # top 45%
last wipe 25d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123418:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020018:0003:0012:0022:0007:0016: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 4 Oct, 11:55 UTC25d ago 2 NaN running 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.

display(srv.map, srv.info())

Map

5000 · seed 50000
Map of Westerwald PVE
map
Procedural Map
size
5000
seed
50000
Open on RustMaps

Server

srv.info()
address
5.39.17.35:28015
region
–
max players
5
group limit
8, the default
wipe schedule
–
last wipe
4 Oct 2026, 11:55 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
Dies ist ein reiner PVE Server das töten und Raiden anderer spieler ist verboten und wird mit einem bann bestraft

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ABYSS | PvE | US | Vanilla | Noob FriendlyNA · groups of 8+ · monthly · 55 on average49/200
1[EU] RustEZ Pure PvE | Low Decay | No Killing | No RaidingEU · groups of 8+ · monthly · 32 on average37/200
2[US] RustEZ Pure PvE | Low Decay | No Killing | No RaidingNA · groups of 8+ · monthly · 31 on average19/200
3[PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendlygroups of 8+ · monthly · 22 on average12/150
4【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍EA · groups of 30+ · monthly · 22 on average17/200
5JP RustPvE kokuu Server No kill No raid beeginnerEA · groups of 8+ · monthly · 15 on average10/200

Quick answers

From the figures on this page.

Population

What position does Westerwald PVE take in the server rankings?

Over the last seven days Westerwald PVE sits at #10,074 on player hours, in the top 45% of ranked servers.

How full does Westerwald PVE run?

The sample now reads 0 players for Westerwald PVE, out of 5 slots. Over the last seven days it averaged 0 players and peaked at 1.

Server data

How well does Westerwald PVE perform?

Averaged over 48 hours: 81 server fps, never under 45. Buildings, deployables and all else in the world took the count as high as 140,006 entities. Memory peaked at 5,168 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does Westerwald PVE run?

Rust network protocol 2635 and build 168909 on Linux is what Westerwald PVE runs. Steam updates your game for you, but the protocol must match to join.

Is Westerwald PVE up, and what does its uptime show?

Online is the state at the latest refresh for Westerwald PVE. The uptime it reports puts the last restart about 1 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.

Which location does Westerwald PVE run from?

No region is published by Westerwald PVE. Rust Data does not look up where the machine stands; it shows where a server says it is. 5.39.17.35:28015 is its address.

Rules, settings, map

Which settings and rules does Westerwald PVE run?

You will not find a gather rate in the string Westerwald PVE. Eight players per group: that is the game's default, and it applies here. Recorded as pve, player combat is not allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

What is the map on Westerwald PVE?

The game generates the map on Westerwald PVE: procedural, size 5,000, seed 50000. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does Westerwald PVE wipe, and how often?

A rhythm cannot be read from the wipes of Westerwald PVE on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 25 days 5 hours ago.

On Westerwald PVE, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 1 hours in.

Tags and filters

Which lists on Rust Data hold Westerwald PVE, and which filters?

The Rust Data lists that Westerwald PVE fits are: Rust community servers, unfiltered and Rust PvE servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.

How should you read the server tags on Westerwald PVE?

The game's server browser reads these tags from Westerwald PVE: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): 5 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^p (PvE): PvE: the world is the threat, not other players. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

What is the way into Westerwald PVE?

In Rust, F1 opens the console: type client.connect 5.39.17.35:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp5,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp5
Max players 5 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

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.

Rust Data 102,314 players 11,909 servers online