Westerwald PVE
5.39.17.35:28015Up, checked 6m agoMonitored since 13 Sep 2026
Health checks
from the latest readings- ReachableOn the Steam server list, checked 6m agoPassing
- Capacity0% of 5 slots in usePassing
- Queuenobody waitingPassing
- Performancerunning at 84 fpsPassing
- Fresh mapwiped 4d agoPassing
- Next wipetoo few wipes seen yetNo data
Activity
players each hour, last 48- Group limit
- 8, the default
- Wipe schedule
- not published
- Map
- Procedural Map · 5000
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- 1[EU] RustEZ Pure PvE | Low Decay | No Killing | No RaidingEU · groups of 8+ · monthly · 80 on average124 / 200
- 2[US] RustEZ Pure PvE | Low Decay | No Killing | No RaidingNA · groups of 8+ · monthly · 74 on average44 / 200
- 3Abyss|US|PVE|NOOB FRIENDLY|NO KILL NO RAIDNA · groups of 8+ · monthly · 65 on average40 / 200
- 4【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍EA · groups of 30+ · monthly · 35 on average40 / 200
- 5Stillwater Shores PVE | PVPNA · groups of 30+ · monthly · 28 on average16 / 100
- 6MadRust PVE - Get AchievementsNA · groups of 8+ · monthly · 28 on average30 / 50
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Rank
daily · 1 is bestTop 25% of all ranked servers. Ranked on player hours over the last seven days.
Performance
48 hours: hourly readings. 30 to 90 days: a point a day, measured since 17 Sep. Low fps and a climbing entity count mean lag.
Wipe calendar
1 day with a wipe in the last 16 weeksNot enough wipes seen yet to tell. Every server wipes at the monthly force wipe.
- wipe-day peak
- 2 players, last three wipes
The first 48 hours of its last wipes
-
4 Oct
Sun 11:55 UTC peak 2 · running
- 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
Server tags
What each tag it publishes means. Published as mp5,ptrak,$r?,v2634,^p,gmrust,cs166652,ts8.
gmrustGame mode Survival in the standard Rust style.mp5Max players 5 player slots.ts8Group limit Teams are capped at 8, which is the game default.v2634Protocol Your game must be on protocol 2634 to join.cs166652Build The game build is 166652.ptrakNetworking RakNet is the network layer, as standard for the game.$r?Region code A region code is not set.^pPvE The world is the danger, not other players.Flag meanings are Facepunch's.
Player data
What position does Westerwald PVE hold?
The seven-day player hours rank for Westerwald PVE is #5,928, in the top 25% of ranked servers.
What is the player count on Westerwald PVE?
With 5 slots, Westerwald PVE holds 0 players at present. In the past week, the average is 0 players and the peak is 2. Over the past 48 hours, the peak hour was 21:00 UTC, averaging 2 players.
Settings and rules
What map is used on Westerwald PVE?
Westerwald PVE uses a procedural map of size 5,000 with seed 50000, generated by the game. You can look at the map on RustMaps from this page, as the same size and seed give the same result.
What are the settings and rules for Westerwald PVE?
No gather rate appears in the name of Westerwald PVE. The game's default applies: no more than 8 players per group. It runs pve, no player-versus-player fighting. The server browser lists it under Community. The server has VAC, Valve's anti-cheat, active.
Wipe schedule
What happens on Westerwald PVE during wipe day?
The average busiest count over recent wipes was 2 players. Peak numbers on the latest wipe arrived 1 hours after it began.
When does Westerwald PVE wipe?
Too few wipes from Westerwald PVE are recorded to reveal a rhythm. The monthly force wipe applies to every Rust server. The next one is Thursday 5 November at 19:00 UTC. 4 days 5 hours is the age of the current world.
Server tags
What is the meaning of the tags on Westerwald PVE?
gmrust (Game mode): Survival in the standard Rust style; mp5 (Max players): 5 player slots; ts8 (Group limit): Teams are capped at 8, which is the game default; v2634 (Protocol): Your game must be on protocol 2634 to join; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet is the network layer, as standard for the game; $r? (Region code): A region code is not set; ^p (PvE): The world is the danger, not other players are the tags Westerwald PVE publishes; the game's server browser reads them. Shown at the top of this page are three more things from the tags: its players now, its queue and the time its world was made.
What lists and filters on Best Rust Servers hold Westerwald PVE?
Included in these Best Rust Servers lists is Westerwald PVE: Community servers, no training or build tags and Best Rust PvE servers. You will find it on the server list under: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more; Last wipe: In the last week.
About the server
What Rust version does Westerwald PVE run?
The Rust version on Westerwald PVE is network protocol 2634 and build 166652, running on Linux. Steam updates your game to the same protocol required for joining.
What is the location of the server Westerwald PVE?
There is no published region for Westerwald PVE. Best Rust Servers does not look up where the machine stands; it shows where a server says it is. 5.39.17.35:28015 is its address.
What is the performance like on Westerwald PVE?
In the last 48 hours, the server averaged 95 fps, with a minimum of 82. A maximum of 140,752 entities were present, comprising buildings, deployables and all else. The highest memory usage was 4,396 MB. Low fps and a growing entity count are the sources of lag for players.
What is the uptime and reliability of Westerwald PVE?
Westerwald PVE is online at the moment. Based on the uptime it reports, the last restart was roughly 4 days 3 hours ago. In the last 7 full days, 168 of 168 hours were online, an uptime of 100%. Best Rust Servers recorded its first appearance on 13 September 2026.
How to join
What are the steps to join Westerwald PVE?
Use Launch Rust on this page to open Rust through Steam and connect, or press F1 in Rust and enter client.connect 5.39.17.35:28015 in the console.