Rust Server TrendsSeismic network · station log
Recording Stations11,704 Players60,571 Active3,281 Wipes · 3 h172 48 h

Station XX-11716 · no signal

Rust Br | Sucata não dá em Arvore

Offline 178.132.198.131:31012 checked 31d ago

Connect
Players now
3/ 40
8% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#11,716
top 49%
Last wipe
32d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-11716 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
3of 40 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep23 Sep26 Sep29 Sep2 Oct5 Oct

Top 49% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

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.

usual gap
4.7 daysbetween real wipes
wipe-day peak
3players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sun 27 SepTue 22 Sep
01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 27 Sep, 16:09 UTC32d ago M0.3rising 3 – running 1
Tue 22 Sep, 22:21 UTC37d ago M0.3rising 3 held half 4.7 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - BR Main SA · groups of 16+ · weekly · 171 on average
791/ 800
Rustoria.co - BR Long SA · groups of 12+ · monthly · 64 on average
64/ 200
[LATAM] Sudamerica United | 29/10 Wipe SA · groups of 32+ · monthly · 35 on average
236/ 250
[BR/LATAM] Rust Na Veia | MAX 4 | SA · groups of 8+ · weekly · 34 on average
4/ 200
[wipe day] ARENA BR SOLO | VANILLA | LATAM | SA · groups of 8+ · biweekly · 28 on average
12/ 200
[BR/LATAM] ORIGEMZ | VANILLA | SOLO/DUO/TRIO | WIPE 23/10 SA · groups of 8+ · weekly · 25 on average
0/ 300
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Rust Br | Sucata não dá em Arvore?

The map on Rust Br | Sucata não dá em Arvore is procedural, produced by the game.

Which settings and rules apply on Rust Br | Sucata não dá em Arvore?

You will find no gather rate in the name of Rust Br | Sucata não dá em Arvore. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on Rust Br | Sucata não dá em Arvore?

A reading taken now finds Rust Br | Sucata não dá em Arvore offline; the most recent activity was 31 days 1 hours ago.

How does Rust Br | Sucata não dá em Arvore rank against other Rust servers?

The last seven days of player hours place Rust Br | Sucata não dá em Arvore at #11,716, in the top 49% of all ranked servers.

Server facts

How reliably does Rust Br | Sucata não dá em Arvore stay online?

Rust Br | Sucata não dá em Arvore is down at the moment; the last recorded contact was 31 days 1 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 15 September 2026 is when Rust Server Trends first recorded it.

Which region does Rust Br | Sucata não dá em Arvore run from?

The name of Rust Br | Sucata não dá em Arvore points to South America, even though it publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 178.132.198.131:31012.

What build of Rust does Rust Br | Sucata não dá em Arvore use?

Rust network protocol 2633 and build 165217 on Linux is what Rust Br | Sucata não dá em Arvore runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on Rust Br | Sucata não dá em Arvore?

3 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 2 hours after the wipe. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.

How often does Rust Br | Sucata não dá em Arvore wipe, and on which days?

On record so far are too few of Rust Br | Sucata não dá em Arvore's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 32 days 4 hours.

Lists and tags

What do the server tags on Rust Br | Sucata não dá em Arvore mean?

The game's server browser reads the tags Rust Br | Sucata não dá em Arvore publishes: gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): 40 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): The game build is 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Rust Br | Sucata não dá em Arvore appear?

These Rust Server Trends lists include Rust Br | Sucata não dá em Arvore: Rust community servers without the side modes. On the server list, the filters it matches are: Region: South America; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

What steps get you onto Rust Br | Sucata não dá em Arvore?

To join, enter client.connect 178.132.198.131:31012 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp40,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp40
Max players 40 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165217
Build The game build is 165217.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.