RUST METRICSFlight deck · live data
Data live Servers11,782 Players67,928 Populated3,558 Fresh wipes 3 h196 Scan5 min
‹ All servers185.189.255.68:35500
Online Full Queue Fresh wipe Wipe due No query

Wasilisc test map

Online 185.189.255.68:35500 checked 11m ago

weekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 11:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 46 SERVER FPS

Server fps

48 h low 33 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 119,647 ×1000

Entities

48 h range 111,124–121,851 · memory 3,966 MB
1239 ET SINCE RESTART 1D 11H

Uptime

1 days 11 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,318top 69%
Last wipe25d agoweekly schedule
Next wipe2d 23hSun 1 Nov, 11:59 UTC
Memory3,966MBat the last reading
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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Sunday 1 November, 11:59 UTC, in 2d 23h. 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

  1. WPT 1Sun 1 Nov, 11:59 UTC2d 23h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 6hFW
  3. WPT 3Sun 8 Nov, 11:59 UTC9d 23h
  4. WPT 4Sun 15 Nov, 11:59 UTC16d 23h
  5. WPT 5Sun 22 Nov, 11:59 UTC23d 23h
  6. WPT 6Sun 29 Nov, 11:59 UTC30d 23h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 6hFW
  8. WPT 8Sun 6 Dec, 11:59 UTC37d 23h

The first 48 hours of its last wipes

Sun 4 OctSun 27 SepWed 23 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 11:59 UTC25d 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.

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 Wasilisc test map when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 1 it fell below half when it didn't.

What wipe timing does Wasilisc test map follow?

Its tag guides the prediction: too few of Wasilisc test map's wipes are on record to confirm its schedule. Sunday 1 November at 11:59 UTC is when its next wipe is due. 25 days ago the current world was made. The tags state a wipe schedule of one wipe a week.

Lists and filters

How should you read the tags on Wasilisc test map?

These are the tags Wasilisc test map publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp100 (Max players): Slots: 100; ts10 (Group limit): Team cap: 10; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^w (Weekly): Check: wipe cycle. Every week; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Wasilisc test map?

Rust Metrics lists featuring Wasilisc test map: Modded Rust servers, checked live. 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.

Occupancy

Where does Wasilisc test map sit in the rankings?

Player hours over seven days put Wasilisc test map at #15,318, in the top 69% of all ranked servers.

What is the population on Wasilisc test map?

0 of 100 slots are filled on Wasilisc test map right now. Seven-day reading: 0 players on average.

Server

What location is Wasilisc test map hosted in?

No region comes from Wasilisc test map. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 185.189.255.68:35500.

What Rust version is Wasilisc test map on?

Reading: Wasilisc test map, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

Is performance on Wasilisc test map within range?

Over the last 48 hours the average was 48 server fps; the floor was 33. Check: entities. The peak was 121,851, counting buildings, deployables and the rest of the world. Memory peak: 4,816 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is Wasilisc test map, and is it online now?

Wasilisc test map reports online. Status: normal. Reading: uptime. About 35 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What settings and rules apply on Wasilisc test map?

Reading the name gives no gather rate for Wasilisc test map. The cap on groups is 10 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

What map is Wasilisc test map on?

Check: map. Procedural, size 4,500, seed 2147483647, generated by the game on Wasilisc test map. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Map name, as listed: Custom Map.

Join

What do you do to join Wasilisc test map?

To join: start Rust, press F1 and type client.connect 185.189.255.68:35500. Or press Launch Rust here and Steam opens the game 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 mp100,ptrak,$r?,v2635,^w,gmvanilla,cs168909,ts10,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp100
Max players Slots: 100.
ts10
Group limit Team cap: 10.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.