Offline 82.177.102.210:28085 checked 2d ago
aurora body test 6
Connect
srv = rust.server("82.177.102.210:28087")
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:28085
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Oct 2026, 07:19 UTC
- hostname
- –
- first seen
- 20 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 · 154 on average | 24/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 33/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 15/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Population data
What position does aurora body test 6 take in the server rankings?
Player hours over seven days put aurora body test 6 at #15,358, in the top 69% of the ranked set.
How full does aurora body test 6 run?
Offline now for aurora body test 6, with the last sample 2 days 15 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is aurora body test 6 on?
Version Rust network protocol 2634 and build 166652 on Windows is reported by aurora body test 6. Steam updates your game for you, but the protocol must match to join.
How reliable is aurora body test 6, and is it up?
aurora body test 6 is offline at this refresh; the last response came 2 days 15 hours ago. Uptime of 23% across the last 7 full days: 38 hours of 168. Rust Data logged it first on 20 October 2026.
Where does aurora body test 6 sit?
No region is published by aurora body test 6. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 82.177.102.210:28085.
Rules, settings, map
What rules and settings are recorded for aurora body test 6?
You will not find a gather rate in the string aurora body test 6. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC is not running; Valve's anti-cheat is off.
What is the map on aurora body test 6?
aurora body test 6 runs a procedural map, which the game generates.
Wipes and dates
When does aurora body test 6 wipe, and on what schedule?
A rhythm cannot be read from the wipes of aurora body test 6 on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 8 days 20 hours ago.
Tags and filters
Which lists on Rust Data hold aurora body test 6, and which filters?
These Rust Data lists include aurora body test 6: Modded Rust servers. These filters bring it up 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 6?
These tags are published by aurora body test 6 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): The server runs build 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is 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.
Connecting
How can I connect to aurora body test 6?
The manual route: launch Rust, F1, then client.connect 82.177.102.210:28085. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.