LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 46% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · 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.
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
The current map
Sunday 4 October 2026, 11:55 UTC
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.
The average peak across its recent wipes is 2 players. The crowd on the latest wipe peaked 1 hours in.
Westerwald PVE's wipe history is too thin on record to show a rhythm. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. This world dates from 24 days 18 hours.
These are the Rust Live Stats lists Westerwald PVE fits: Live Rust community servers and Rust PvE servers, live now. Under the filters Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more it appears on the server list.
gmrust (Game mode): Survival here follows standard Rust; mp5 (Max players): The slot count is 5; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): Build: 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): The server sets no region code; ^p (PvE): The world is the danger here; players do not fight each other: that is the tag list Westerwald PVE publishes for the game's server browser. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Live now: 0 players on Westerwald PVE, out of 5 slots. The seven-day average is 0 players, with a peak of 1.
On player hours for the past seven days, Westerwald PVE sits at #10,159, inside the top 46% of ranked servers.
No gather rate appears in the name Westerwald PVE. No custom limit is set, so groups hold the default 8 players. It runs pve, no fighting other players. Community is its browser category. Anti-cheat: VAC from Valve is enabled.
Size 5,000, seed 50000: that is the procedural map the game generates for Westerwald PVE. RustMaps shows it from this page, since equal size and seed give an equal map.
Nothing on Westerwald PVE states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 5.39.17.35:28015 is its address.
The average server fps was 81 over the last 48 hours; the lowest was 45. It supported up to 140,068 entities, covering buildings, deployables and all other objects. Up to 5,168 MB of memory was used. Players experience lag when fps is low and the entity count climbs.
The setup on Westerwald PVE is Rust network protocol 2635 and build 168909 with Linux. Steam updates it for you, but your game needs the same protocol to join.
Westerwald PVE is up and running at this moment. Based on the uptime it reports, the last restart was about 2 days 13 hours ago. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. Rust Live Stats has tracked it since 13 September 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 5.39.17.35:28015.