Rust StatisticsWorking papers on every public Rust server · 81,821 players now

Rust Br | Sucata não dá em Arvore

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 29d ago · 178.132.198.136:40122

Abstract

We describe the public Rust server Rust Br | Sucata não dá em Arvore, reached at 178.132.198.136:40122. It is offline at the last check, against a seven-day mean of 01. It ranks #12,438 of all servers, the top 52%. It last wiped 30d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now2/405% full
In the queue0no queue
Seven-day mean0peak –
Rank2#12,438top 52%
Last wipe30d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 52% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep30 Sep2 Oct4 Oct6 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap1.1 daysbetween real wipes
Wipe-day peak3players, last three wipes
Mon 28 SepSun 27 Sep
00.511.52+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 3, 1 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 28 Sep, 23:1730d ago 3 – running 0
Sun 27 Sep, 19:5531d ago 3 – 1.1 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address178.132.198.136:40122
Region–
Max players40
Group limit8, the default
Wipe schedule–
Last wipe28 Sep 2026, 23:17 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are rust community servers listed [2] and servers wiping soon [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rustoria.co - BR MainSA · groups of 16+ · weekly · 175 on average17/250
Rustoria.co - BR LongSA · groups of 12+ · monthly · 66 on average34/200
Rustoria.co - BR Main | JUST WIPED 29.10SA · no group limit · 65 on average62/100
[BR/LATAM] Rust Na Veia | MAX 4 |SA · groups of 8+ · weekly · 34 on average0/200
[wipe day] ARENA BR SOLO | VANILLA | LATAM |SA · groups of 8+ · biweekly · 32 on average2/200
[BR/LATAM] ORIGEMZ | VANILLA | SOLO/DUO/TRIO | WIPE 23/10SA · groups of 8+ · weekly · 25 on average1/300

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of Rust Br | Sucata não dá em Arvore?

Without a region tag from Rust Br | Sucata não dá em Arvore, its name still points to South America. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 178.132.198.136:40122.

A.2What is the online status and reliability of Rust Br | Sucata não dá em Arvore?

At the present moment, Rust Br | Sucata não dá em Arvore is offline; it was last seen 29 days 13 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. The first record of it by Rust Statistics dates to 13 September 2026.

A.3What is the Rust version for Rust Br | Sucata não dá em Arvore?

Rust Br | Sucata não dá em Arvore is running Rust network protocol 2633 and build 165217 on the Linux operating system. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4When are wipes carried out on Rust Br | Sucata não dá em Arvore?

There are not yet enough recorded wipes for Rust Br | Sucata não dá em Arvore to reveal its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The current world has been running for 30 days 15 hours.

A.5How would you describe wipe day on Rust Br | Sucata não dá em Arvore?

Across its recent wipes, the average peak population was 3 players. The peak on the latest wipe came 1 hours after it began.

Population

A.6What position does Rust Br | Sucata não dá em Arvore occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts Rust Br | Sucata não dá em Arvore at #12,438, within the top 52% of ranked servers.

A.7How would you characterise the player activity on Rust Br | Sucata não dá em Arvore?

The last recorded sighting of Rust Br | Sucata não dá em Arvore was 29 days 13 hours ago; it is offline now.

Tags and filters

A.8What is the meaning of the tags on Rust Br | Sucata não dá em Arvore?

The game's server browser reads gmrust (Game mode): This is survival as standard Rust plays; mp40 (Max players): The slot count is 40; ts8 (Group limit): 8 per team, the value the game sets by default; v2633 (Protocol): Your game must run protocol 2633 to connect; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset, which Rust Br | Sucata não dá em Arvore publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can Rust Br | Sucata não dá em Arvore be found among the Rust Statistics lists and filters?

Rust community servers, measured are the Rust Statistics lists that Rust Br | Sucata não dá em Arvore fits. You will find it on the server list filtered by: Region: South America; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

A.10Which settings and rules are in force on Rust Br | Sucata não dá em Arvore?

No gather rate appears in the name of Rust Br | Sucata não dá em Arvore. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gather, build and raid: the standard game. Fighting and raiding between players are both permitted. The server browser lists it under Community. The server has VAC on, Valve's anti-cheat.

A.11On which map does Rust Br | Sucata não dá em Arvore take place?

The game generates the map on Rust Br | Sucata não dá em Arvore; that format is procedural.

Connection

A.12What is the process for joining Rust Br | Sucata não dá em Arvore?

Enter client.connect 178.132.198.136:40122 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp40,ptrak,$r?,v2633,gmrust,cs165217,ts8.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp40Max players. The slot count is 40.
ts8Group limit. 8 per team, the value the game sets by default.
v2633Protocol. Your game must run protocol 2633 to connect.
cs165217Build. The game build is 165217.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. The region code is unset.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Rust community servers listed. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.