Working its way up from the back of the class: #15,771 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
28/ 100
F
Lost ground: down 6,998 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.
AveragePeakWipe
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
W······
·······
·······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.
usual gap4.3 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Mon 5 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 5 Oct, 17:38 UTC24d ago
1
–
running
0
Thu 1 Oct, 10:24 UTC28d ago
1
–
4.3 days
0
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
BRUTAL RUST | TESTER leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 179.61.132.160:22017.
Is BRUTAL RUST | TESTER up, and how steady is its uptime?
You cannot join now: BRUTAL RUST | TESTER is offline, last seen 18 days 9 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 24 September 2026.
On what Rust version does BRUTAL RUST | TESTER sit?
The server BRUTAL RUST | TESTER is on Rust network protocol 2634 and build 167398 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does BRUTAL RUST | TESTER wipe its map?
BRUTAL RUST | TESTER has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 24 days 9 hours.
What should you expect from wipe day on BRUTAL RUST | TESTER?
The average peak on its recent wipes was 1 players. 1 hours after the latest wipe began, the crowd hit its peak.
Population
Where does BRUTAL RUST | TESTER place in the wider field of Rust servers?
In the top 71% of all ranked servers, BRUTAL RUST | TESTER sits at #15,771 for player hours over the last seven days.
What does the population on BRUTAL RUST | TESTER look like?
It has been 18 days 9 hours since BRUTAL RUST | TESTER was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on BRUTAL RUST | TESTER?
The game's browser takes its cue from the tags BRUTAL RUST | TESTER has set: gmvanilla (Game mode): You play vanilla survival here; mp100 (Max players): The server holds 100 slots; ts10 (Group limit): Teams cap out at 10; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167398 (Build): This runs on build 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show BRUTAL RUST | TESTER?
Rust Server Score lists that include BRUTAL RUST | TESTER: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
What settings and rules apply on BRUTAL RUST | TESTER?
Nothing in the name of BRUTAL RUST | TESTER states a gather rate. The limit for a group is 10 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
Which map is in play on BRUTAL RUST | TESTER?
BRUTAL RUST | TESTER runs a game-generated procedural map at size 4,000, seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Wiped 5 days ago.
How to join
What is the way to join BRUTAL RUST | TESTER?
To connect, start Rust, press F1, and type client.connect 179.61.132.160:22017. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://brutalgaming.es.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmvanilla,cs167398,ts10,^z,^y
Game
gmvanilla
Game modeYou play vanilla survival here.
mp100
Max playersThe server holds 100 slots.
ts10
Group limitTeams cap out at 10.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework here.
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.