Skip to main content

Independent statistics on public Rust serversNot affiliated with Facepunch Studios

Latest count: 60,014 players on 11,706 servers
Rust CensusThe census of every public Rust server, counted and refreshed.

Statistical profileOffline

Aurora Combat

185.189.255.23:35100 checked 15h ago

weekly wipes moddedoxide
Release date
Next release
In five minutes (09:50 UTC)
Source
Live server queries
Server address
185.189.255.23:35100
First recorded
14 September 2026

Connect to this server

Launch Rust and join Website

1. Main points

Players now

1/ 50

2% full

7-day average

1

peak 3

Rank

#5,794

top 26%

Last wipe

9d ago

weekly schedule

Next wipe

4d 13h

Tue 3 Nov, 14:52 UTC

Main points

  • The server is offline; at its last check there were 1 players on it, 2% of its 50 slots.
  • Over the last seven days it averaged 1 players, with a peak of 3.
  • It ranks #5,794 of all ranked servers, the top 26%, on player hours over the last seven days.
  • Its current map went up 9d ago; the next wipe is expected Tuesday 3 November, 14:52 UTC, its weekly schedule tag.

2. Players

Figure 1: Players on Aurora Combat

Players now and over time, UTC

AveragePeak
00.250.50.75108:0009:00

Hourly average and peak, UTC.

Source: Live server queries, Rust Census

3. Server performance

Figure 2: Frame rate, entities and memory

From asking the server directly; low fps and a climbing entity count mean lag

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

Note

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.

4. Rank

Figure 3: Rank among all servers, 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.

Source: Live server queries, Rust Census

5. Wipe schedule

Patternfrom its schedule tag

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

Usual gap

5.1 days

between real wipes

On rhythm

14%

of its recent wipes

Wipe-day peak

4

players, last three wipes

Crowd held

100%

of its cycles kept half the crowd

Table 1: Coming wipes

Expected from its own rhythm and the force wipe

InDate and timeKind
4d 13hTue 3 Nov, 14:52 UTCOwn schedule
6d 18hThu 5 Nov, 19:00 UTCForce wipe FW
11d 13hTue 10 Nov, 14:52 UTCOwn schedule
18d 13hTue 17 Nov, 14:52 UTCOwn schedule
25d 13hTue 24 Nov, 14:52 UTCOwn schedule
32d 13hTue 1 Dec, 14:52 UTCOwn schedule
34d 18hThu 3 Dec, 19:00 UTCForce wipe FW
39d 13hTue 8 Dec, 14:52 UTCOwn schedule

Figure 4: The first 48 hours of its last wipes

Players each hour, from the hour of the wipe

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.

Source: Live server queries, Rust Census

6. Wipes

Table 2: Wipes, newest first

Every wipe seen on this server

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

Notes

  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.
  2. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Source: Live server queries, Rust Census

7. Map

Figure 5: Map of Aurora Combat

3000 · seed 1

Map of Aurora Combat

Table 3: The world

As the server publishes it

MapCustom Map
Size3000
Seed1

8. Server characteristics

Table 4: Characteristics of Aurora Combat

What the server publishes and what was recorded

Address185.189.255.23:35100
Region–
Max players50
Group limit10 max
Wipe scheduleweekly
Last wipe20 Oct 2026, 14:52 UTC
Hostname–
First seen14 Sep 2026

9. Similar servers

Table 5: Servers like this one

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

ServerCharacteristicsPlayers
【极光】100000000倍|枪战|礼包|建造|新手入门EA · groups of 16+ · 20 on average21 / 200
【星云】10000倍|爆枪|秒造|全解|礼包|新手入门EA · groups of 16+ · 15 on average18 / 200
ADRENALIN Rust RU 2X [ лутай СКИНЫ ] Loot+EU · groups of 60+ · 2x · weekly · 4 on average0 / 100
RUSTBURG.GG #1〔X5/X10|NO LIMIT|LOOT+|FPS+|KITS|TP〕27.10EU · groups of 50+ · 5x · weekly · 185 on average43 / 100
Scrapland x10000000 |BATTLEFIELD|KITS|TP|CLANS|SKINBOX|PVP|NA · groups of 35+ · 1e+07x · weekly · 137 on average228 / 300
CoolingLine #1 - x1000 | NOLIMIT | FAST | LOOT+ | FPS |CLANSEU · groups of 100+ · 1000x · weekly · 66 on average34 / 50

10. Quick answers

From the figures on this page.

Wipe details

When does Aurora Combat wipe, and how often?

As its schedule cannot be confirmed from the few wipes of Aurora Combat on record, the prediction follows its tag. On Tuesday 3 November at 14:52 UTC the next wipe is expected. 9 days 10 hours have passed since this world was made. The tags list a wipe schedule of one week.

What should you expect on wipe day at Aurora Combat?

An average of 4 players attended at peak across recent wipes. On the latest wipe, 25 hours passed before the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

About the server

Is Aurora Combat up, and how well has it held up?

The latest count records Aurora Combat as offline, last seen 15 hours ago. About 43 minutes ago is when it last restarted, according to the uptime it reports. Of the 168 hours in the last 7 full days, it was up 30 of them, or 18%. The first sighting of it by Rust Census was on 14 September 2026.

What does the performance record of Aurora Combat show?

Average server fps over the last 48 hours was 509, with a low of 509. The world carried up to 1,278 entities, including buildings, deployables and all else. Up to 971 MB of memory was used. Lag, as players feel it, comes from low fps and a climbing entity count.

In which location is Aurora Combat based?

No region is given by Aurora Combat. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. 185.189.255.23:35100 is its address.

On which Rust version does Aurora Combat operate?

The version in use on Aurora Combat is Rust network protocol 2635 and build 168909 on Windows. The same protocol is required for your game to join, and Steam updates it for you.

Player counts

How many players does Aurora Combat carry?

The last count for Aurora Combat was 15 hours ago; it is offline at present. Averaged over seven days: 1 players, with a peak of 3. An average of 1 players was recorded at 09:00 UTC, the busiest hour of the last 48.

How does Aurora Combat compare with other servers in the rankings?

For seven-day player hours, Aurora Combat is ranked #5,794, placing it in the top 26% of all ranked servers.

Tags, lists

Where does Aurora Combat appear among the Rust Census lists and filters?

These Rust Census lists include Aurora Combat: Modded Rust servers, counted and Rust battlefield servers. It appears under these filters on the server 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.

What is meant by each tag shown on Aurora Combat?

gmrust (Game mode): The game mode is standard survival as Rust runs it; mp50 (Max players): The server holds 50 slots; ts10 (Group limit): No team may hold more than 10; v2635 (Protocol): To connect, your game version must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server carries no region code; ^w (Weekly): This server wipes once a week; ^i (Battlefield): This is a battlefield server: high rates, kits and fast PvP; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): Plugins or settings alter the game on this modded server are the tags Aurora Combat publishes, and the game's server browser reads them. At the top of this page you will find the tags for current players, queue and world creation time.

Map and rules

Which map has been recorded for Aurora Combat?

Aurora Combat runs a procedural map of size 3,000 with seed 1, generated by the game. Because one size and seed give one map, RustMaps can display it from this page. The map carries the name: Custom Map.

What settings and rules have been listed for Aurora Combat?

No gather rate is given in the name of Aurora Combat. No group exceeds 10 players. battlefield is the game mode recorded, fast PvP with kits and high rates. The server browser lists it under Modded: plugins or settings alter the game. Plugins on it number Oxide. Anti-cheat is active: VAC, Valve's system, is on.

Connecting

What steps are needed to join Aurora Combat?

You can open the console in Rust with F1 and enter client.connect 185.189.255.23:35100; or press Launch Rust and join on this page, and you are connected through Steam. The website recorded for it is https://gamestores.app/.

11. Server tags

What each tag this server publishes means: a glossary.

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

Game

gmrustGame mode The game mode is standard survival as Rust runs it.
mp50Max players The server holds 50 slots.
ts10Group limit No team may hold more than 10.
v2635Protocol To connect, your game version must match protocol 2635.
cs168909Build Game build: 168909.
ptrakNetworking The network layer is RakNet, the game's standard.
$r?Region code This server carries no region code.

Wipe schedule

^wWeekly This server wipes once a week.

Gameplay

^iBattlefield This is a battlefield server: high rates, kits and fast PvP.

Mods and access

^oOxide Plugins are handled by Oxide (uMod) on this server.
^zModded Plugins or settings alter the game on this modded server.

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.