RUST METRICSFlight deck · live data
Data live Servers11,786 Players66,925 Populated3,511 Fresh wipes 3 h190 Scan5 min
‹ All servers185.189.255.72:35200
Online Full Queue Fresh wipe Wipe due No query

#5 Wasilisc PvE х3

Online 185.189.255.72:35200 checked 7m ago

weekly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 11:00 UTC
0 50 100 150 200 PAX 0 /200

Players now

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

Server fps

48 h low 34 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 132,122 ×1000

Entities

48 h range 125,848–137,642 · memory 3,913 MB
1239 ET SINCE RESTART 07:57

Uptime

7 h 57 min since its last restart, at the last reading
7-day average1peak 6
Rank#3,203top 14%
Last wipe6d agoweekly schedule
Next wipe2hThu 29 Oct, 15:18 UTC
Memory3,913MB48 h peak 3 players
REC 1

Players

AveragePeak
0123413:0022:0007:0016:0002:0011:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608013:0022:0007:0016:0002:0011: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
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 14% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

fixed weekdays

Next wipe Thursday 29 October, 15:18 UTC, in 2h. Every Thursday at 15:18 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm83%of its recent wipes
wipe-day peak5players, last three wipes
crowd held0%else halves by day 4

Coming wipes

  1. WPT 1Thu 29 Oct, 15:18 UTC2h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 6hFW
  3. WPT 3Thu 12 Nov, 15:18 UTC14d 2h
  4. WPT 4Thu 19 Nov, 15:18 UTC21d 2h
  5. WPT 5Thu 26 Nov, 15:18 UTC28d 2h
  6. WPT 6Thu 3 Dec, 19:00 UTC35d 6hFW
  7. WPT 7Thu 10 Dec, 15:18 UTC42d 2h

The first 48 hours of its last wipes

Thu 22 OctThu 15 OctThu 8 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 4 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 15:18 UTC6d ago 6 – running 1
Thu 15 Oct, 15:22 UTC13d ago 5 halved by day 4 7 days 0
Thu 8 Oct, 15:17 UTC20d ago 3 halved by day 3 7 days 0
Thu 1 Oct, 15:12 UTC27d ago 3 halved by day 5 7 days 1
Thu 24 Sep, 15:12 UTC34d ago 3 halved by day 6 7 days 0
Thu 17 Sep, 17:03 UTC41d ago 4 halved by day 3 6.9 days 3

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 #5 Wasilisc PvE х3?

An average of 5 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 4 hours. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 4 it fell below half when it didn't.

When does #5 Wasilisc PvE х3 wipe?

The wipe rhythm of #5 Wasilisc PvE х3 is every Thursday at 15:18 UTC. Thursday 29 October at 15:18 UTC is when its next wipe is due. The world it runs now was made 6 days 21 hours ago. Its tags carry a weekly wipe schedule.

Tags

How should you read the tags on #5 Wasilisc PvE х3?

These are the tags #5 Wasilisc PvE х3 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp200 (Max players): Slots: 200; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^w (Weekly): Check: wipe cycle. Every week; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does #5 Wasilisc PvE х3 appear in Rust Metrics lists and filters?

On Rust Metrics, #5 Wasilisc PvE х3 sits in these lists: EU Rust servers, checked, Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Weekly ^w, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week.

Population

Where does #5 Wasilisc PvE х3 sit in the rankings?

Player hours over seven days put #5 Wasilisc PvE х3 at #3,203, in the top 14% of all ranked servers.

What player count does #5 Wasilisc PvE х3 carry?

0 of 200 slots are filled on #5 Wasilisc PvE х3 right now. Check: players over seven days. Average 1, peak 6. The last 48 hours peaked at 17:00 UTC, averaging 3 players at that hour.

Operator and location

Which location does #5 Wasilisc PvE х3 run from?

Reading: location. Nothing in the tags, but the name of #5 Wasilisc PvE х3 points to Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 185.189.255.72:35200.

What Rust version is #5 Wasilisc PvE х3 on?

Reading: #5 Wasilisc PvE х3, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.

How does #5 Wasilisc PvE х3 perform?

Over the last 48 hours the average was 50 server fps; the floor was 34. Check: entities. The peak was 137,642, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 4,928 MB. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on #5 Wasilisc PvE х3, and is it online?

#5 Wasilisc PvE х3 reports online. Status: normal. By its reported uptime, the last restart was roughly 7 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does #5 Wasilisc PvE х3 enforce, and what are its settings?

Reading the name gives no gather rate for #5 Wasilisc PvE х3. The group cap is 8 players, which is the default in the game. The mode is pve. Note the following: no combat against other players. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

What map is #5 Wasilisc PvE х3 on?

Check: map. Procedural, size 4,500, seed 1509524579, generated by the game on #5 Wasilisc PvE х3. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Custom Map.

Join

How do you connect to #5 Wasilisc PvE х3?

Check: join. Open Rust, press F1, then enter client.connect 185.189.255.72:35200. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://wasilisc.ru/cookies.html?backurl=http://wasilisc.ru/?try=3 is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2635,^w,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp200
Max players Slots: 200.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

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

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.