On the class lists: D (46), with population over 48 hours and no performance mark.
Players now1/ 2000% full
7-day average3peak 14
Rank#1,707top 8%
Last wipe14d agobiweekly schedule
Next wipedueThu 29 Oct, 15:19 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 3 of 200 on average. Plenty of space to grow.
Standingrank on player hours
92/ 100
A
Well up the rankings: #1,707 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
66/ 100
C+
Slows down under load at times: 40 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
41/ 100
F
Slipped a little: down 299 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); wipes are the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 8% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
···F···
·······
···W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 15:19 UTCdue.
Its biweekly schedule tag · low confidence
usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak16players, last three wipes
crowd held0%else halves by day 8.5
Coming wipes
dueThu 29 Oct, 15:19 UTC
7d 3hThu 5 Nov, 19:00 UTCFW
13d 23hThu 12 Nov, 15:19 UTC
27d 23hThu 26 Nov, 15:19 UTC
35d 3hThu 3 Dec, 19:00 UTCFW
41d 23hThu 10 Dec, 15:19 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 OctThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 16, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 15:19 UTC14d ago
16
–
running
2
Thu 1 Oct, 18:11 UTCFW27d ago
16
halved by day 10
13.9 days
5
Thu 17 Sep, 17:03 UTC41d ago
17
halved by day 7
14 days
6
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
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for #1 Wasilisc PvE x1. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 185.189.255.72:35000.
Is #1 Wasilisc PvE x1 up, and how steady is its uptime?
The server is up: #1 Wasilisc PvE x1 is online now. According to its reported uptime, the last restart was about 10 hours ago. It was up 95% of the time over the last 7 full days, 159 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
How well does #1 Wasilisc PvE x1 run?
It averaged 40 server fps over the last 48 hours, with a low of 24. Buildings, deployables and everything else in the world added up to as many as 161,302 entities. At its highest, it used 5,247 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does #1 Wasilisc PvE x1 sit?
The server #1 Wasilisc PvE x1 is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does #1 Wasilisc PvE x1 reset?
Its tag sets the prediction, as the record holds too few of #1 Wasilisc PvE x1's wipes to confirm its schedule. It is due to wipe next on Thursday 29 October at 15:19 UTC. It has been running its current world for 14 days. Its tags give a wipe schedule of every two weeks.
What should you expect from wipe day on #1 Wasilisc PvE x1?
Across its recent wipes, the busiest moments averaged 16 players. The crowd on the latest wipe was largest 2 hours after it began. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 8.5.
Population
What position does #1 Wasilisc PvE x1 hold in the rankings?
Over the last seven days, #1 Wasilisc PvE x1 has #1,707 for player hours, in the top 8% of all ranked servers.
What does the population on #1 Wasilisc PvE x1 look like?
With 200 slots available, #1 Wasilisc PvE x1 currently has 1 players. Averaging 3 players over seven days, it peaked at 14. Over the last 48 hours, the peak hour was 17:00 UTC, averaging 6 players.
Tags and filters
How should you read the tags on #1 Wasilisc PvE x1?
You'll see #1 Wasilisc PvE x1 tagged with gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): Its slot count is 200; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^b (Biweekly): The server wipes on a two-week cycle; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature #1 Wasilisc PvE x1?
These Rust Server Score lists count #1 Wasilisc PvE x1 among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Gather rate: 1x.
Map and rules
What settings and rules apply on #1 Wasilisc PvE x1?
#1 Wasilisc PvE x1 sets gather at 1x, as its name suggests. The default of 8 players applies as the group cap. It runs pve, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
#1 Wasilisc PvE x1 runs which map?
A procedural map of size 4,500 and seed 145283435, generated by the game, is what #1 Wasilisc PvE x1 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Map.
Getting in
What is the way to join #1 Wasilisc PvE x1?
To connect, start Rust, press F1, and type client.connect 185.189.255.72:35000. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://wasilisc.ru/cookies.html?backurl=http://wasilisc.ru/?try=3.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2635,^b,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max playersIts slot count is 200.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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.
A term to build on. Strongest in uptime (A+); wipes are the one to work on (F).