Local forecast · EU
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Online EU 85.233.150.44:35015 checked 11m ago
Current conditions
observed 11m agoplayers now
0% full
- 7-day average
- 1
- peak 8
- Rank
- #2,974
- top 13% · #1121 in EU
- Last wipe
- 6d ago
- biweekly schedule
- Next wipe
- 17h
- Fri 30 Oct, 15:34 UK · 15:34 UTC
Next wipe
a steady gapFriday 30 October, 15:34 UK · 15:34 UTC
in 17h
Every 7 days 4 hours · medium confidence
Coming wipes
- Fri 30 Oct 15:34 UK · 15:34 UTC 17h
- Thu 5 Nov 19:00 UK · 19:00 UTC 6d 20h FW
- Fri 6 Nov 19:21 UK · 19:21 UTC 7d 21h
- Fri 13 Nov 23:08 UK · 23:08 UTC 15d 1h
- Sat 21 Nov 02:54 UK · 02:54 UTC 22d 4h
- Sat 28 Nov 06:41 UK · 06:41 UTC 29d 8h
- Thu 3 Dec 19:00 UK · 19:00 UTC 34d 20h FW
- Sat 5 Dec 10:28 UK · 10:28 UTC 36d 12h
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 13% of all ranked servers, top 38% in EU. Ranked on player hours over the last seven days.
Wipe schedule
a steady gapNext wipe Friday 30 October, 15:34 UK · 15:34 UTC, in 17h. Every 7 days 4 hours · medium confidence
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 6 hours in.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 12:47 UKFri 23 Oct, 11:47 UTC · 6d ago | 3 | – | running | 0 |
| Fri 16 Oct, 09:01 UKFri 16 Oct, 08:01 UTC · 13d ago | 3 | halved by day 6 | 7.2 days | 0 |
| Thu 8 Oct, 17:08 UKThu 8 Oct, 16:08 UTC · 21d ago | 4 | held half | 7.7 days | 0 |
| Fri 2 Oct, 13:57 UKFri 2 Oct, 12:57 UTC · 27d ago | 5 | halved by day 5 | 6.1 days | 0 |
| Fri 25 Sep, 04:34 UKFri 25 Sep, 03:34 UTC · 34d ago | 4 | held half | 7.4 days | 0 |
| Thu 17 Sep, 20:34 UKThu 17 Sep, 19:34 UTC · 42d ago | 2 | held half | 7.3 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageAbout the server
How smoothly does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run?
Across the last 48 hours the average was 57 server fps, with a floor of 22. At its peak the world had 87,606 entities, counting buildings, deployables and the rest. Memory use reached 3,931 MB at its peak. A falling fps and a rising entity count show up to players as lag.
How reliable is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], and is it online now?
You will find Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] online at the moment. Its reported uptime shows a restart about 2 days 19 hours ago. In the last 7 full days it stayed up 167 of 168 hours, 99% of the time. On 13 September 2026 it was first recorded by Rust Wipe Stats.
What location is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] based in?
In Europe is where Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself, using its EU tag. The location Rust Wipe Stats shows is the one the server claims; the machine's real position is not looked up. You can reach it at 85.233.150.44:35015.
What version of Rust is running on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
On Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] you will find Rust network protocol 2635 and build 168909, hosted on Linux. The protocol must match for you to join, and Steam keeps it updated.
Tags, lists and filters
How should you read the tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
For the game's server browser, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] publishes these tags: gmrust (Game mode): Standard survival, the Rust way; mp100 (Max players): It holds 100 players; ts8 (Group limit): Teams are at the game default of 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): It runs game build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region field is left blank; ^b (Biweekly): The cycle is two weeks between wipes; ^o (Oxide): It runs on Oxide, also called uMod, for plugins; ^z (Modded): Plugins or settings alter the game here, so it is listed under Modded; EU (Europe): Its place in the server browser is Europe. At the top of this page you can see the player count now, the queue and the world's creation time, all from the tags.
Which Rust Wipe Stats filters and lists carry Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
These Rust Wipe Stats lists include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 10x Rust servers, Rust servers in Europe and Modded Rust servers. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week; Gather rate: 10x.
Settings and rules
What map is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on?
A procedural map of size 3,700 with seed 262731628, generated by the game, runs on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. The same map comes from the same size and seed, and RustMaps shows it from this page.
Which settings and rules are in force on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] sets gather at 10x, according to its own name. The default of 8 players is the group limit here. It plays as survival, gather, build, raid: the standard game. Raiding and player combat are both allowed. Plugins or settings change the game here, and the browser files it under Modded. Plugin frameworks in use: Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
Which days and times does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] schedule its wipes for?
The recent gap between wipes on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has been about 7.3 days. Expect the next wipe on Friday 30 October at 15:34 UTC. The world it is running now dates from 6 days 10 hours. The tags say it wipes every two weeks.
What should you expect from wipe day on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
The average peak across its recent wipes was 3 players. 6 hours after the latest wipe, the crowd hit its peak. 60% of recent wipes kept more than half the peak until the next wipe. The fall below half came by day 5.5 when the crowd did not hold.
Population history
How many players does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hold?
Out of 100 slots, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has 0 filled right now. The seven-day average is 1 players, with a peak of 8. Its busiest point in the last 48 hours was 15:00 UTC, averaging 6 players.
What position does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hold among Rust servers?
Player hours over the last seven days rank Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] at #2,974, top 13% overall and #1,121 in Europe.
Getting in
What steps let you join Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Open the console in Rust with F1, then type client.connect 85.233.150.44:35015 to join. On this page, Launch Rust does the same through Steam.