Online 185.189.255.68:35500 checked 8m ago
Wasilisc test map
Connect
srv = rust.server("185.189.255.68:35510")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Sunday 1 November, 11:59 UTC, in 4d 16h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 4d 16h | Sun 1 Nov, 11:59 UTC | wipe |
| 1 | 8d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 11d 16h | Sun 8 Nov, 11:59 UTC | wipe |
| 3 | 18d 16h | Sun 15 Nov, 11:59 UTC | wipe |
| 4 | 25d 16h | Sun 22 Nov, 11:59 UTC | wipe |
| 5 | 32d 16h | Sun 29 Nov, 11:59 UTC | wipe |
| 6 | 36d 23h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 39d 16h | Sun 6 Dec, 11:59 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 11:59 UTC23d ago | 0 | NaN | running | 0 |
| 1 | Sun 27 Sep, 18:00 UTC30d ago | 1 | halved by day 1 | 6.7 days | 0 |
| 2 | Wed 23 Sep, 17:50 UTC34d 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.
display(srv.map, srv.info())Map
4500 · seed 2147483647
- map
- Custom Map
- size
- 4500
- seed
- 2147483647
Server
srv.info()- address
- 185.189.255.68:35500
- region
- –
- max players
- 100
- group limit
- 10 max
- wipe schedule
- weekly
- last wipe
- 4 Oct 2026, 11:59 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 124/100 |
| 1 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 111 on average | 191/225 |
| 2 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 30/200 |
| 3 | [NA] Willjum's Solo Only | Thursday Wipes | NA · groups of 8+ · weekly · 26 on average | 14/100 |
| 4 | [EU] Willjum's Solo Only | Thursday Wipes | EU · groups of 8+ · weekly · 25 on average | 28/175 |
| 5 | QS『芬达』100000倍/10.27/枪战/蓝图全解/萌新/建造 | EA · groups of 20+ · weekly · 23 on average | 29/100 |
Quick answers
From the figures on this page.
Population data
How does Wasilisc test map compare in the rankings?
Player hours over seven days put Wasilisc test map at #15,383, in the top 70% of the ranked set.
How full does Wasilisc test map run?
Current row: 0 players on Wasilisc test map, against 100 slots. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on Wasilisc test map?
Server fps over the last 48 hours averages 48; the floor is 41. Entity numbers reached 120,178, and that includes buildings, deployables and the rest. The memory field tops out at 4,952 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on Wasilisc test map?
Rust network protocol 2635 and build 168909 on Windows is what Wasilisc test map runs. Steam updates your game for you, but the protocol must match to join.
Is Wasilisc test map up, and what does its uptime show?
Online is the state at the latest refresh for Wasilisc test map. The uptime it reports puts the last restart about 4 days 19 hours ago. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does Wasilisc test map run from?
No region is published by Wasilisc test map. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 185.189.255.68:35500.
Rules, settings, map
What rules and settings are recorded for Wasilisc test map?
No gather rate appears in the name: Wasilisc test map. The cap on a group is 10 players. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Wasilisc test map selected?
Size 4,500, seed 2147483647: the procedural map on Wasilisc test map, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.
Wipes and dates
On what schedule does Wasilisc test map wipe?
Too few wipes are on record for Wasilisc test map to confirm its schedule, so the tag drives the prediction. Sunday 1 November at 11:59 UTC is when the next wipe is due. A new world was started 23 days 7 hours ago, and that is the one in play. A weekly wipe schedule is published in its tags.
On Wasilisc test map, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 1 in the other cases.
Lists and tags
Which Rust Data filters and lists contain Wasilisc test map?
The Rust Data lists that Wasilisc test map fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
How should you read the server tags on Wasilisc test map?
These tags are published by Wasilisc test map and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts10 (Group limit): No team may exceed 10; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^w (Weekly): The interval is one week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into Wasilisc test map?
Enter client.connect 185.189.255.68:35500 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://wasilisc.ru/cookies.html?backurl=http://wasilisc.ru/?try=3.