Station EU-15506 · no signal
Brutal PvE II
Offline EU 216.106.188.124:7006 checked 38d ago
- Players now
- 2/ 25
- 8% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,506
- top 67% · #2525 in EU
- Last wipe
- 41d ago
- biweekly schedule
- Next wipe
- 8h
- Thu 29 Oct, 18:08 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 2of 25 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 67% of all ranked servers, top 83% in EU. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 18:08 UTC, in 8h. Its biweekly schedule tag · low confidence
- wipe-day peak
- 4players, last three wipes
Coming wipes
- 8hThu 29 Oct, 18:08 UTC
- 7d 9hThu 5 Nov, 19:00 UTCFW
- 14d 8hThu 12 Nov, 18:08 UTC
- 28d 8hThu 26 Nov, 18:08 UTC
- 35d 9hThu 3 Dec, 19:00 UTCFW
- 42d 8hThu 10 Dec, 18:08 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 24 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 17 Sep, 18:08 UTC41d ago | M0.6▲rising | 4 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on Brutal PvE II?
Brutal PvE II runs a procedural map of size 4,500 with seed 17982026, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on Brutal PvE II?
The name of Brutal PvE II gives no gather rate. The group limit is 8 players, the game's default. It plays in pve mode, no combat against other players. Plugins or settings alter the game here; the browser lists it as Modded. Carbon is the plugin framework it runs. Joining is limited to players who have Rust's premium status. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on Brutal PvE II?
No players are recorded on Brutal PvE II at this moment; it is offline, and the last sighting was 38 days 20 hours ago.
How does Brutal PvE II rank against other Rust servers?
The last seven days of player hours place Brutal PvE II at #15,506, in the top 67% of all ranked servers and #2,525 in Europe.
Operator and location
How reliably does Brutal PvE II stay online?
As recorded now, Brutal PvE II is not reachable, the last contact having been 38 days 20 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.
Where in the world is Brutal PvE II hosted?
In Europe Brutal PvE II lists itself, with the tag EU. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 216.106.188.124:7006.
What build of Rust does Brutal PvE II use?
Rust network protocol 2633 and build 164530 on Linux is what Brutal PvE II runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on Brutal PvE II?
4 players, on average, was the busiest crowd at its recent wipes. 24 hours after the latest wipe, the crowd peaked.
How often does Brutal PvE II wipe, and on which days?
The prediction follows its tag, because too few of Brutal PvE II's wipes are on record to confirm its schedule. The date of its next wipe is Thursday 29 October at 18:08 UTC. The present world dates from 41 days 15 hours. Every two weeks it wipes, according to the schedule in its tags.
Server tags
What do the server tags on Brutal PvE II mean?
Tags published by Brutal PvE II and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp25 (Max players): Slots: 25; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs164530 (Build): Game build: 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): A wipe comes every second week; ^p (PvE): There's no player combat; the world provides the threat; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here; ^q (Premium): Joining is limited to players who have Rust's premium status; EU (Europe): In the server browser it appears under Europe. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Brutal PvE II appear?
The Rust Server Trends lists that take in Brutal PvE II are: EU Rust servers, Modded Rust servers, tracked live and Rust PvE servers. These filters bring it up on the server list: Region: Europe; Type: Modded; Game mode: PvE and Premium; Server tag: Biweekly ^b, PvE ^p, Premium ^q, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks.
Join the server
How do you connect to Brutal PvE II?
To join, enter client.connect 216.106.188.124:7006 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. Joining is limited to players who have Rust's premium status.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.