S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2
185.189.255.207:35100EUUp, checked 11m agoMonitored since 13 Sep 2026
Health checks
from the latest readings- ReachableOn the Steam server list, checked 11m agoPassing
- Capacity0% of 200 slots in usePassing
- Queuenobody waitingPassing
- Performancerunning at 109 fpsPassing
- Fresh mapwiped 6d agoPassing
- Next wipeThu 5 Nov, 19:00 UTC, in 27d 21hPassing
Activity
players each hour, last 48- Group limit
- 100 max
- Wipe schedule
- monthly
- Map
- Procedural Map · 3500
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- 1Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 717 on average697 / 750
- 2Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 648 on average469 / 500
- 3MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10EU · groups of 300+ · 2x · monthly · 429 on average227 / 500
- 4Magic Rust #27 — Vanilla 2x (Monthly) | PyccкийEU · groups of 150+ · 2x · monthly · 423 on average225 / 300
- 5EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 366 on average318 / 350
- 6EU Limitless 2x Monthly Main | No BP Wipes | x2EU · groups of 12+ · 2x · monthly · 258 on average235 / 245
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Rank
daily · 1 is bestTop 30% of all ranked servers, top 65% in EU. Ranked on player hours over the last seven days.
Performance
48 hours: hourly readings. 30 to 90 days: a point a day, measured since 17 Sep. Low fps and a climbing entity count mean lag.
Wipe calendar
2 days with a wipe in the last 16 weeksIn 27d 21h. The force wipe · high confidence
- usual gap
- 14.1 days between real wipes
- wipe-day peak
- 2 players, last three wipes
- crowd held
- 0% else halves by day 1
The first 48 hours of its last wipes
-
2 Oct
Fri 17:39 UTC peak 4 · running
-
18 Sep
Fri 14:23 UTC peak 1 · lasted 14.1 days
- Address
- 185.189.255.207:35100
- Region
- EU
- Max players
- 200
- Group limit
- 100 max
- Wipe schedule
- monthly
- Last wipe
- 2 Oct 2026, 17:39 UTC
- Hostname
- s1.diyaland.shop
- First seen
- 13 Sep 2026
The only server publishing a diyaland.shop hostname.
Server tags
What each tag it publishes means. Published as mp200,ptrak,$r?,v2634,^m,EU,gmvanilla,cs166652,ts100,^o^z.
gmvanillaGame mode Survival in the vanilla style.mp200Max players The slot count is 200.ts100Group limit Each team can have at most 100 players.v2634Protocol Your game must be on protocol 2634 to join.cs166652Build The game build is 166652.ptrakNetworking The network layer is RakNet, the game's standard.$r?Region code A region code is not set.^mMonthly A monthly wipe happens, together with Facepunch's force wipe.^oOxide A plugin framework, Oxide (uMod), is in use.^zModded Plugins or settings change the game, so it is listed under Modded.EUEurope The server browser lists it under Europe.Flag meanings are Facepunch's.
Player count
What is the rank of S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
In Europe, S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 holds position #1,892, while its seven-day player hours rank #6,907 overall, within the top 30% of ranked servers.
What is the player count on S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
At the moment, 0 of 200 slots on S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 are filled. The average over seven days is 0 players, peaking at 4. Over the past 48 hours, the peak hour was 20:00 UTC, averaging 0 players.
Rules and settings
What is the map on S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
The map on S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 is procedural, size 3,500 with seed 1059853669, created by the game. You can look at the map on RustMaps from this page, as the same size and seed give the same result.
What settings and rules apply on S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
2x gather applies here, taken from the server name S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2. The maximum group size is 100 players. survival is the mode, the usual game: gathering, building and raiding. Combat between players is allowed, and bases can be raided. The server browser lists it as Modded: plugins or settings change gameplay. The plugins it uses are Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
What can you expect from wipe day on S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
The average busiest count over recent wipes was 2 players. 26 hours after the latest wipe, the crowd reached its peak. Until the next wipe, the crowd remained above half the peak in 0% of recent wipes. In the other cases, numbers dropped below half by day 1.
What wipe pattern does S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 follow?
Once a month, at the force wipe, S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 wipes. The force wipe on Thursday 5 November at 19:00 UTC is the next wipe, and every Rust server wipes then. 6 days 3 hours is the age of the current world. The tags carry a monthly wipe schedule.
Server tags
Who is behind S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
The diyaland.shop hostname published by S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 is used by no other server we track.
What is the meaning of the tags on S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
The tags below come from S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 and are read by the game's server browser: gmvanilla (Game mode): Survival in the vanilla style; mp200 (Max players): The slot count is 200; ts100 (Group limit): Each team can have at most 100 players; v2634 (Protocol): Your game must be on protocol 2634 to join; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code is not set; ^m (Monthly): A monthly wipe happens, together with Facepunch's force wipe; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings change the game, so it is listed under Modded; EU (Europe): The server browser lists it under Europe. The tags also carry its current players, its queue and when its world was made, all shown at the top of this page.
What lists and filters on Best Rust Servers hold S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
The Best Rust Servers lists that S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 fits are: 2x Rust servers, Europe Rust servers and Best modded Rust servers. You will find it on the server list under: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week; Gather rate: 2x.
About the server
What Rust version does S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 run?
Rust network protocol 2634 and build 166652 on Windows is what S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 runs. Steam updates your game to the same protocol required for joining.
Where can S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 be found?
In Europe, S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 lists itself with its EU tag. Where a server says it is, that is what Best Rust Servers shows; it does not look up the machine's location. 185.189.255.207:35100 is its address.
What is the performance like on S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
In the last 48 hours, the server averaged 131 fps, with a minimum of 86. The world contained up to 71,459 entities, such as buildings, deployables and other items. Memory peaked at 2,847 MB. Lag, as felt by players, is caused by low fps and an increasing number of entities.
What is the online status and reliability of S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
The server S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2 is currently online. Based on the uptime it reports, the last restart was roughly 3 days ago. In the last 7 full days, 168 of 168 hours were online, an uptime of 100%. Best Rust Servers recorded its first appearance on 13 September 2026.
Join the server
How do you connect to S1.DIYALAND.SHOP | WIPE 02.10 | NO LIMIT | X2?
Use Launch Rust on this page to open Rust through Steam and connect, or press F1 in Rust and enter client.connect 185.189.255.207:35100 in the console.
