RUST METRICSFlight deck · live data
Data live Servers11,826 Players80,135 Populated3,731 Fresh wipes 3 h265 Scan5 min
‹ All servers66.51.96.68:28005
Online Full Queue Fresh wipe Wipe due No query

Azeroth - The Last Battle

Online NA 66.51.96.68:28005 checked 12m ago

monthly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 13:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 5 SERVER FPS

Server fps

48 h low 5 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 71,684 ×1000

Entities

48 h range 68,620–72,011 · memory 2,029 MB
1239 ET SINCE RESTART 1D 11H

Uptime

1 days 11 hours since its last restart, at the last reading
7-day average1peak 5
Rank#4,401top 20% · #749 in NA
Last wipe3d agomonthly schedule
Next wipe7d 4hThu 5 Nov, 19:00 UTC FW
Memory2,029MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5215:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304015:0000:0009:0019:0004:0013:00

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Oct26 Oct27 Oct28 Oct29 Oct

Top 20% of all ranked servers, top 40% in NA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. The force wipe · high confidence

wipe-day peak5players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 4hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 4hFW

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on Azeroth - The Last Battle?

At their busiest, its recent wipes drew 5 players on average. After the latest wipe, numbers topped out at 1 hours.

How often does Azeroth - The Last Battle wipe, and when?

The only wipe for Azeroth - The Last Battle is the force wipe, once a month. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 3 days 15 hours ago. The tags state a wipe schedule of one wipe a month.

Lists and filters

Which tags does Azeroth - The Last Battle carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server; NA (North America): North America is the browser category it sits in from Azeroth - The Last Battle. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Azeroth - The Last Battle appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Azeroth - The Last Battle: Modded Rust servers, checked live and North America: server readout. Reading: server list filters. It comes up under 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.

Population

Where does Azeroth - The Last Battle sit in the rankings?

Top 20% of all ranked servers: Azeroth - The Last Battle takes #4,401 on seven-day player hours and #749 in North America.

What player count does Azeroth - The Last Battle carry?

Current headcount on Azeroth - The Last Battle: 0 players, 50 slots available. Seven-day check: 1 players on average. Peak reading: 5. The last 48 hours peaked at 23:00 UTC, averaging 2 players at that hour.

Operator and location

Where does Azeroth - The Last Battle sit?

Reading: location. The NA tag puts Azeroth - The Last Battle in North America. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 66.51.96.68:28005.

What Rust version is Azeroth - The Last Battle on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by Azeroth - The Last Battle. To get in, your game needs the same protocol; Steam applies the update.

How does Azeroth - The Last Battle perform?

Check: fps. Average 12 server fps over the last 48 hours, low of 5. Within range. Peak entity count: 72,011. Buildings, deployables and all else included. Check: memory. Peak use was 2,442 MB. What players call lag comes from low fps and an entity count on the rise.

Is Azeroth - The Last Battle up, and how often does it stay up?

Reading: online. Azeroth - The Last Battle answers right now. Check: restart. The uptime it reports puts the last restart about 35 hours ago. Reading: 99% uptime over the last 3 full days. It was up 71 of 72 hours. Reading: first seen 25 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on Azeroth - The Last Battle?

No gather rate appears in the name: Azeroth - The Last Battle. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on Azeroth - The Last Battle?

From seed 1, the game generates the procedural map on Azeroth - The Last Battle. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

What do you do to join Azeroth - The Last Battle?

Press F1 in Rust and enter client.connect 66.51.96.68:28005. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^m,NA,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

Region

NA
North America North America is the browser category it sits in.

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.