Offline 82.177.102.210:28055 checked 2d ago
aurora body test 3
Connect
srv = rust.server("82.177.102.210:28057")
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 best
Top 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:28055
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 09:39 UTC
- hostname
- –
- first seen
- 19 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 · 150 on average | 104/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 153/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 45/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 18/1000 |
Quick answers
From the figures on this page.
Population data
How does aurora body test 3 compare in the rankings?
Over the last seven days aurora body test 3 sits at #15,338 on player hours, in the top 69% of ranked servers.
What population does aurora body test 3 carry?
Offline now for aurora body test 3, with the last sample 2 days 17 hours ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does aurora body test 3 run?
The build is Rust network protocol 2634 and build 166652 on Windows, run by aurora body test 3. Steam updates your game for you, but the protocol must match to join.
Is aurora body test 3 up, and what does its uptime show?
The latest sample has aurora body test 3 offline, with a last sighting 2 days 17 hours ago. 41 of 168 hours up over the last 7 full days, or 24%. Its earliest recorded date in Rust Data is 19 October 2026.
In which location is aurora body test 3 hosted?
There is no region published for aurora body test 3. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 82.177.102.210:28055.
Settings and map
Which rules apply on aurora body test 3, and what settings?
No gather rate appears in the name: aurora body test 3. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. The VAC field reads off.
Which map has aurora body test 3 selected?
aurora body test 3 runs a procedural map, which the game generates.
Wipes and dates
On what schedule does aurora body test 3 wipe?
A rhythm cannot be read from the wipes of aurora body test 3 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. A new world was started 9 days 22 hours ago, and that is the one in play.
Lists and tags
Where does aurora body test 3 appear among Rust Data lists and filters?
These Rust Data lists include aurora body test 3: 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 3?
These tags are published by aurora body test 3 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): Slot count: 2; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to aurora body test 3?
The manual route: launch Rust, F1, then client.connect 82.177.102.210:28055. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.