RUST METRICSFlight deck · live data
Data live Servers11,696 Players65,102 Populated3,491 Fresh wipes 3 h113 Scan5 min
‹ All servers95.188.71.57:28041
Online Full Queue Fresh wipe Wipe due No query

IRONRUST #2 [SOLO] WIPE 21|10|26

Online EU 95.188.71.57:28041 checked 13m ago

biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Wed 10:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 87 SERVER FPS

Server fps

48 h low 71 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 109,922 ×1000

Entities

48 h range 94,098–112,527 · memory 3,361 MB
1239 ET SINCE RESTART 11:05

Uptime

11 h 5 min since its last restart, at the last reading
7-day average1peak 5
Rank#2,730top 12% · #1040 in EU
Last wipe6d agobiweekly schedule
Next wipe7d 0hWed 4 Nov, 12:38 UTC
Memory3,361MB48 h peak 3 players
REC 1

Players

AveragePeak
0123412:0021:0006:0016:0001:0010:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020012:0021:0006:0016:0001:0010:00

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.

REC 3

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 12% of all ranked servers, top 36% in EU. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Wednesday 4 November, 12:38 UTC, in 7d 0h. Its biweekly schedule tag · low confidence

usual gap9.4 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak4players, last three wipes
crowd held50%else halves by day 7

Coming wipes

  1. WPT 1Wed 4 Nov, 12:38 UTC7d 0h
  2. WPT 2Thu 5 Nov, 19:00 UTC8d 7hFW
  3. WPT 3Wed 18 Nov, 12:38 UTC21d 0h
  4. WPT 4Wed 2 Dec, 12:38 UTC35d 0h
  5. WPT 5Thu 3 Dec, 19:00 UTC36d 7hFW

The first 48 hours of its last wipes

Wed 21 OctTue 13 OctFri 2 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 16 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 21 Oct, 12:38 UTC6d ago 3 – running 0
Tue 13 Oct, 05:46 UTC15d ago 7 halved by day 6 8.3 days 2
Fri 2 Oct, 07:20 UTC26d ago 3 held half 10.9 days 0
Fri 25 Sep, 03:48 UTC33d ago 5 held half 7.1 days 1
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on IRONRUST #2 [SOLO] WIPE 21|10|26?

The busiest point of its recent wipes drew 4 players on average. 16 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. By day 7 it fell below half when it didn't.

When does IRONRUST #2 [SOLO] WIPE 21|10|26 wipe?

Its tag guides the prediction: too few of IRONRUST #2 [SOLO] WIPE 21|10|26's wipes are on record to confirm its schedule. On Wednesday 4 November at 12:38 UTC its next wipe is due. 6 days 23 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.

Tag meanings

How should you read the tags on IRONRUST #2 [SOLO] WIPE 21|10|26?

These are the tags IRONRUST #2 [SOLO] WIPE 21|10|26 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server; EU (Europe): Its browser listing: Europe. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show IRONRUST #2 [SOLO] WIPE 21|10|26?

These Rust Metrics lists carry IRONRUST #2 [SOLO] WIPE 21|10|26: EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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.

Occupancy

Where does IRONRUST #2 [SOLO] WIPE 21|10|26 sit in the rankings?

Top 12% of all ranked servers: IRONRUST #2 [SOLO] WIPE 21|10|26 takes #2,730 on seven-day player hours and #1,040 in Europe.

What is the population on IRONRUST #2 [SOLO] WIPE 21|10|26?

0 of 100 slots are filled on IRONRUST #2 [SOLO] WIPE 21|10|26 right now. Check: players over seven days. Average 1, peak 5. Average at the busiest hour was 3 players, at 14:00 UTC over the last 48 hours.

Server

What location is IRONRUST #2 [SOLO] WIPE 21|10|26 hosted in?

IRONRUST #2 [SOLO] WIPE 21|10|26 gives Europe as its location, with the EU tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 95.188.71.57:28041.

What Rust version is IRONRUST #2 [SOLO] WIPE 21|10|26 on?

Rust network protocol 2635 and build 168909 on Windows is the build IRONRUST #2 [SOLO] WIPE 21|10|26 runs. Matching protocol is required to join. Let Steam update your game.

Is performance on IRONRUST #2 [SOLO] WIPE 21|10|26 within range?

Check: fps. Average 87 server fps over the last 48 hours, low of 71. Within range. Check: entities. The peak was 112,527, counting buildings, deployables and the rest of the world. Memory peak: 4,094 MB. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on IRONRUST #2 [SOLO] WIPE 21|10|26, and is it online?

Reading: online. IRONRUST #2 [SOLO] WIPE 21|10|26 answers right now. By its reported uptime, the last restart was roughly 11 hours ago. Uptime for the last 7 full days: 161 of 168 hours, or 96%. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What settings and rules apply on IRONRUST #2 [SOLO] WIPE 21|10|26?

Reading the name gives no gather rate for IRONRUST #2 [SOLO] WIPE 21|10|26. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on IRONRUST #2 [SOLO] WIPE 21|10|26?

Check: map. Procedural, size 4,301, seed 4613, generated by the game on IRONRUST #2 [SOLO] WIPE 21|10|26. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How do you connect to IRONRUST #2 [SOLO] WIPE 21|10|26?

To join: start Rust, press F1 and type client.connect 95.188.71.57:28041. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://m.vk.com/public149683027.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,EU,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

Region

EU
Europe Its browser listing: Europe.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.