StatusLive Servers online11,635 Players30,176 Populated2,756 Wiped · 3 h70 Interval5 min Date29 OCT 2026

DWG RG-S3753Server sheetchecked 12m ago

Rust | Sucata não dá em Arvore

Online 45.146.81.131:28022 checked 12m ago

moddedoxide
Connect
Players now 0/ 40 0% full
7-day average1peak 5
Rank#3,753top 17%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Fig. 1

Players

AveragePeak
0246806:0015:0000:0008:0017:0003:00

Hourly average and peak, UTC.

Fig. 1Players on Rust | Sucata não dá em Arvore
Fig. 2

Server performance

010020030040006:0015:0000:0008:0017:0003:00

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

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k30 Sep6 Oct12 Oct17 Oct23 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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 gap14.1 daysbetween real wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 7

The first 48 hours of its last wipes

Thu 15 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 22:43 UTC13d ago 2 – running 0
Thu 1 Oct, 19:23 UTC FW27d ago 4 halved by day 7 14.1 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 log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 152 on average
41 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
123 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average
38 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
15 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
2 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
4 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

How reliable is Rust | Sucata não dá em Arvore, and is it online now?

Right now, Rust | Sucata não dá em Arvore is recorded as online. Counted from its reported uptime, the last restart was about 6 days 4 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 30 September 2026 is when Rust Graphs first saw it.

Is Rust | Sucata não dá em Arvore stable in the figures recorded?

The last 48 hours give an average of 189 server fps and a floor of 58. Counted at its highest: 73,012 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 3,958 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for Rust | Sucata não dá em Arvore?

There is no region published by Rust | Sucata não dá em Arvore. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 45.146.81.131:28022.

What Rust version is recorded for Rust | Sucata não dá em Arvore?

On Linux, Rust | Sucata não dá em Arvore runs Rust network protocol 2635 and build 168909. The same protocol is required for joining, and Steam updates your game to it.

Counts

What player count is recorded on Rust | Sucata não dá em Arvore?

0 of 40 slots on Rust | Sucata não dá em Arvore are taken at the latest refresh. Averaged across seven days, the player count is 1, with a peak of 5. Over the last 48 hours the busiest hour was 23:00 UTC, at an average of 5 players.

In the rankings, which position does Rust | Sucata não dá em Arvore hold?

Player hours over seven days place Rust | Sucata não dá em Arvore at #3,753, within the top 17% of ranked servers.

Wipe times

What happens on Rust | Sucata não dá em Arvore on the day of a wipe?

The recent wipes averaged a busiest count of 3 players. 20 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. By day 7 the crowd had fallen below half on the wipes where it did not hold.

What wipe schedule has been recorded for Rust | Sucata não dá em Arvore?

Rust | Sucata não dá em Arvore's rhythm cannot be told yet: too few of its wipes are on record. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. 13 days 6 hours ago the current world was made.

Rules and settings

Which rules and settings are recorded for Rust | Sucata não dá em Arvore?

The name of Rust | Sucata não dá em Arvore records no gather rate. The group limit is 8 players, the game's default. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.

On which map is Rust | Sucata não dá em Arvore played?

Seed 58421 and size 3,500 define the procedural map Rust | Sucata não dá em Arvore generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

Where does Rust | Sucata não dá em Arvore appear among the Rust Graphs lists and filters?

These Rust Graphs lists include Rust | Sucata não dá em Arvore: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meaning is attached to each tag on Rust | Sucata não dá em Arvore?

Tags published by Rust | Sucata não dá em Arvore, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp40 (Max players): The slot count is 40; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Connect

What is the way to connect to Rust | Sucata não dá em Arvore?

In Rust, press F1 and type client.connect 45.146.81.131:28022 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival, as Rust plays.
mp40
Max players The slot count is 40.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build 168909 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code field is empty.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed 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.

KeyTag string decoded