Working its way up from the back of the class: #15,477 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
24/ 100
F
Lost ground: down 8,173 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 best
RankRank in region
Top 68% of all ranked servers, top 84% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 29 October, 18:08 UTC, in 1d 22h.
Biweekly: 14 days after its last wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll see Brutal PvE II listed in Europe, tagged EU. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 178.63.43.239:7003.
Is Brutal PvE II up, and how steady is its uptime?
The server is down: Brutal PvE II is offline now, with the last sighting 36 days 15 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 20 September 2026.
What Rust version is Brutal PvE II on?
Rust network protocol 2633 and build 164530 on Linux is what Brutal PvE II runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Brutal PvE II wipe its map?
biweekly: 14 days after its last wipe gives the basis for estimating Brutal PvE II's next wipe. It is due to wipe next on Thursday 29 October at 18:08 UTC. 40 days 1 hours have passed since this world was made. Its tags give a wipe schedule of every two weeks.
Population
Where does Brutal PvE II place in the wider field of Rust servers?
Over the last seven days, Brutal PvE II has #15,477 for player hours, in the top 68% of all ranked servers and #2,535 in Europe.
What does the population on Brutal PvE II look like?
Brutal PvE II is offline at the moment; the last time it was seen was 36 days 15 hours ago.
Tags and filters
What do Brutal PvE II's tags stand for?
The game's browser takes its cue from the tags Brutal PvE II has set: gmrust (Game mode): Rust survival, played by the standard rules; mp25 (Max players): 25 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): The server wipes on a two-week cycle; ^p (PvE): The danger comes from the world, not from other players; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon; ^q (Premium): You need Rust's premium status to get in; EU (Europe): You will find it under Europe in the browser. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Brutal PvE II appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Brutal PvE II among them: European Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters 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.
Server rules
How is Brutal PvE II set up, and what rules does it keep?
Nothing in the name of Brutal PvE II states a gather rate. The default of 8 players applies as the group cap. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. You need Rust's premium status to get in. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Brutal PvE II uses?
A procedural map, generated by the game, is what Brutal PvE II runs.
Connecting
How do you get onto Brutal PvE II?
To connect, start Rust, press F1, and type client.connect 178.63.43.239:7003. Or click Launch Rust here, which launches Rust through Steam and joins you. You need Rust's premium status to get in.
Server tags
what each one means
Published asmp25,ptrak,$r?,v2633,^z,^y,^b,EU,^p,gmrust,cs164530,^q,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp25
Max players25 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is Carbon.
^q
PremiumYou need Rust's premium status to get in.
Region
EU
EuropeYou will find it under Europe in the browser.
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.
A term to build on. Even marks across the subjects, from F to F.