Station XX-15338 · no signal
Brutal PVE III
Offline 86.149.190.162:28015 checked 12h ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,338
- top 69%
- Last wipe
- 25d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 16.9 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 3 Oct, 16:55 UTC25d ago | M0.0■steady | 0 | – | – | running | 0 |
| Wed 16 Sep, 19:35 UTC42d ago | M0.0▲rising | 1 | held half | 16.9 days | 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 pageRules and settings
Which map is running on Brutal PVE III?
Brutal PVE III uses a procedural map, which the game generates.
Which settings and rules apply on Brutal PVE III?
No gather rate appears in the name of Brutal PVE III. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on Brutal PVE III right now?
Brutal PVE III is not responding at this moment and is offline, last seen 12 hours ago. The population averaged 0 players over the past week.
How does Brutal PVE III rank against other Rust servers?
Over the last seven days, Brutal PVE III recorded enough player hours to reach #15,338 worldwide, placing it in the top 69% of all ranked servers.
Operator and location
How reliably does Brutal PVE III stay online?
No contact with Brutal PVE III right now, and the last recorded contact was 12 hours ago. 2 of 168 hours in the last 7 full days were up time, 1% of the total. Its earliest appearance in the records of Rust Server Trends dates to 15 September 2026.
Where in the world is Brutal PVE III hosted?
No region is published by Brutal PVE III. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 86.149.190.162:28015 is the address it uses.
What build of Rust does Brutal PVE III use?
On Windows, Brutal PVE III runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on Brutal PVE III?
On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
How often does Brutal PVE III wipe, and on which days?
On record so far are too few of Brutal PVE III's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 25 days 15 hours.
Lists and tags
What do the server tags on Brutal PVE III mean?
These are the tags Brutal PVE III publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. 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 III appear?
You will find Brutal PVE III on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How to join
How do you connect to Brutal PVE III?
To join, enter client.connect 86.149.190.162:28015 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.
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.