Online 176.57.171.141:28515 checked 9m ago
[GER]Inusura_PVE
Connect
srv = rust.server("176.57.171.141:28516")
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 66% 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 7d 12h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 12h | 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 1, 31 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 03:28 UTC27d ago | 1 | 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 685613304
- map
- Procedural Map
- size
- 4500
- seed
- 685613304
Server
srv.info()- address
- 176.57.171.141:28515
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 03:28 UTC
- hostname
- –
- first seen
- 13 Sep 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 | 1[PvE]Тульский|Русский|Classic+Ивенты | EU · groups of 8+ · monthly · 34 on average | 18/200 |
| 1 | [PvE] Relic Europe | No Killing | No Raiding | No Decay | EU · groups of 30+ · monthly · 31 on average | 5/200 |
| 2 | [GER] Rust Oase |PVE|Quests|XP|Raidable Bases|Events | EU · groups of 15+ · monthly · 30 on average | 5/140 |
| 3 | [EU] Salty Zombies PvE #1 | Skills | Raid | Quests | Jetpack | | EU · groups of 8+ · monthly · 26 on average | 8/150 |
| 4 | Hex EU PVE Monthly 1X BiWeekly 5X | RPG | Custom Weapons | Jet | EU · no group limit · 1x · monthly · 25 on average | 17/100 |
| 5 | Фармер[FULL PVE-НОВИЧОК-РЕЙД БАЗЫ] | EU · groups of 8+ · monthly · 17 on average | 7/75 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does [GER]Inusura_PVE rank?
Over the last seven days [GER]Inusura_PVE sits at #14,679 on player hours, in the top 66% of ranked servers.
What population does [GER]Inusura_PVE carry?
The sample now reads 0 players for [GER]Inusura_PVE, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 2.
Server data
How well does [GER]Inusura_PVE perform?
Averaged over 48 hours: 4 server fps, never under 1. Buildings, deployables and all else in the world took the count as high as 118,257 entities. Memory peaked at 2,966 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does [GER]Inusura_PVE run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by [GER]Inusura_PVE. Steam updates your game for you, but the protocol must match to join.
Is [GER]Inusura_PVE up, and what does its uptime show?
[GER]Inusura_PVE reports itself online at the current refresh. A restart about 1 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.
Which location does [GER]Inusura_PVE run from?
No region tag is published by [GER]Inusura_PVE, though its name points to Europe. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 176.57.171.141:28515.
Rules, settings, map
What rules and settings are recorded for [GER]Inusura_PVE?
No gather rate appears in the name: [GER]Inusura_PVE. The group limit sits at the default of 8 players. Recorded as pve, no combat between players. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Vanilla, by its own description: facepunch's stock game, with rates, kits and rules untouched. VAC is not running; Valve's anti-cheat is off.
Which map has [GER]Inusura_PVE selected?
The game generates the map on [GER]Inusura_PVE: procedural, size 4,500, seed 685613304. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does [GER]Inusura_PVE wipe, and on what schedule?
A single wipe each month, the force wipe, is all [GER]Inusura_PVE does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 27 days 3 hours ago, and that is the one in play. The tags list wipes as monthly.
On [GER]Inusura_PVE, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 31 hours in.
Tags and filters
Which lists on Rust Data hold [GER]Inusura_PVE, and which filters?
The Rust Data lists that [GER]Inusura_PVE fits are: EU Rust servers, Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Region: Europe; Type: Vanilla and Modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on [GER]Inusura_PVE?
The game's server browser reads these tags from [GER]Inusura_PVE: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into [GER]Inusura_PVE?
In Rust, F1 opens the console: type client.connect 176.57.171.141:28515. Launch Rust on this page does the same by opening the game through Steam and connecting.
