Working its way up from the back of the class: #15,330 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
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
5/ 100
F
Lost ground: down 13,894 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (D); momentum is the one to work on (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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers, and #529 of the trio servers (top 84%). Ranked on player hours over the last seven days.
Attendance: the wipe record
9 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W··W·
·····W·
···F·W·
·W···W·
·W···W·
·······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3.5 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak10players, last three wipes
crowd held50%else halves by day 1.5
The first 48 hours of its last wipes
Sat 17 OctSat 17 OctTue 13 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 22:19 UTC12d ago
1
–
running
0
Sat 17 Oct, 15:58 UTC12d ago
9
–
0.3 days
1
Tue 13 Oct, 18:01 UTC16d ago
21
halved by day 1
3.9 days
3
Sat 10 Oct, 15:59 UTC19d ago
28
halved by day 2
3.1 days
2
Tue 6 Oct, 17:59 UTC23d ago
26
✓ held half
3.9 days
3
Sat 3 Oct, 17:59 UTC26d ago
10
✓ held half
3 days
1
Thu 1 Oct, 18:40 UTCFW28d ago
7
–
2 days
0
Sat 26 Sep, 17:56 UTC33d ago
17
halved by day 3
5 days
1
Sat 19 Sep, 18:10 UTC40d ago
12
halved by day 2
7 days
1
Wed 16 Sep, 21:06 UTC43d ago
2
✓ held half
2.9 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
Where in the world is [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
You won't find a region tag on [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO, but its name indicates South America. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 187.127.62.179:28015.
Is [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO up, and how steady is its uptime?
The server is down: [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO is offline now, with the last sighting 12 days 1 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
On what Rust version does [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO sit?
You will find [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO on Rust network protocol 2634 and build 166494, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO wipe, and how often?
No next wipe can be predicted for [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 12 days 4 hours.
What happens on [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO when wipe day arrives?
Across its recent wipes, the busiest moments averaged 10 players. 0 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 50% of its recent wipes. In the other wipes it slipped under half by day 1.5.
Player count
Where does [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO place in the wider field of Rust servers?
In the top 70% of all ranked servers, [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO sits at #15,330 for player hours over the last seven days. In the trio group, it ranks #529.
Is [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO a busy server?
[BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO is offline at the moment; the last time it was seen was 12 days 1 hours ago.
Tags
What is meant by the tags on [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
You'll see [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; ts3 (Group limit): No team may go above 3; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): The game build is 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
These Rust Server Score lists count [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO among them: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. These filters bring it up on the server list: Region: South America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Trio; Last wipe: In the last 2 weeks; Gather rate: 2x.
Rules and settings
What settings and rules apply on [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
The name of [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO points to a 2x gather rate. You can have up to 3 players in a group (trio). You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO uses?
[BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO runs a game-generated procedural map at size 3,054, seed 409262. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
Enter client.connect 187.127.62.179:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://baguncinha.fun.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs166494,ts3,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
ts3
Group limitNo team may go above 3.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThe game build is 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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. Strongest in wipe hold (D); momentum is the one to work on (F).