Rust | Sucata não dá em Arvore
Online 45.146.81.131:28022 checked 10m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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, measured since 30 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Li4Rank
daily · 1 is bestTop 18% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 20 hours in.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on Rust | Sucata não dá em Arvore?
At their busiest, its recent wipes averaged 3 players. 20 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 7 it was below half in the wipes that did not hold.
What is the wipe schedule on Rust | Sucata não dá em Arvore?
The record of Rust | Sucata não dá em Arvore's wipes is not yet long enough to show a rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 13 days ago.
Player counts
How busy is Rust | Sucata não dá em Arvore?
The current population of Rust | Sucata não dá em Arvore is 5, against 40 slots. Averaged over the past week: 1 players, peaking at 4. Look at 01:00 UTC for the last 48 hours: that hour averaged 4 players.
How does Rust | Sucata não dá em Arvore rank against other Rust servers?
Player hours over seven days put Rust | Sucata não dá em Arvore at #3,958, in the top 18% of ranked servers.
Rules and settings
Which map does Rust | Sucata não dá em Arvore run?
The map on Rust | Sucata não dá em Arvore is procedural, size 3,500 with seed 58421, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map.
What are the rules and settings on Rust | Sucata não dá em Arvore?
The name Rust | Sucata não dá em Arvore does not specify a gather rate. Groups can contain up to 8 players, the default in the game. The server runs survival, gather, build and raid in the standard game. You can fight other players and raid their bases. The server browser lists it as Modded: plugins or settings change the game. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, turned on.
Server details
Which version of Rust does Rust | Sucata não dá em Arvore run?
Rust network protocol 2635 and build 168909 is the build Rust | Sucata não dá em Arvore runs, on Linux. Steam updates your game for you, and the protocol has to match for you to join.
Is Rust | Sucata não dá em Arvore online, and how reliable is it?
The server is up at the moment: Rust | Sucata não dá em Arvore is online. About 5 days 22 hours ago is when it last restarted, by its own uptime figure. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. Rust Heatmap has had it on record since 30 September 2026.
Where is Rust | Sucata não dá em Arvore located?
Nothing about a region comes from Rust | Sucata não dá em Arvore. Rust Heatmap shows the location a server states. It does not look up the machine's location. 45.146.81.131:28022 is its address.
Does Rust | Sucata não dá em Arvore run smoothly?
It averaged 189 server fps over the last 48 hours, with a low of 58. Buildings, deployables and the rest of the world came to as much as 73,012 entities. The highest memory use was 3,958 MB. Lag, as players experience it, comes from low fps and a rising entity count.
Tags
Which Rust Heatmap lists and filters include Rust | Sucata não dá em Arvore?
These Rust Heatmap lists include Rust | Sucata não dá em Arvore: Modded Rust servers, by live population. Filtering the list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks brings it up.
What do the server tags on Rust | Sucata não dá em Arvore mean?
gmrust (Game mode): Rust survival, standard rules; mp40 (Max players): Slot count: 40; ts8 (Group limit): At most 8 per team: the default the game ships with; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): Build 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): A region code is not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Settings or plugins alter the game, which puts it under Modded are the tags Rust | Sucata não dá em Arvore publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
Connect
How do I join Rust | Sucata não dá em Arvore?
To join by console, open it with F1 in Rust and enter client.connect 45.146.81.131:28022. Or press Launch Rust on this page, which connects you through Steam.