Offline 82.177.102.210:28035 checked 6d ago
aurora body test
Connect
srv = rust.server("82.177.102.210:28037")
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. 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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 82.177.102.210:28035
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 22:45 UTC
- hostname
- –
- first seen
- 17 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 157/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 66/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 11/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 21/1000 |
Quick answers
From the figures on this page.
Population
What position does aurora body test take in the server rankings?
Player hours over seven days put aurora body test at #15,323, in the top 69% of the ranked set.
How full does aurora body test run?
aurora body test returns no live count at this refresh, having last been seen 6 days 23 hours ago. Over the last seven days it averaged 0 players.
Server data
Which Rust version is aurora body test on?
Version Rust network protocol 2634 and build 166652 on Windows is reported by aurora body test. Joining needs the same protocol on your game; Steam handles the update.
How reliable is aurora body test, and is it up?
aurora body test is offline at this refresh; the last response came 6 days 23 hours ago. Uptime of 7% across the last 7 full days: 12 hours of 168. The first row Rust Data holds for it is dated 17 October 2026.
Which location does aurora body test run from?
For aurora body test, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 82.177.102.210:28035 is its address.
Map and rules
Which settings and rules does aurora body test run?
You will not find a gather rate in the string aurora body test. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. The VAC field reads off.
Which map has aurora body test selected?
The game generates its map: procedural, on aurora body test.
Wipes and dates
On what schedule does aurora body test wipe?
A rhythm cannot be read from the wipes of aurora body test on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 11 days 12 hours ago.
Tags, lists
Where does aurora body test appear among Rust Data lists and filters?
The Rust Data lists that aurora body test fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on aurora body test?
The game's server browser reads these tags from aurora body test: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): Slot count: 2; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. 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.
Join steps
What is the way to join aurora body test?
In Rust, F1 opens the console: type client.connect 82.177.102.210:28035. Launch Rust on this page does the same by opening the game through Steam and connecting.