RUST METRICSFlight deck · live data
Data live Servers11,626 Players40,285 Populated2,838 Fresh wipes 3 h132 Scan5 min
‹ All servers185.189.255.23:35100
Offline Full Queue Fresh wipe Wipe due No query

Aurora Combat

Offline 185.189.255.23:35100 checked 19h ago

weekly wipes moddedoxide
COM 1 · connect

Server instruments

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

Players now

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

Server fps

48 h low 509 · below 20 is lag, below 10 is bad
0 5 10 15 20 ENT 1,278 ×1000

Entities

48 h range 1,278–1,278 · memory 971 MB
1239 ET SINCE RESTART 00:43

Uptime

0 h 43 min since its last restart, at the last reading
7-day average1peak 3
Rank#5,787top 26%
Last wipe9d agoweekly schedule
Next wipe4d 9hTue 3 Nov, 14:52 UTC
Memory971MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75108:0009:00

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

Top 26% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Tuesday 3 November, 14:52 UTC, in 4d 9h. Its weekly schedule tag · low confidence

usual gap5.1 daysbetween real wipes
on rhythm14%of its recent wipes
wipe-day peak4players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

  1. WPT 1Tue 3 Nov, 14:52 UTC4d 9h
  2. WPT 2Thu 5 Nov, 19:00 UTC6d 14hFW
  3. WPT 3Tue 10 Nov, 14:52 UTC11d 9h
  4. WPT 4Tue 17 Nov, 14:52 UTC18d 9h
  5. WPT 5Tue 24 Nov, 14:52 UTC25d 9h
  6. WPT 6Tue 1 Dec, 14:52 UTC32d 9h
  7. WPT 7Thu 3 Dec, 19:00 UTC34d 14hFW
  8. WPT 8Tue 8 Dec, 14:52 UTC39d 9h

The first 48 hours of its last wipes

Tue 20 OctMon 19 OctSat 17 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 25 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 14:52 UTC9d ago 4 – running 4
Mon 19 Oct, 15:07 UTC10d ago 4 – 1 days 2
Sat 17 Oct, 11:25 UTC12d ago 4 held half 2.2 days 2
Fri 16 Oct, 13:31 UTC13d ago 4 – 0.9 days 2
Tue 6 Oct, 22:24 UTC23d ago 9 held half 9.6 days 0
Thu 1 Oct, 20:31 UTC FW28d ago 5 held half 5.1 days 0
Thu 24 Sep, 16:06 UTC35d ago 5 halved by day 4 7.2 days 0
Wed 16 Sep, 16:45 UTC43d ago 9 halved by day 3 8 days 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

Wipe schedule

What should you expect from wipe day on Aurora Combat?

At their busiest, its recent wipes drew 4 players on average. 25 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

When does Aurora Combat wipe?

The prediction follows its tag, because too few of Aurora Combat's wipes are on record to confirm its schedule. Due on Tuesday 3 November at 14:52 UTC is its next wipe. The world in play was created 9 days 14 hours ago. A weekly wipe schedule is published in its tags.

Tag meanings

Which tags does Aurora Combat carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts10 (Group limit): Team cap: 10; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^w (Weekly): It wipes each week; ^i (Battlefield): Check: mode. Battlefield, with kits and high rates for quick fights; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from Aurora Combat. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Aurora Combat appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Aurora Combat: Modded Rust servers, checked live and Rust battlefield servers: check the readings. Reading: server list filters. It comes up under Type: Modded; Server tag: Weekly ^w, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks.

Occupancy

What position does Aurora Combat hold among Rust servers?

Ranking for Aurora Combat: #5,787 on seven-day player hours, top 26% of all ranked servers.

What is the population on Aurora Combat?

Aurora Combat is not responding; status offline, last seen 19 hours ago. Seven-day check: 1 players on average. Peak reading: 3. The last 48 hours peaked at 09:00 UTC, averaging 1 players at that hour.

Operator and location

What location is Aurora Combat hosted in?

No region tag on Aurora Combat. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 185.189.255.23:35100.

What Rust version is Aurora Combat on?

Rust network protocol 2635 and build 168909 on Windows is the build Aurora Combat runs. Check: protocol. To join, your game must match; Steam handles the update.

Is performance on Aurora Combat within range?

Reading: 509 server fps on average across the last 48 hours. It never dropped below 509. Check: entities. The peak was 1,278, counting buildings, deployables and the rest of the world. Reading: 971 MB of memory at the highest. Expect lag when fps falls and entities climb.

How reliable is Aurora Combat, and is it online now?

Aurora Combat reports offline. The last reading came 19 hours ago. Check: restart. The uptime it reports puts the last restart about 43 minutes ago. Uptime for the last 7 full days: 32 of 168 hours, or 19%. The first sighting on Rust Metrics was 14 September 2026.

Settings and map

How is Aurora Combat configured, and what rules are in force?

Check: gather rate. The name Aurora Combat does not state one. Check: group limit. Up to 10 players. battlefield, kits and high rates drive fast PvP — that is the game mode. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on Aurora Combat?

Size 3,000 and seed 1: the game generates the procedural map on Aurora Combat from them. View it on RustMaps from this page: matching size and seed give an identical map. Map name, as listed: Custom Map.

Join

How do you connect to Aurora Combat?

Press F1 in Rust and enter client.connect 185.189.255.23:35100. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://gamestores.app/ is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^w,^i,gmrust,cs168909,ts10,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts10
Group limit Team cap: 10.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly It wipes each week.

Gameplay

^i
Battlefield Check: mode. Battlefield, with kits and high rates for quick fights.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.