RUST METRICSFlight deck · live data
Data live Servers11,696 Players36,352 Populated2,907 Fresh wipes 3 h94 Scan5 min
‹ All servers45.146.81.131:28022
Online Full Queue Fresh wipe Wipe due No query

Rust | Sucata não dá em Arvore

Online 45.146.81.131:28022 checked 5m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Thu 01:00 UTC
0 10 20 30 40 PAX 0 /40

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 177 SERVER FPS

Server fps

48 h low 58 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 70,929 ×1000

Entities

48 h range 69,837–73,012 · memory 3,722 MB
1239 ET SINCE RESTART 6D 02H

Uptime

6 days 2 hours since its last restart, at the last reading
7-day average1peak 5
Rank#3,774top 17%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Memory3,722MB48 h peak 5 players
REC 1

Players

AveragePeak
0246803:0012:0021:0006:0015:0001:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040003:0012:0021:0006:0015:0001: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.

REC 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.

PLAN

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

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

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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on Rust | Sucata não dá em Arvore?

The busiest point of its recent wipes drew 3 players on average. After the latest wipe, numbers topped out at 20 hours. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell below half by day 7 when it didn't.

When does Rust | Sucata não dá em Arvore wipe?

The rhythm of Rust | Sucata não dá em Arvore's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 13 days 4 hours ago.

Tag meanings

How should you read the tags on Rust | Sucata não dá em Arvore?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): Slots: 40; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from Rust | Sucata não dá em Arvore. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Rust | Sucata não dá em Arvore appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Rust | Sucata não dá em Arvore: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

Where does Rust | Sucata não dá em Arvore sit in the rankings?

Ranking for Rust | Sucata não dá em Arvore: #3,774 on seven-day player hours, top 17% of all ranked servers.

How full does Rust | Sucata não dá em Arvore get?

0 of 40 slots are filled on Rust | Sucata não dá em Arvore right now. Seven-day check: 1 players on average. Peak reading: 5. The last 48 hours peaked at 23:00 UTC, averaging 5 players at that hour.

Server details

What location is Rust | Sucata não dá em Arvore hosted in?

No region comes from Rust | Sucata não dá em Arvore. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 45.146.81.131:28022.

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

Version check: Rust network protocol 2635 and build 168909 on Linux, run by Rust | Sucata não dá em Arvore. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for Rust | Sucata não dá em Arvore?

Reading: 191 server fps on average across the last 48 hours. It never dropped below 58. Check: entities. The peak was 73,012, counting buildings, deployables and the rest of the world. Reading: 3,958 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

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

Reading: online. Rust | Sucata não dá em Arvore answers right now. Reading: uptime. About 6 days 2 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 30 September 2026, recorded by Rust Metrics.

Settings and map

How is Rust | Sucata não dá em Arvore configured, and what rules are in force?

Check: gather rate. The name Rust | Sucata não dá em Arvore does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. 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. Check: anti-cheat. VAC, Valve's system, is on.

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

Check: map. Procedural, size 3,500, seed 58421, generated by the game on Rust | Sucata não dá em Arvore. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How can you get onto Rust | Sucata não dá em Arvore?

Press F1 in Rust and enter client.connect 45.146.81.131:28022. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp40
Max players Slots: 40.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock 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.