On the class lists: C− (57), with population over 48 hours and no performance mark.
Players now2/ 405% full
7-day average1peak 4
Rank#3,672top 17%
Last wipe18d agono schedule published
Next wipe–no wipe 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,672 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 117 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
50/ 100
D
Holding steady: up 9 places this week.
A steady term.
Strongest in performance (A+); population is 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.
AveragePeak
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 16 Oct. 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
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
In what location does (Aura PvE) No Decay PvE sit?
You'll find no region listed by (Aura PvE) No Decay PvE. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 15.204.13.12:24660.
How reliable is (Aura PvE) No Decay PvE, and is it up?
The server is up: (Aura PvE) No Decay PvE is online now. According to its reported uptime, the last restart was about 8 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. On 16 October 2026, Rust Server Score saw it for the first time.
Is (Aura PvE) No Decay PvE smooth to play on?
The average over the last 48 hours was 117 server fps, and it never went below 1. Buildings, deployables and everything else in the world added up to as many as 66,388 entities. At its highest, it used 3,970 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is (Aura PvE) No Decay PvE on?
The server (Aura PvE) No Decay PvE is on Rust network protocol 2635 and build 168909 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does (Aura PvE) No Decay PvE wipe its map?
There are too few wipes on record for (Aura PvE) No Decay PvE to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 18 days 21 hours have passed since this world was made.
Player numbers
Where does (Aura PvE) No Decay PvE place in the wider field of Rust servers?
In the top 17% of all ranked servers, (Aura PvE) No Decay PvE sits at #3,672 for player hours over the last seven days.
How many players does (Aura PvE) No Decay PvE usually have?
With 40 slots available, (Aura PvE) No Decay PvE currently has 2 players. The seven-day average is 1 players, with a peak of 4. The busiest time in the last 48 hours was 05:00 UTC, with an average of 4 players.
Lists and filters
What is meant by the tags on (Aura PvE) No Decay PvE?
gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; 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; ^p (PvE): The danger comes from the world, not from other players; ^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 (Aura PvE) No Decay PvE publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature (Aura PvE) No Decay PvE?
These Rust Server Score lists count (Aura PvE) No Decay PvE among them: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
What settings and rules apply on (Aura PvE) No Decay PvE?
You will find no gather rate in the name of (Aura PvE) No Decay PvE. The group limit stays at the game's default of 8 players. pve is the mode here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
(Aura PvE) No Decay PvE runs which map?
A procedural map of size 3,000 and seed 646127621, generated by the game, is what (Aura PvE) No Decay PvE runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
What is the way to join (Aura PvE) No Decay PvE?
To connect, start Rust, press F1, and type client.connect 15.204.13.12:24660. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://aurapve.com/.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
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.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
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 steady term. Strongest in performance (A+); population is the one to work on (F).