Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Online EU 85.233.150.44:35015 checked 6m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 15% of all ranked servers, top 42% in EU. Ranked on player hours over the last seven days.
Bx1Wipe schedule
a steady gapNext wipe Friday 30 October, 15:34 UTC, in 1d 18h. Every 7 days 4 hours · medium confidence
Coming wipes
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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 11:47 UTC5d ago | 3° | – | running | 0 |
| Fri 16 Oct, 08:01 UTC12d ago | 3° | halved by day 6 | 7.2 days | 0 |
| Thu 8 Oct, 16:08 UTC20d ago | 4° | held half | 7.7 days | 0 |
| Fri 2 Oct, 12:57 UTC26d ago | 5° | halved by day 5 | 6.1 days | 0 |
| Fri 25 Sep, 03:34 UTC33d ago | 4° | held half | 7.4 days | 0 |
| Thu 17 Sep, 19:34 UTC41d 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Its recent wipes drew an average peak of 3 players. 6 hours after the latest wipe, the crowd peaked. Above half the peak until the next wipe: that held in 60% of its recent wipes. By day 5.5 it was below half in the wipes that did not hold.
What is the wipe schedule on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
The recent gap between wipes on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is about 7.3 days. Due on Friday 30 October at 15:34 UTC: the next wipe. The world in play now was made 5 days 9 hours ago. A fortnightly wipe is listed in the tags.
Population
How busy is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
The current population of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is 3, against 100 slots. The average across the last seven days is 1 players; the peak reached 6. Its busiest point in the last 48 hours was 14:00 UTC, averaging 3 players.
How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] rank against other Rust servers?
Top 15% of ranked servers and #1,228 in Europe: that is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] at #3,307 for player hours over seven days.
Settings and rules
Which map does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run?
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]. From this page you can view the map on RustMaps, since the same size and seed give the same map.
What are the rules and settings on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
10x gather is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] advertises in its name. The group limit is 8 players, which is the game's default. The server runs survival, gather, build and raid in the standard game. You can fight other players and raid their bases. Plugins or settings change the game, and it is listed under Modded in the server browser. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, turned on.
Server details
Which version of Rust does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run?
The build on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is Rust network protocol 2635 and build 168909, running on Linux. Your game must run the same protocol to join, and Steam takes care of updating it.
Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] online, and how reliable is it?
Online now: Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. About 39 hours ago is when it last restarted, by its own uptime figure. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. Rust Heatmap has had it on record since 13 September 2026.
Where is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] located?
With its EU tag, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself in Europe. Rust Heatmap shows the location a server states. It does not look up the machine's location. To connect, use 85.233.150.44:35015.
Does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run smoothly?
The last 48 hours brought an average of 58 server fps and a floor of 22. The world held as many as 88,778 entities, buildings and deployables included. At its peak it held 3,563 MB of memory. Lag, as players experience it, comes from low fps and a rising entity count.
Tags
Which Rust Heatmap lists and filters include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
These Rust Heatmap lists include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 10x Rust servers, EU Rust servers, busiest first and Modded Rust servers, by live population. Filtering the list by 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 brings it up.
What do the server tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] mean?
The game's server browser reads the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] publishes: gmrust (Game mode): Survival in the standard Rust form; mp100 (Max players): Slot count: 100; ts8 (Group limit): At most 8 per team: the default the game ships with; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): Build 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^b (Biweekly): Every two weeks the server wipes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Listed as Modded, since settings or plugins change the game; EU (Europe): The server browser lists it under Europe. The top of this page also shows the tags for players now, the queue and when the world was made.
How to join
How do I join Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Enter client.connect 85.233.150.44:35015 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you.