RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h95 Scan5 min
‹ All servers84.32.26.228:28010
Offline Full Queue Fresh wipe Wipe due No query

RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY

Offline EU 84.32.26.228:28010 checked 1d ago

monthly wipes vanillamoddedoxide
COM 1 · connect
Launch Rust and join Website

Server instruments

last reading Mon 20:00 UTC
0 54 108 161 215 PAX 0 /215

Players now

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

Server fps

48 h low 30 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 69,395 ×1000

Entities

48 h range 69,395–71,479 · memory 2,750 MB
1239 ET SINCE RESTART 1D 04H

Uptime

1 days 4 hours since its last restart, at the last reading
7-day average0peak 2
Rank#11,562top 52% · #2370 in EU
Last wipe3d agomonthly schedule
Next wipe3d 22hSun 1 Nov, 16:55 UTC
Memory2,750MBat the last reading
REC 1

Players
AveragePeak
0123419:0020:00

Hourly average and peak, UTC.

REC 2

Server performance
01020304019:0020: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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep7 Oct14 Oct21 Oct28 Oct

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

PLAN

Wipe schedule

a steady gap

Next wipe Sunday 1 November, 16:55 UTC, in 3d 22h. Every 7 days 1 hours · medium confidence

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 3

Coming wipes

  1. WPT 1Sun 1 Nov, 16:55 UTC3d 22h
  2. WPT 2Thu 5 Nov, 19:00 UTC8d 0hFW
  3. WPT 3Sun 8 Nov, 17:52 UTC10d 23h
  4. WPT 4Sun 15 Nov, 18:48 UTC18d 0h
  5. WPT 5Sun 22 Nov, 19:45 UTC25d 1h
  6. WPT 6Sun 29 Nov, 20:42 UTC32d 2h
  7. WPT 7Thu 3 Dec, 19:00 UTC36d 0hFW
  8. WPT 8Sun 6 Dec, 21:38 UTC39d 3h

The first 48 hours of its last wipes

Sun 25 OctSun 18 OctSat 10 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 15:59 UTC3d ago 2 – running 0
Sun 18 Oct, 15:02 UTC10d ago 1 halved by day 4 7 days 0
Sat 10 Oct, 19:19 UTC17d ago 1 halved by day 2 7.8 days 0
Sun 4 Oct, 08:34 UTC24d ago 0 – 6.4 days 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Reset cycle

What happens on RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 3 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 3 it fell below half when it didn't.

What wipe timing does RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY follow?

Lately its wipes have been about every 7 days on RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY. Due on Sunday 1 November at 16:55 UTC is its next wipe. The world in play was created 3 days 2 hours ago. The tags state a wipe schedule of one wipe a month.

Lists and filters

Which tags does RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp215 (Max players): Slots: 215; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EU (Europe): Europe is the browser category it sits in from RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY appear in Rust Metrics lists and filters?

These Rust Metrics lists carry RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY: EU Rust servers, checked and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Region: Europe; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.

Population

What position does RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY hold among Rust servers?

Ranked by seven-day player hours, RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY sits at #11,562 and #2,370 in Europe, inside the top 52%.

What is the population on RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY?

Status for RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY: offline. Last seen 45 hours ago. Seven-day check: 0 players on average. Peak reading: 2.

Server

Where does RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY sit?

Reading: location. The EU tag puts RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY in Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 84.32.26.228:28010.

What Rust version is RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY on?

Rust network protocol 2635 and build 168909 on Linux is the build RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY runs. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY?

Reading: 30 server fps on average across the last 48 hours. It never dropped below 30. Peak entity count: 71,479. Buildings, deployables and all else included. Memory peak: 2,750 MB. Expect lag when fps falls and entities climb.

Is RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY up, and how often does it stay up?

Reading: offline. RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY last answered 45 hours ago. Check: restart. The uptime it reports puts the last restart about 28 hours ago. Reading: 82% uptime over the last 7 full days. It was up 138 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY enforce, and what are its settings?

Check: gather rate. The name RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. The server calls itself vanilla, with this meaning: rates, kits and rules are exactly as Facepunch ships them. Anti-cheat reading: VAC on, Valve's system.

What map is RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY on?

Size 3,500 and seed 1337: the game generates the procedural map on RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY from them. The map repeats when size and seed match. Open it on RustMaps from this page. Read the map name: Wiped 1 days ago.

How to join

What do you do to join RustOps - Solo/Duo Bi-Weekly #3 | WIPES ON WEDNESDAY AND SUNDAY?

Check: join. Open Rust, press F1, then enter client.connect 84.32.26.228:28010. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://rustops.org/.

PLACARDS

Server tags

what each one means

Published as mp215,ptrak,$r?,v2635,^m,^v,EU,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp215
Max players Slots: 215.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Difficulty

^v
Vanilla Rates, kits and rules are exactly as Facepunch ships them.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

EU
Europe Europe is the browser category it sits in.

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.