On the class lists: F (35), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,323top 69%
Last wipe24d agoweekly schedule
Next wipe3d 0hSun 1 Nov, 11:59 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,323 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
81/ 100
B+
Mostly smooth: 48 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
48/ 100
D
Slipped a little: down 696 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population is 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 69% 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···W
······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 Sunday 1 November, 11:59 UTC, in 3d 0h.
Its weekly schedule tag · low confidence
usual gap5.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
Coming wipes
3d 0hSun 1 Nov, 11:59 UTC
7d 7hThu 5 Nov, 19:00 UTCFW
10d 0hSun 8 Nov, 11:59 UTC
17d 0hSun 15 Nov, 11:59 UTC
24d 0hSun 22 Nov, 11:59 UTC
31d 0hSun 29 Nov, 11:59 UTC
35d 7hThu 3 Dec, 19:00 UTCFW
38d 0hSun 6 Dec, 11:59 UTC
The first 48 hours of its last wipes
Sun 4 OctSun 27 SepWed 23 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 11:59 UTC24d ago
0
–
running
0
Sun 27 Sep, 18:00 UTC31d ago
1
halved by day 1
6.7 days
0
Wed 23 Sep, 17:50 UTC35d ago
1
halved by day 1
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Wasilisc test map leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 185.189.255.68:35500 is the address to use.
Is Wasilisc test map up, and how steady is its uptime?
Right now, Wasilisc test map is online. The uptime it reports puts the last restart at about 34 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Does Wasilisc test map perform well?
The average over the last 48 hours was 48 server fps, and it never went below 33. Buildings, deployables and everything else in the world added up to as many as 121,851 entities. Up to 4,816 MB of memory was used. Players feel lag when fps drops and entities pile up.
Which Rust version is Wasilisc test map running?
You will find Wasilisc test map on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Wasilisc test map wipe, and how often?
Too few wipes on Wasilisc test map are recorded to confirm the schedule, so its tag guides the prediction. Expect the next wipe on Sunday 1 November at 11:59 UTC. The world it runs now was created 24 days 23 hours. The tags carry a weekly wipe schedule.
What happens on Wasilisc test map when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Population
Where does Wasilisc test map place in the wider field of Rust servers?
Over the last seven days, Wasilisc test map has #15,323 for player hours, in the top 69% of all ranked servers.
What does the population on Wasilisc test map look like?
With 100 slots available, Wasilisc test map currently has 0 players. A seven-day average of 0 players applies here.
Lists and filters
What do Wasilisc test map's tags stand for?
The game's browser takes its cue from the tags Wasilisc test map has set: gmvanilla (Game mode): You play vanilla survival here; mp100 (Max players): 100 slots are available; ts10 (Group limit): No team may go above 10; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. 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 Wasilisc test map?
These Rust Server Score lists count Wasilisc test map among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
Server rules
How is Wasilisc test map set up, and what rules does it keep?
Nothing in the name of Wasilisc test map states a gather rate. The limit for a group is 10 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Wasilisc test map runs which map?
Wasilisc test map runs a game-generated procedural map at size 4,500, seed 2147483647. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.
Getting in
What is the way to join Wasilisc test map?
Enter client.connect 185.189.255.68:35500 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://wasilisc.ru/cookies.html?backurl=http://wasilisc.ru/?try=3.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,gmvanilla,cs168909,ts10,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp100
Max players100 slots are available.
ts10
Group limitNo team may go above 10.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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+); population is the one to work on (F).