Rust Player Count
45,504 playing now

Online185.189.255.72:35200checked 10m ago

#5 Wasilisc PvE х3

weekly wipes moddedoxidepve
Players now 0/ 200 0% full
7-day average 0 peak 3
Rank #5,170 top 23%
Last wipe 6d ago weekly schedule
Next wipe 14h Thu 15 Oct, 15:17 UTC

Players

AveragePeak
00.511.5201:0010:0019:0005:0014:0023:00

Hourly average and peak, UTC.

Server performance

02040608001:0010:0019:0005:0014:0023: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.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Wipe schedule

fixed weekdays

Next wipe Thursday 15 October, 15:17 UTC, in 14h. Every Thursday at 15:17 UTC · medium confidence

Usual gap 7 days between real wipes
On rhythm 75% of its recent wipes
Wipe-day peak 3 players, last three wipes
Crowd held 0% else halves by day 5

Coming wipes

14hThu 15 Oct, 15:17 UTC
7d 14hThu 22 Oct, 15:17 UTC
14d 14hThu 29 Oct, 15:17 UTC
21d 18hThu 5 Nov, 19:00 UTC FW
28d 14hThu 12 Nov, 15:17 UTC
35d 14hThu 19 Nov, 15:17 UTC
42d 14hThu 26 Nov, 15:17 UTC

The first 48 hours of its last wipes

Thu 8 OctThu 1 OctThu 24 Sep
01234+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 15:17 UTC6d ago 3 – running 0
Thu 1 Oct, 15:12 UTC13d ago 3 halved by day 5 7 days 1
Thu 24 Sep, 15:12 UTC20d ago 3 halved by day 6 7 days 0
Thu 17 Sep, 17:03 UTC27d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#3 Wasilisc PvE х5EU · groups of 8+ · weekly · 6 on average 1/ 200
TRINUM.RU PVE NoKill NoRaid Skills Artifacts Boss ZombieEU · groups of 8+ · weekly · 5 on average 1/ 250
[GUA] MODDED 2Х | PVE | MAP WIPE 11.10EU · groups of 64+ · weekly · 2 on average 1/ 200
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 199 on average 117/ 2000
1[PvE]Тульский|Русский|Classic+ИвентыEU · groups of 8+ · monthly · 74 on average 18/ 200
[EU] Salty Zombies PvE #1 | Skills | Raid | Quests | Jetpack | EU · groups of 8+ · monthly · 51 on average 25/ 150

Quick answers

from the figures on this page

Rules and settings

What configuration does #5 Wasilisc PvE х3 use?

The name of #5 Wasilisc PvE х3 does not state a gather rate. The group limit is the game's default of 8 players. The server runs pve, other players cannot be fought. The server browser lists it under Modded, because plugins or settings alter the game. Plugins: Oxide. Anti-cheat VAC from Valve is on.

Which map is running on #5 Wasilisc PvE х3?

A procedural map of size 4,500 is what #5 Wasilisc PvE х3 runs, generated by the game with seed 1509524579. The map is identical for the same size and seed, so it can be viewed on RustMaps from this page. Its map is called: Custom Map.

Tags, lists and filters

Where can #5 Wasilisc PvE х3 be found in Rust Player Count lists and filters?

The Rust Player Count lists that #5 Wasilisc PvE х3 fits are: EU Rust servers, Modded Rust servers and Rust PvE servers. You can find it on the server list using these filters: 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.

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

The game's server browser reads these tags from #5 Wasilisc PvE х3: gmrust (Game mode): Survival as standard in Rust; mp200 (Max players): 200 slots are available; ts8 (Group limit): Teams max out at 8, the standard game limit; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, Rust's standard one; $r? (Region code): The region code field is empty; ^w (Weekly): A wipe takes place each week; ^p (PvE): No player-versus-player combat: the environment provides the danger; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): It appears under Modded because plugins or settings modify the game. The tags also include its current players, its queue and when its world was made, shown at the top of this page.

Player numbers

What is the player count on #5 Wasilisc PvE х3?

Right now, 0 players are on #5 Wasilisc PvE х3, which has 200 slots. With a peak of 3, the average over seven days is 0 players. The highest average in the last 48 hours was 1 players at 15:00 UTC.

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

For player hours in the last seven days, #5 Wasilisc PvE х3 ranks #5,170 and is in the top 23% of all ranked servers.

About the server

What is the uptime and reliability of #5 Wasilisc PvE х3?

#5 Wasilisc PvE х3 is currently online. Based on the uptime it reports, the last restart was about 20 hours ago. For the last 7 full days, it was online for 144 of 168 hours, a 86% uptime. Its first appearance in Rust Player Count was on 13 September 2026.

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

Windows hosts #5 Wasilisc PvE х3, which runs Rust network protocol 2634 and build 167781. Joining requires the same protocol on your game; Steam updates it for you.

What is the location of #5 Wasilisc PvE х3?

Its name points to Europe, even though #5 Wasilisc PvE х3 publishes no region tag. Rust Player Count displays the location a server claims, not the physical location of the machine. It is located at 185.189.255.72:35200.

How well does #5 Wasilisc PvE х3 perform?

The server ran at an average of 58 fps over the last 48 hours, never falling below 47. The maximum number of entities it carried was 131,370, which includes buildings, deployables and everything else. Memory usage reached up to 4,271 MB. A climbing entity count and low fps are felt as lag by players.

Wipe days

What changes on #5 Wasilisc PvE х3 on wipe day?

The average busiest point in recent wipes reached 3 players. 40 hours after the latest wipe, the crowd hit its peak. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. If not, the crowd went below half by day 5.

What wipe pattern does #5 Wasilisc PvE х3 follow?

Wipes on #5 Wasilisc PvE х3 follow a every Thursday at 15:17 UTC pattern. On Thursday 15 October at 15:17 UTC the next wipe is expected. It has been running its current world for 6 days 9 hours. According to its tags, wipes are scheduled weekly.

How to join

What is the process to join #5 Wasilisc PvE х3?

Joining is done by opening the console (F1) and running client.connect 185.189.255.72:35200. Another way is the Launch Rust option on this page, which uses Steam to start Rust and put you in. For more, visit its website at https://wasilisc.ru/cookies.html?backurl=http://wasilisc.ru/?try=3.

Server tags

what each one means

Published as mp200,ptrak,$r?,v2634,^w,^p,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival as standard in Rust.
mp200
Max players 200 slots are available.
ts8
Group limit Teams max out at 8, the standard game limit.
v2634
Protocol To join, your game must match protocol 2634.
cs167781
Build Build number: 167781.
ptrak
Networking The network layer is RakNet, Rust's standard one.
$r?
Region code The region code field is empty.

Wipe schedule

^w
Weekly A wipe takes place each week.

Gameplay

^p
PvE No player-versus-player combat: the environment provides the danger.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) is in use.
^z
Modded It appears under Modded because plugins or settings modify 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.