On the class lists: D (48), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average1peak 5
Rank#3,726top 17%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 1 of 40 on average. Plenty of space to grow.
Standingrank on player hours
83/ 100
B+
Holds a respectable place: #3,726 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 191 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
56/ 100
C−
Moving up: up 417 places this week.
A fair term, with more to come.
Strongest in performance (A+); wipes are the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 17% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
···W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 2, 20 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 22:43 UTC13d ago
2
–
running
0
Thu 1 Oct, 19:23 UTCFW27d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is Rust | Sucata não dá em Arvore based in?
Rust | Sucata não dá em Arvore leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 45.146.81.131:28022.
How dependable is Rust | Sucata não dá em Arvore, and is it online at the moment?
You can join now: Rust | Sucata não dá em Arvore is online. About 6 days 18 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 30 September 2026.
Does Rust | Sucata não dá em Arvore perform well?
The average over the last 48 hours was 191 server fps, and it never went below 103. Up to 73,012 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 4,084 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is Rust | Sucata não dá em Arvore on?
Rust network protocol 2635 and build 168909 on Linux is what Rust | Sucata não dá em Arvore runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Rust | Sucata não dá em Arvore reset?
The record holds too few of Rust | Sucata não dá em Arvore's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 13 days 19 hours have passed since this world was made.
What happens on Rust | Sucata não dá em Arvore when wipe day arrives?
Recent wipes have peaked at 3 players on average. 20 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. Day 7 is when it sank below half in the wipes that did not hold.
Population
Where does Rust | Sucata não dá em Arvore place in the wider field of Rust servers?
Over the last seven days, Rust | Sucata não dá em Arvore has #3,726 for player hours, in the top 17% of all ranked servers.
How many players does Rust | Sucata não dá em Arvore usually have?
With 40 slots available, Rust | Sucata não dá em Arvore currently has 0 players. The seven-day average is 1 players, with a peak of 5. The busiest time in the last 48 hours was 23:00 UTC, with an average of 5 players.
Tags and filters
What is meant by the tags on Rust | Sucata não dá em Arvore?
gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Rust | Sucata não dá em Arvore publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Rust | Sucata não dá em Arvore?
Rust Server Score lists that include Rust | Sucata não dá em Arvore: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
How is Rust | Sucata não dá em Arvore set up, and what rules does it keep?
Nothing in the name of Rust | Sucata não dá em Arvore states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Rust | Sucata não dá em Arvore uses?
A procedural map of size 3,500 and seed 58421, generated by the game, is what Rust | Sucata não dá em Arvore runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join Rust | Sucata não dá em Arvore?
To connect, start Rust, press F1, and type client.connect 45.146.81.131:28022. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A fair term, with more to come. Strongest in performance (A+); wipes are the one to work on (F).