Fig. 1Players on [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIORG-S15330-01 · Sheet 1 of 11
Fig. 2
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.
Fig. 2FPS, entities and memoryRG-S15330-02 · Sheet 2 of 11
Fig. 3
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.
Fig. 3Rank on player hours, dailyRG-S15330-03 · Sheet 3 of 11
Schedule
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
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
ScheduleExpected wipesRG-S15330-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 22:19 UTC11d ago
1
–
running
0
Sat 17 Oct, 15:58 UTC11d ago
9
–
0.3 days
1
Tue 13 Oct, 18:01 UTC15d ago
21
halved by day 1
3.9 days
3
Sat 10 Oct, 15:59 UTC18d ago
28
halved by day 2
3.1 days
2
Tue 6 Oct, 17:59 UTC22d ago
26
held half
3.9 days
3
Sat 3 Oct, 17:59 UTC25d ago
10
held half
3 days
1
Thu 1 Oct, 18:40 UTCFW27d ago
7
–
2 days
0
Sat 26 Sep, 17:56 UTC32d ago
17
halved by day 3
5 days
1
Sat 19 Sep, 18:10 UTC39d ago
12
halved by day 2
7 days
1
Wed 16 Sep, 21:06 UTC42d 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.
Table 1Wipe logRG-S15330-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO online, and what uptime has been recorded?
The current state of [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO is offline, with the last sighting 11 days 11 hours ago. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. On 13 September 2026 is when Rust Graphs first saw it.
2.
What location is recorded for [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
South America is where the name of [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO points, with no region tag published. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 187.127.62.179:28015.
3.
On which Rust version is [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO running?
Rust network protocol 2634 and build 166494 on Linux: that is what [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO runs. The same protocol is required for joining, and Steam updates your game to it.
Population
4.
How many players are plotted on [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
The latest refresh records [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO as offline, last seen 11 days 11 hours ago.
5.
What rank has been recorded for [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
Over the last seven days, [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO records #15,330 for player hours: the top 70% of all ranked servers. #529 against other trio servers.
Schedules
6.
What is recorded on [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO on wipe day?
At their busiest, its recent wipes drew 10 players on average. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 50% of its recent wipes. By day 1.5 the crowd had fallen below half on the wipes where it did not hold.
7.
Which times and days are wipes plotted at on [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
No next wipe can be predicted for [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO: its wipes fall at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The current world has been in use since 11 days 13 hours ago.
Rules and settings
8.
What settings and rules apply on [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
The name records 2x gather for [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO. Groups: 3 players maximum (trio). survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.
9.
What is the map for [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
[BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO runs a procedural map of size 3,054 with seed 409262, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Filters
10.
On Rust Graphs, which lists and filters contain [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO?
These Rust Graphs lists include [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO: Servers with a 2x gather rate, Modded Rust servers and Trio Rust servers, plotted live. On the server list, these filters bring it up: 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.
11.
On [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO, what is meant by each tag?
Tags published by [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): The slot count is 100; ts3 (Group limit): The team limit is 3; v2634 (Protocol): Join only if your game is on protocol 2634; cs166494 (Build): Build: 166494; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Connect
12.
How is [BR/LATAM] BAGUNCINHA 2X | WIPE 17/10 | SOLO|DUO|TRIO joined?
Connect with client.connect 187.127.62.179:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. https://baguncinha.fun is its website.
NotesAnswered from the figuresRG-S15330-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs166494,ts3,^o^z
Game
gmrust
Game modeSurvival in standard Rust style.
mp100
Max playersThe slot count is 100.
ts3
Group limitThe team limit is 3.
v2634
ProtocolJoin only if your game is on protocol 2634.
cs166494
BuildBuild: 166494.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeNo region code is recorded.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is 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.
KeyTag string decodedRG-S15330-11 · Sheet 11 of 11
