RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h37 Scan5 min
‹ All servers95.188.71.57:28015
Online Full Queue Fresh wipe Wipe due No query

Protocol 404 WiPe 02.10.26

Online EU 95.188.71.57:28015 checked 2h ago

biweekly wipes vanillaoxide
COM 1 · connect

Server instruments

last reading Wed 17: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 73 SERVER FPS

Server fps

48 h low 73 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 185,998 ×1000

Entities

48 h range 162,858–187,147 · memory 3,376 MB
1239 ET SINCE RESTART 17:51

Uptime

17 h 51 min since its last restart, at the last reading
7-day average0peak 2
Rank#4,977top 22% · #1696 in EU
Last wipe26d agobiweekly schedule
Next wipe1d 16hFri 30 Oct, 11:50 UTC
Memory3,376MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5220:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020020:0005:0014:0023:0008:0017: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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 11:50 UTC, in 1d 16h. Its biweekly schedule tag · low confidence

wipe-day peak2players, last three wipes

Coming wipes

  1. WPT 1Fri 30 Oct, 11:50 UTC1d 16h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 23hFW
  3. WPT 3Fri 13 Nov, 11:50 UTC15d 16h
  4. WPT 4Fri 27 Nov, 11:50 UTC29d 16h
  5. WPT 5Thu 3 Dec, 19:00 UTC35d 23hFW
  6. WPT 6Fri 11 Dec, 11:50 UTC43d 16h

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 11:50 UTC26d ago 2 – 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.

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 happens on Protocol 404 WiPe 02.10.26 when wipe day comes?

The busiest point of its recent wipes drew 2 players on average. 26 hours after the wipe, the crowd peaked on the latest wipe.

When does Protocol 404 WiPe 02.10.26 wipe?

Its tag guides the prediction: too few of Protocol 404 WiPe 02.10.26's wipes are on record to confirm its schedule. Friday 30 October at 11:50 UTC is when its next wipe is due. The world it runs now was made 26 days 7 hours ago. A wipe schedule of every two weeks is published in its tags.

Tag meanings

Which tags does Protocol 404 WiPe 02.10.26 carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; 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): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^o (Oxide): It runs Oxide, also known as uMod; EU (Europe): Its browser listing: Europe from Protocol 404 WiPe 02.10.26. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Protocol 404 WiPe 02.10.26 appear in Rust Metrics lists and filters?

On Rust Metrics, Protocol 404 WiPe 02.10.26 sits in these lists: EU Rust servers, checked, Rust community servers: live readings and Vanilla Rust servers, live. Reading: server list filters. It comes up under Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Occupancy

Where does Protocol 404 WiPe 02.10.26 sit in the rankings?

Top 22% of all ranked servers: Protocol 404 WiPe 02.10.26 takes #4,977 on seven-day player hours and #1,696 in Europe.

What player count does Protocol 404 WiPe 02.10.26 carry?

Current headcount on Protocol 404 WiPe 02.10.26: 0 players, 100 slots available. Check: players over seven days. Average 0, peak 2. The last 48 hours peaked at 03:00 UTC, averaging 2 players at that hour.

Server details

What location is Protocol 404 WiPe 02.10.26 hosted in?

Protocol 404 WiPe 02.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. Check: address. It reads 95.188.71.57:28015.

What Rust version is Protocol 404 WiPe 02.10.26 on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by Protocol 404 WiPe 02.10.26. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for Protocol 404 WiPe 02.10.26?

Reading: 90 server fps on average across the last 48 hours. It never dropped below 73. Peak entity count: 187,147. Buildings, deployables and all else included. Reading: 3,682 MB of memory at the highest. Expect lag when fps falls and entities climb.

Is Protocol 404 WiPe 02.10.26 up, and how often does it stay up?

Reading: online. Protocol 404 WiPe 02.10.26 answers right now. Reading: uptime. About 17 hours ago it restarted, on its own count. Uptime for the last 7 full days: 161 of 168 hours, or 96%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Protocol 404 WiPe 02.10.26?

No gather rate appears in the name: Protocol 404 WiPe 02.10.26. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Plugin count: Oxide. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. Anti-cheat reading: VAC on, Valve's system.

What map is Protocol 404 WiPe 02.10.26 on?

From seed 11, the game generates the procedural map on Protocol 404 WiPe 02.10.26. Its size is 5,600. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How can you get onto Protocol 404 WiPe 02.10.26?

Check: join. Open Rust, press F1, then enter client.connect 95.188.71.57:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
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 Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

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

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.

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.