On the class lists: C− (59), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average1peak 5
Rank#4,406top 20% · #750 in NA
Last wipe3d agomonthly schedule
Next wipe7d 7hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 1 of 50 on average. Plenty of space to grow.
Standingrank on player hours
80/ 100
B+
Holds a respectable place: #4,406 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
21/ 100
F
Needs to work on its frame rate: 12 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in uptime (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.
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 25 Oct. 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, top 40% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 7h.
The force wipe · high confidence
wipe-day peak5players, last three wipes
Coming wipes
7d 7hThu 5 Nov, 19:00 UTCFW
35d 7hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 25 Oct, 23:24 UTC3d ago
5
–
running
1
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
You'll see Azeroth - The Last Battle listed in North America, tagged NA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 66.51.96.68:28005.
How reliable is Azeroth - The Last Battle, and is it up?
Right now, Azeroth - The Last Battle is online. The uptime it reports puts the last restart at about 32 hours ago. It was up 99% of the time over the last 3 full days, 71 of 72 hours. It was first seen by Rust Server Score on 25 October 2026.
Does Azeroth - The Last Battle perform well?
The average over the last 48 hours was 12 server fps, and it never went below 5. Buildings, deployables and everything else in the world added up to as many as 72,011 entities. At its highest, it used 2,442 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is Azeroth - The Last Battle on?
You will find Azeroth - The Last Battle on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does Azeroth - The Last Battle wipe, and how often?
Azeroth - The Last Battle wipes with the force wipe and at no other time. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 3 days 12 hours have passed since this world was made. Its tags record that it wipes monthly.
What should you expect from wipe day on Azeroth - The Last Battle?
Recent wipes have peaked at 5 players on average. Peak numbers came 1 hours into the latest wipe.
Player count
Where does Azeroth - The Last Battle place in the wider field of Rust servers?
In North America, Azeroth - The Last Battle is #750, and overall it is #4,406 on player hours over the last seven days, in the top 20% of all ranked servers.
What does the population on Azeroth - The Last Battle look like?
With 50 slots available, Azeroth - The Last Battle currently has 0 players. The seven-day average is 1 players, with a peak of 5. Over the last 48 hours, the peak hour was 23:00 UTC, averaging 2 players.
Tags and filters
How should you read the tags on Azeroth - The Last Battle?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; 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): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): In the server browser it appears under North America are the tags Azeroth - The Last Battle publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature Azeroth - The Last Battle?
Rust Server Score lists that include Azeroth - The Last Battle: Modded Rust servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.
Rules and settings
What settings and rules apply on Azeroth - The Last Battle?
The name of Azeroth - The Last Battle gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Azeroth - The Last Battle?
Azeroth - The Last Battle runs a game-generated procedural map at size 3,500, seed 1. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto Azeroth - The Last Battle?
Enter client.connect 66.51.96.68:28005 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,^m,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
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
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
NA
North AmericaIn the server browser it appears under North America.
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 term to build on. Strongest in uptime (A+); population is the one to work on (F).