Rust PopulationField survey · Rust servers
Observing 62,312 players 11,738 servers 3,391 with someone on 192 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 5,679habitat unknownfirst seen 14 Sep 2026

Aurora Combat

Offline 185.189.255.23:35100 checked 1h ago

weekly wipes moddedoxide

Measurements

Players now
1/ 50
= 1 player
2% full
7-day average
1
peak 3
Rank
#5,679
top 26%
Last wipe
8d ago
weekly schedule
Next wipe
5d 3h
Tue 3 Nov, 14:52 UTC
Obs. 1 · sightings

Players

AveragePeak
00.250.50.75108:0009:00

Hourly average and peak, UTC.

Obs. 2 · condition

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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Obs. 4 · the wipe cycle

Wipe schedule

from its schedule tag

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

5.1 days
usual gap
between real wipes
14%
on rhythm
of its recent wipes
4
wipe-day peak
players, last three wipes
100%
crowd held
of its cycles kept half the crowd

Coming wipes

5d 3h
Tue 3 Nov, 14:52 UTC
7d 7h
Thu 5 Nov, 19:00 UTC
FW
12d 3h
Tue 10 Nov, 14:52 UTC
19d 3h
Tue 17 Nov, 14:52 UTC
26d 3h
Tue 24 Nov, 14:52 UTC
33d 3h
Tue 1 Dec, 14:52 UTC
35d 7h
Thu 3 Dec, 19:00 UTC
FW
40d 3h
Tue 8 Dec, 14:52 UTC

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 seen

Wipes

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

Field questions

Quick answers

from the figures on this page

Player counts

How does Aurora Combat rank against other Rust servers?

Over the past week it ranks #5,679 for player hours, which puts Aurora Combat in the top 26% of all ranked servers.

How busy is Aurora Combat?

At this count Aurora Combat is offline, with its last sighting 1 hours ago. Averaged over seven days, it drew 1 players and reached a peak of 3. Look at the last 48 hours and 09:00 UTC stands out: it averaged 1 players.

Tags

What do the server tags on Aurora Combat mean?

What the game's server browser reads from Aurora Combat is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts10 (Group limit): Teams can have no more than 10 players; v2635 (Protocol): Your game needs the same version, protocol 2635, to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set; ^w (Weekly): Every week the server wipes; ^i (Battlefield): High rates and kits drive fast PvP here; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings change the game; it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include Aurora Combat?

Aurora Combat appears among the Rust Population lists that follow: Modded Rust servers, counted and Rust battlefield servers. These are the filters it appears under when you browse the list: 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.

Wipe notes

What does wipe day look like on Aurora Combat?

The busiest point of its recent wipes averaged 4 players. The crowd on the latest wipe peaked 25 hours in. Half that peak held until the next wipe in 100% of its recent wipes.

What is the wipe schedule on Aurora Combat?

Its tag sets the prediction: too few of Aurora Combat's wipes are on record to confirm the schedule. Due on Tuesday 3 November at 14:52 UTC is its next wipe. 8 days 20 hours ago the current world was made. Its tags carry a wipe schedule of one wipe a week.

Map and rules

Which map does Aurora Combat run?

The map on Aurora Combat is procedural, made by the game at size 3,000 from seed 1. The map follows from its size and seed, and RustMaps shows it from this page. The name on the map is Custom Map.

What are the rules and settings on Aurora Combat?

No gather rate appears in the name of Aurora Combat. Up to 10 players can team together. This server runs battlefield, kits and high rates drive fast PvP. The server browser files it under Modded, where plugins or settings alter the game. You will find Oxide running as plugins. The anti-cheat VAC from Valve is enabled.

Server details

Which version of Rust does Aurora Combat run?

Rust network protocol 2635 and build 168909 on Windows is what Aurora Combat uses. Your game needs the same protocol to join; Steam takes care of updating it.

Does Aurora Combat run smoothly?

It ran at 509 server fps on average over the last 48 hours, and never went below 509. The entity count reached 1,278: buildings, deployables and all other objects. Up to 971 MB of memory was used. What players experience as lag comes from low fps and a rising entity count.

Is Aurora Combat online, and how reliable is it?

Offline at the moment, Aurora Combat was last seen 1 hours ago. Judging by the uptime it reports, the last restart was about 43 minutes ago. It was up 21% of the time over the last 7 full days, 36 out of 168 hours. The first sighting by Rust Population was on 14 September 2026.

Where is Aurora Combat located?

A region is not published by Aurora Combat. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 185.189.255.23:35100.

Getting in

How do I join Aurora Combat?

Open the console with F1 in Rust and enter client.connect 185.189.255.23:35100. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you. You can find its website at https://gamestores.app/.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp50
Max players 50 slots are available.
ts10
Group limit Teams can have no more than 10 players.
v2635
Protocol Your game needs the same version, protocol 2635, to join.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer here, as standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Every week the server wipes.

Gameplay

^i
Battlefield High rates and kits drive fast PvP here.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), is in use.
^z
Modded Plugins or settings change the game; it is listed under 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.