RUST METRICSFlight deck · live data
Data live Servers11,713 Players43,388 Populated3,068 Fresh wipes 3 h103 Scan5 min
‹ All servers76.13.163.82:28015
Online Full Queue Fresh wipe Wipe due No query

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

Online 76.13.163.82:28015 checked 10m ago

2x trio moddedoxide
COM 1 · connect

Server instruments

last reading Wed 23:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 100 SERVER FPS

Server fps

48 h low 38 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 47,164 ×1000

Entities

48 h range 43,636–70,059 · memory 2,271 MB
1239 ET SINCE RESTART 1D 05H

Uptime

1 days 5 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,349top 69%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Memory2,271MBat the last reading
REC 1

Players

AveragePeakWipe
0123402:0011:0020:0004:0013:0023:00Wiped Tue 27 Oct, 18:02 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
010020030040002:0011:0020:0004:0013:0023: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k18 Oct20 Oct22 Oct25 Oct27 Oct29 Oct

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

PLAN

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.1 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 18:02 UTC1d ago – – running 0
Sat 24 Oct, 16:00 UTC4d ago 0 – 3.1 days 0
Tue 20 Oct, 18:01 UTC8d ago 0 – 3.9 days 0
Sun 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.

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

No next wipe can be predicted for [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 31 hours ago the current world was made.

Tags

How should you read the tags on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts3 (Group limit): Team cap: 3; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO appear in Rust Metrics lists and filters?

On Rust Metrics, [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO sits in these lists: 2x Rust servers, checked live, Modded Rust servers, checked live and Trio servers, group limit 3. 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 3 days; Gather rate: 2x.

Occupancy

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

Player hours over seven days put [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO at #15,349, in the top 69% of all ranked servers. The trio group places it at #525.

How full does [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO get?

0 of 50 slots are filled on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO right now. Seven-day reading: 0 players on average.

Server

Where does [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO sit?

Check: location. No region tag comes from [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO, but the name points to South America. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 76.13.163.82:28015.

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 the build [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: 114 server fps on average across the last 48 hours. It never dropped below 38. Check: entities. The peak was 70,059, counting buildings, deployables and the rest of the world. Reading: 2,835 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.

How reliable is [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO, and is it online now?

Check: connection. [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO is online at this moment. By its reported uptime, the last restart was roughly 29 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 18 October 2026.

Settings and map

How is [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO configured, and what rules are in force?

Gather rate check: 2x. That comes from the name [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO. The group cap is 3 players, read as trio. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

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

From seed 910508, the game generates the procedural map on [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO. Its size is 3,095. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How do you connect to [BR/LATAM] BAGUNCINHA 2X | WIPE 27/10 | SOLO|DUO|TRIO?

Check: join. Open Rust, press F1, then enter client.connect 76.13.163.82:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://baguncinha.fun is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts3
Group limit Team cap: 3.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.