Offline 185.189.255.23:35100 checked 17h ago
Aurora Combat
Connect
srv = rust.server("185.189.255.23:35110")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 26% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Tuesday 3 November, 14:52 UTC, in 4d 11h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 4d 11h | Tue 3 Nov, 14:52 UTC | wipe |
| 1 | 6d 15h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 11d 11h | Tue 10 Nov, 14:52 UTC | wipe |
| 3 | 18d 11h | Tue 17 Nov, 14:52 UTC | wipe |
| 4 | 25d 11h | Tue 24 Nov, 14:52 UTC | wipe |
| 5 | 32d 11h | Tue 1 Dec, 14:52 UTC | wipe |
| 6 | 34d 15h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 39d 11h | Tue 8 Dec, 14:52 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 25 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 20 Oct, 14:52 UTC9d ago | 4 | NaN | running | 4 |
| 1 | Mon 19 Oct, 15:07 UTC10d ago | 4 | NaN | 1 days | 2 |
| 2 | Sat 17 Oct, 11:25 UTC12d ago | 4 | held half | 2.2 days | 2 |
| 3 | Fri 16 Oct, 13:31 UTC13d ago | 4 | NaN | 0.9 days | 2 |
| 4 | Tue 6 Oct, 22:24 UTC23d ago | 9 | held half | 9.6 days | 0 |
| 5 | Thu 1 Oct, 20:31 UTC FW28d ago | 5 | held half | 5.1 days | 0 |
| 6 | Thu 24 Sep, 16:06 UTC35d ago | 5 | halved by day 4 | 7.2 days | 0 |
| 7 | 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.
display(srv.map, srv.info())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | 【极光】100000000倍|枪战|礼包|建造|新手入门 | EA · groups of 16+ · 20 on average | 24/200 |
| 1 | 【星云】10000倍|爆枪|秒造|全解|礼包|新手入门 | EA · groups of 16+ · 15 on average | 18/200 |
| 2 | ADRENALIN Rust RU 2X [ лутай СКИНЫ ] Loot+ | EU · groups of 60+ · 2x · weekly · 4 on average | 0/100 |
| 3 | RUSTBURG.GG #1〔X5/X10|NO LIMIT|LOOT+|FPS+|KITS|TP〕27.10 | EU · groups of 50+ · 5x · weekly · 187 on average | 37/100 |
| 4 | Scrapland x10000000 |BATTLEFIELD|KITS|TP|CLANS|SKINBOX|PVP| | NA · groups of 35+ · 1e+07x · weekly · 135 on average | 181/300 |
| 5 | CoolingLine #1 - x1000 | NOLIMIT | FAST | LOOT+ | FPS |CLANS | EU · groups of 100+ · 1000x · weekly · 67 on average | 18/50 |
Quick answers
From the figures on this page.
Population data
What position does Aurora Combat take in the server rankings?
Player hours over seven days put Aurora Combat at #5,786, in the top 26% of the ranked set.
What population does Aurora Combat carry?
The current row shows Aurora Combat offline; the last response was 17 hours ago. Over the last seven days it averaged 1 players and peaked at 3. The 48-hour sample puts the busiest hour at 09:00 UTC, averaging 1 players.
Server facts
What does performance look like on Aurora Combat?
The 48-hour average is 509 server fps, with a low of 509. The entity count peaked at 1,278, covering buildings, deployables and the rest of the world. The memory field tops out at 971 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on Aurora Combat?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Aurora Combat. Steam updates your game for you, but the protocol must match to join.
How reliable is Aurora Combat, and is it online now?
The latest sample has Aurora Combat offline, with a last sighting 17 hours ago. A restart about 43 minutes ago is what its reported uptime implies. Uptime of 19% across the last 7 full days: 32 hours of 168. Its earliest recorded date in Rust Data is 14 September 2026.
Which location does Aurora Combat run from?
There is no region published for Aurora Combat. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 185.189.255.23:35100 is its address.
Map and rules
What rules and settings are recorded for Aurora Combat?
No gather rate appears in the name: Aurora Combat. Group size tops out at 10 players. Recorded as battlefield, fast PvP, kits supplied, rates high. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
What is the map on Aurora Combat?
The game generates the map on Aurora Combat: procedural, size 3,000, seed 1. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.
Wipe schedule
When does Aurora Combat wipe, and on what schedule?
The tag sets the prediction: Aurora Combat has too few wipes on record to confirm its schedule. Tuesday 3 November at 14:52 UTC is when the next wipe is due. The world it runs now was generated 9 days 12 hours ago. A weekly wipe schedule is published in its tags.
What is wipe day on Aurora Combat like?
Recent wipes averaged 4 players at their peak. The crowd on the latest wipe topped out 25 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags and filters
Where does Aurora Combat appear among Rust Data lists and filters?
On Rust Data, Aurora Combat appears in these lists: Modded Rust servers 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.
Which meanings do the tags on Aurora Combat hold?
Read by the game's server browser, the tags Aurora Combat publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts10 (Group limit): No team may exceed 10; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^w (Weekly): A wipe every week; ^i (Battlefield): High rates and kits, for fast PvP; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join Aurora Combat?
The manual route: launch Rust, F1, then client.connect 185.189.255.23:35100. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://gamestores.app/ is the website recorded for it.