Offline 212.227.139.212:29015 checked 14d ago
Aachener Alemannen
Connect
srv = rust.server("212.227.139.212:29016")
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 1 Oct. 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 15h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 15h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 15h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 19 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 22:44 UTC FW28d ago | 2 | NaN | running | 0 |
# 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
4500 · seed 249563
- map
- Procedural Map
- size
- 4500
- seed
- 249563
Server
srv.info()- address
- 212.227.139.212:29015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 22:44 UTC
- hostname
- –
- first seen
- 1 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 · 151 on average | 18/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 34/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 6/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 21/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 116/200 |
Quick answers
From the figures on this page.
Population data
What position does Aachener Alemannen take in the server rankings?
Player hours over seven days put Aachener Alemannen at #15,097, in the top 70% of the ranked set.
What population does Aachener Alemannen carry?
The current row shows Aachener Alemannen offline; the last response was 14 days 10 hours ago.
Server data
Which Rust version is Aachener Alemannen on?
Rust network protocol 2634 and build 167781 on Windows is what Aachener Alemannen runs. Joining needs the same protocol on your game; Steam handles the update.
Is Aachener Alemannen up, and what does its uptime show?
Offline now for Aachener Alemannen, last seen 14 days 10 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 1 October 2026.
Where does Aachener Alemannen sit?
There is no region published for Aachener Alemannen. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 212.227.139.212:29015.
Settings and map
Which rules apply on Aachener Alemannen, and what settings?
No gather rate appears in the name: Aachener Alemannen. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on Aachener Alemannen?
Aachener Alemannen runs a procedural map of size 4,500 with seed 249563, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does Aachener Alemannen wipe, and how often?
The only wipe Aachener Alemannen takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 28 days 4 hours ago.
What is wipe day on Aachener Alemannen like?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 19 hours in.
Tags and filters
Which lists on Rust Data hold Aachener Alemannen, and which filters?
The Rust Data lists that Aachener Alemannen fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Aachener Alemannen?
These tags are published by Aachener Alemannen and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. 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 Aachener Alemannen?
The manual route: launch Rust, F1, then client.connect 212.227.139.212:29015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.