On the class lists: C+ (65), with population over 48 hours and no performance mark.
Players now1/ 502% full
7-day average0peak 6
Rank#4,437top 20%
Last wipe23h agoweekly schedule
Next wipe6d 0hWed 4 Nov, 14:22 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
80/ 100
B+
Holds a respectable place: #4,437 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: 133 server fps on average.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
100/ 100
A+
Climbing fast: up 9,932 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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 23 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 20% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
·······
W······
·······
···W··W
··W·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Wednesday 4 November, 14:22 UTC, in 6d 0h.
Its weekly schedule tag · low confidence
usual gap2.9 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak4players, last three wipes
crowd held50%else halves by day 5
Coming wipes
6d 0hWed 4 Nov, 14:22 UTC
7d 4hThu 5 Nov, 19:00 UTCFW
13d 0hWed 11 Nov, 14:22 UTC
20d 0hWed 18 Nov, 14:22 UTC
27d 0hWed 25 Nov, 14:22 UTC
34d 0hWed 2 Dec, 14:22 UTC
35d 4hThu 3 Dec, 19:00 UTCFW
41d 0hWed 9 Dec, 14:22 UTC
The first 48 hours of its last wipes
Sun 25 OctThu 22 OctThu 22 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 28 Oct, 14:22 UTC23h ago
–
–
running
0
Sun 25 Oct, 16:03 UTC3d ago
0
–
2.9 days
0
Thu 22 Oct, 21:18 UTC6d ago
6
✓ held half
2.8 days
0
Thu 22 Oct, 12:04 UTC7d ago
6
–
0.4 days
0
Mon 5 Oct, 04:46 UTC24d ago
0
–
17.3 days
0
Wed 23 Sep, 18:54 UTC35d ago
1
halved by day 5
11.4 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 | Ashes of Rust |x3 Loot | RaidBases | based in?
No region is published for | Ashes of Rust |x3 Loot | RaidBases |. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 65.109.115.186:20520.
Is | Ashes of Rust |x3 Loot | RaidBases | up, and how steady is its uptime?
Right now, | Ashes of Rust |x3 Loot | RaidBases | is online. The uptime it reports puts the last restart at about 21 hours ago. It was up 163 of 168 hours over the last 7 full days, which is 97% of the time. On 23 September 2026, Rust Server Score saw it for the first time.
Does | Ashes of Rust |x3 Loot | RaidBases | perform well?
The average over the last 48 hours was 133 server fps, and it never went below 15. Up to 97,175 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 3,538 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does | Ashes of Rust |x3 Loot | RaidBases | sit?
The server | Ashes of Rust |x3 Loot | RaidBases | 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 schedule
On what schedule does | Ashes of Rust |x3 Loot | RaidBases | reset?
Its tag sets the prediction, as the record holds too few of | Ashes of Rust |x3 Loot | RaidBases |'s wipes to confirm its schedule. Expect the next wipe on Wednesday 4 November at 14:22 UTC. The world it runs now was created 23 hours. The tags carry a weekly wipe schedule.
What should you expect from wipe day on | Ashes of Rust |x3 Loot | RaidBases |?
Recent wipes have peaked at 4 players on average. Peak numbers came 0 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 50% of its recent wipes. In the other wipes it slipped under half by day 5.
Player numbers
What position does | Ashes of Rust |x3 Loot | RaidBases | hold in the rankings?
In the top 20% of all ranked servers, | Ashes of Rust |x3 Loot | RaidBases | sits at #4,437 for player hours over the last seven days.
How many players does | Ashes of Rust |x3 Loot | RaidBases | usually have?
Right now, 1 players are on | Ashes of Rust |x3 Loot | RaidBases |, which has 50 slots. Averaging 0 players over seven days, it peaked at 6. The busiest time in the last 48 hours was 12:00 UTC, with an average of 0 players.
Tags and filters
What is meant by the tags on | Ashes of Rust |x3 Loot | RaidBases |?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; 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): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags | Ashes of Rust |x3 Loot | RaidBases | 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 | Ashes of Rust |x3 Loot | RaidBases |?
These Rust Server Score lists count | Ashes of Rust |x3 Loot | RaidBases | among them: 3x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours; Gather rate: 3x.
Server rules
Which rules does | Ashes of Rust |x3 Loot | RaidBases | enforce, and what are its settings?
The name of | Ashes of Rust |x3 Loot | RaidBases | points to a 3x gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map | Ashes of Rust |x3 Loot | RaidBases | uses?
A procedural map of size 4,000 and seed 1006198196, generated by the game, is what | Ashes of Rust |x3 Loot | RaidBases | runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
What is the way to join | Ashes of Rust |x3 Loot | RaidBases |?
Enter client.connect 65.109.115.186:20520 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^w,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
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
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^o
OxidePlugin framework: 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).