Online EU 95.188.71.57:28041 checked 10m ago
IRONRUST #2 [SOLO] WIPE 21|10|26
Connect
srv = rust.server("95.188.71.57:28043")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 bestTop 12% of all ranked servers, top 36% in EU. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Wednesday 4 November, 12:38 UTC, in 7d 6h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 6h | Wed 4 Nov, 12:38 UTC | wipe |
| 1 | 8d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 21d 6h | Wed 18 Nov, 12:38 UTC | wipe |
| 3 | 35d 6h | Wed 2 Dec, 12:38 UTC | wipe |
| 4 | 36d 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 3, 16 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 21 Oct, 12:38 UTC6d ago | 3 | NaN | running | 0 |
| 1 | Tue 13 Oct, 05:46 UTC15d ago | 7 | halved by day 6 | 8.3 days | 2 |
| 2 | Fri 2 Oct, 07:20 UTC25d ago | 3 | held half | 10.9 days | 0 |
| 3 | Fri 25 Sep, 03:48 UTC33d ago | 5 | held half | 7.1 days | 1 |
| 4 | Mon 14 Sep, 14:02 UTC43d ago | 4 | halved by day 8 | 10.6 days | 1 |
# 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
4301 · seed 4613![Map of IRONRUST #2 [SOLO] WIPE 21|10|26](https://files.facepunch.com/rust/map-images/6f6518faf6da1079c9baabcd9d8f68edded67e92d787d939f3b24e2e22237d5d/proceduralmap.4301.1792586275753.289_6f6518faf6da1079c9baabcd9d8f68ed.jpg)
- map
- Procedural Map
- size
- 4301
- seed
- 4613
Server
srv.info()- address
- 95.188.71.57:28041
- region
- EU
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 21 Oct 2026, 12:38 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10 | EU · groups of 50+ · biweekly · 9 on average | 4/200 |
| 1 | RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ | EU · groups of 8+ · biweekly · 7 on average | 1/200 |
| 2 | [ESP][PVE] PACIFIC WORLD (WIPED 15/10/2026) | EU · groups of 16+ · biweekly · 4 on average | 0/50 |
| 3 | РЕЛАКС #2 Х2|Для новичков| No Limit | EU · groups of 10+ · biweekly · 3 on average | 3/200 |
| 4 | #1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RU | EU · groups of 10+ · biweekly · 3 on average | 0/300 |
| 5 | [EU][UK][HUN] Rust Hungary PVE/PVP OFFICIAL | EU · groups of 8+ · biweekly · 2 on average | 0/50 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does IRONRUST #2 [SOLO] WIPE 21|10|26 rank?
On seven-day player hours IRONRUST #2 [SOLO] WIPE 21|10|26 is #2,760 overall and #1,042 in Europe, inside the top 12% of all ranked servers.
How full does IRONRUST #2 [SOLO] WIPE 21|10|26 run?
Current row: 3 players on IRONRUST #2 [SOLO] WIPE 21|10|26, against 100 slots. Over the last seven days it averaged 1 players and peaked at 5. Peak hour in the last 48 hours: 14:00 UTC, mean 3 players.
About the server
How smoothly does IRONRUST #2 [SOLO] WIPE 21|10|26 run?
Averaged over 48 hours: 87 server fps, never under 69. Entity numbers reached 112,527, and that includes buildings, deployables and the rest. Memory peaked at 4,094 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is IRONRUST #2 [SOLO] WIPE 21|10|26 on?
Rust network protocol 2635 and build 168909 on Windows is what IRONRUST #2 [SOLO] WIPE 21|10|26 runs. Joining needs the same protocol on your game; Steam handles the update.
Is IRONRUST #2 [SOLO] WIPE 21|10|26 up, and what does its uptime show?
IRONRUST #2 [SOLO] WIPE 21|10|26 reports itself online at the current refresh. The uptime it reports puts the last restart about 5 hours ago. Uptime of 96% across the last 7 full days: 161 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
In which location is IRONRUST #2 [SOLO] WIPE 21|10|26 hosted?
The EU tag is what IRONRUST #2 [SOLO] WIPE 21|10|26 uses to list itself in Europe. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 95.188.71.57:28041.
Rules, settings, map
Which rules apply on IRONRUST #2 [SOLO] WIPE 21|10|26, and what settings?
No gather rate appears in the name: IRONRUST #2 [SOLO] WIPE 21|10|26. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has IRONRUST #2 [SOLO] WIPE 21|10|26 selected?
IRONRUST #2 [SOLO] WIPE 21|10|26 runs a procedural map of size 4,301 with seed 4613, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does IRONRUST #2 [SOLO] WIPE 21|10|26 wipe, and on what schedule?
Too few wipes are on record for IRONRUST #2 [SOLO] WIPE 21|10|26 to confirm its schedule, so the tag drives the prediction. The schedule puts the next wipe on Wednesday 4 November at 12:38 UTC. The world it runs now was generated 6 days 17 hours ago. Its tags carry a wipe schedule of every two weeks.
On IRONRUST #2 [SOLO] WIPE 21|10|26, what happens on wipe day?
The average peak over recent wipes is 4 players. Peak population on the latest wipe came 16 hours in. Half the peak or more was held to the next wipe in 50% of recent wipes. In the wipes where it did not hold, half was lost by day 7.
Lists and tags
Which Rust Data filters and lists contain IRONRUST #2 [SOLO] WIPE 21|10|26?
The Rust Data lists that IRONRUST #2 [SOLO] WIPE 21|10|26 fits are: EU Rust servers and Modded Rust servers. It appears under these filters on the server list: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week.
How should you read the server tags on IRONRUST #2 [SOLO] WIPE 21|10|26?
The game's server browser reads these tags from IRONRUST #2 [SOLO] WIPE 21|10|26: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; EU (Europe): The server browser files it under Europe. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join IRONRUST #2 [SOLO] WIPE 21|10|26?
In Rust, F1 opens the console: type client.connect 95.188.71.57:28041. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://m.vk.com/public149683027.