Rust Server IndexCard catalogue of Rust servers

Holdings11,829 servers89,289 players14 fresh wipes

Call no.2X15373 On the shelf · online

[BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO

Online 76.13.163.82:28015 checked 2h ago

Subjects 1. 2x 2. trio 3. modded4. oxide
Players now
0/ 50
0% full
7-day average
0
peak –
Rank
#15,373
top 69%
Last wipeWiped27 OCT2026 · 1d 1h ago
1d ago · no schedule published
Next wipe
–
no rhythm it keeps
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeakWipe
0123420:0005:0014:0023:0008:0017:00Wiped Tue 27 Oct, 18:02 UTCWIPE

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

Server fpsWipe
010020030040020:0005:0014:0023:0008:0017:00Wiped Tue 27 Oct, 18:02 UTCWIPE

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 18 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
15k10k15k20k18 Oct20 Oct22 Oct24 Oct26 Oct28 Oct

Top 69% of all ranked servers, and #525 of the trio servers (top 84%). Ranked on player hours over the last seven days.

Record sheet D · loan terms

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 gap
3.1 daysbetween real wipes
on rhythm
33%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
0%else halves by day 1

The first 48 hours of its last wipes

Sat 24 OctTue 20 OctSun 18 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
27 OCT 2026Tue 27 Oct, 18:02 UTC1d ago
– – running 0
24 OCT 2026Sat 24 Oct, 16:00 UTC4d ago
0 – 3.1 days 0
20 OCT 2026Tue 20 Oct, 18:01 UTC8d ago
0 – 3.9 days 0
18 OCT 2026Sun 18 Oct, 13:40 UTC10d ago
3 halved by day 1 2.2 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

SA2X
[LATAM] SOLO NOOB X2 Solo/Duo/Trio | 27/10 WipeSA · trio · 2x · weekly · 64 on average
70/ 100
SA2X
[BR/LATAM] EXTREME 2X | SOLO/DUO/TRIO | WIPE FULL 25/10SA · trio · 2x · weekly · 46 on average
4/ 100
SA2X
[BR/LATAM] GUERRA FRIA 2X TRIO 25/10 [vK.gg]SA · trio · 2x · weekly · 15 on average
0/ 150
SA2X
[BR/LATAM] TERRA HOSTIL 2X | SOLO/ DUO/ TRIO |SA · trio · 2x · weekly · 11 on average
4/ 200
SA2X 1/ 100
SA2X
[BR/LATAM] COMPLEXO 2X - SOLO/DUO/TRIO | WIPE 25/10SA · trio · 2x · weekly · 1 on average
0/ 100
Reference desk

Quick answers

From the figures on this page.

Settings and map

Where can you read the rules and settings that apply on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

Filed under gather rates: 2x, as the name of [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO states. A maximum of 3 players per group applies (trio). The server runs survival, gather, build and raid: the standard game. Fighting and raiding other players is permitted. The server browser lists it under Modded; plugins or settings alter the game. Filed under plugins: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map is in use on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

[BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO runs a procedural map of size 3,095 with seed 910508, generated by the game. The map can be seen on RustMaps from this page, because the same size and seed give the same map.

Lists and filters

Where does [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO appear among the Rust Server Index lists and filters?

Filed under these Rust Server Index lists is [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO: Rust servers filed under 2x gather rate, Modded Rust servers, filed by play style and Trio servers, filed under group limit. Filed under these filters on the server list: Region: South America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Trio; Last wipe: In the last 3 days; Gather rate: 2x.

What is meant by the tags on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

Filed under these tags, as published by [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO and read by the game's server browser: gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): Player cap: 50; ts3 (Group limit): The team ceiling is 3; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): It runs build 168909; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): The region code field is left empty; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or changed settings put this under Modded. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.

Wipe schedule

How does a wipe day run on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

The average peak across its recent wipes is 1 players. The latest wipe peaked 0 hours in. The crowd held above half the peak until the next wipe in 0% of its recent wipes. In the other cases, numbers dropped below half by day 1.

Which wipe timetable does [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO follow?

No next wipe can be predicted for [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO: its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The world it runs now was made 25 hours.

Population

What position does [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO hold among Rust servers?

On player hours over seven days, [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO takes #15,373, within the top 69% of ranked servers. Among servers in the trio group, the rank is #525.

What does the player count on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO look like?

[BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO is currently showing 0 players on 50 slots. Averaged over the last seven days, the count is 0 players.

Server facts

What Rust version is [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO on?

Rust network protocol 2635 and build 168909, on Linux, is what [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO runs. Steam keeps your game updated, but the protocol must match for you to join.

What is the uptime and current status of [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

You will find [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO online as of now. The uptime it reports puts the last restart at about 22 hours ago. Of the last 7 full days, 168 of 168 hours were up, 100% of the time. On 18 October 2026 it was first seen by Rust Server Index.

Is the performance on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO good?

The last 48 hours give an average of 109 server fps and a floor of 38. The entity count reached 70,059, covering buildings, deployables and all else in the world. Memory use reached as much as 2,835 MB. What players feel as lag is low fps together with a rising entity count.

What is the location of [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

No region tag is published by [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO; the name it carries points to South America. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 76.13.163.82:28015.

Connecting

What is the way onto [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

If you would rather use the console, press F1 in Rust and enter client.connect 76.13.163.82:28015. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you. https://baguncinha.fun is where its website lives.

Subject headings explained

Server tags

What each one means.

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts3,^o^z

Game

gmrust
Game mode Survival on standard Rust rules.
mp50
Max players Player cap: 50.
ts3
Group limit The team ceiling is 3.
v2635
Protocol The protocol is 2635; older or newer clients cannot join.
cs168909
Build It runs build 168909.
ptrak
Networking Networking runs on RakNet, the game's default layer.
$r?
Region code The region code field is left empty.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded Plugins or changed settings put this under 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.