Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Online EU 85.233.150.44:35015 checked 10m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 16% of all ranked servers, top 45% in EU. Ranked on player hours over the last seven days.
Wipe schedule
a steady gapNext wipe Friday 30 October, 15:34 UTC, in 2d 6h. Every 7 days 4 hours · medium confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 2d 6h | Fri 30 Oct, 15:34 UTC | its own |
| 8d 9h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 9d 10h | Fri 6 Nov, 19:21 UTC | its own |
| 16d 13h | Fri 13 Nov, 23:08 UTC | its own |
| 23d 17h | Sat 21 Nov, 02:54 UTC | its own |
| 30d 21h | Sat 28 Nov, 06:41 UTC | its own |
| 36d 9h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 38d 1h | Sat 5 Dec, 10:28 UTC | its own |
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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 11:47 UTC4d 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 UTC19d ago | 4 | held half | 7.7 days | 0 |
| Fri 2 Oct, 12:57 UTC25d 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 UTC40d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop] | EU · groups of 8+ · 10x · biweekly · 77 on average | 63 / 150 |
| PROSTOJ CLASSIC #5 [X10|SKINS] | EU · groups of 100+ · 10x · biweekly · 10 on average | 4 / 100 |
| [EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTS | EU · groups of 8+ · 10x · biweekly · 3 on average | 3 / 50 |
| Turbo Rust 10x | PvP | MyMini | SkinBox | x10 | EU · groups of 20+ · 10x · biweekly · 2 on average | 0 / 200 |
| Atlas - EU 10x | No BPs | Kits | Shop | EU · groups of 20+ · 10x · weekly · 340 on average | 238 / 250 |
| KRAKEN | X10 | EU | KITS | RP | FPS+ | EU · groups of 14+ · 10x · weekly · 149 on average | 98 / 400 |
Quick answers
from the figures on this pageWipe data
When does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] wipe?
About every 7.3 days is how often Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has wiped lately. Friday 30 October at 15:34 UTC is when its next wipe is due. The current world dates from 4 days 21 hours. The tags carry an every-two-weeks wipe schedule.
Wipe day on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: what should you expect?
Recent wipes averaged a busiest count of 3 players. The highest player count on the latest wipe arrived 6 hours in. Recent wipes held the crowd above half that peak until the next wipe in 60% of cases. The fall below half arrived by day 5.5 when it didn't hold.
Server details
In which region does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] sit?
In Europe, according to its EU tag, sits Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. The address of the server is 85.233.150.44:35015.
Which Rust version is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on?
On Linux, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam handles the update.
Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] up, and how steady is its uptime?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] reports online at the current check. About 30 hours ago is when it last restarted, judged by its reported uptime. 100% uptime over the last 7 full days, equal to 168 of 168 hours. It entered Rust Server Analytics records on 13 September 2026.
What performance does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] show?
Server fps averaged 58 over the last 48 hours, with a floor of 33. At its highest the entity count was 88,778, including buildings, deployables and all else. Peak memory was 3,365 MB. Players experience lag as low fps combined with a rising entity count.
Tags
How should the tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] be read?
Tags from Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^b (Biweekly): A two-week wipe cycle; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Plugins or settings change the game, so it sits under Modded; EU (Europe): Its browser listing sits in Europe. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On Rust Server Analytics, which lists and filters feature Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
The following Rust Server Analytics lists count Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] among their servers: 10x Rust servers, EU Rust servers: live population data and Modded Rust servers: live data. 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.
Population
Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] sit among Rust servers?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] holds #3,492 on seven-day player hours and #1,304 in Europe, inside the top 16% of the ranked field.
How many players does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] carry?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] holds 0 players of its 100 slots as of the latest update. The seven-day mean is 1 players, against a peak of 6. Averaged over 48 hours, activity is highest at 19:00 UTC with 4 players.
Map and rules
What are the settings on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], and its rules?
10x gathering is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] states in its name. No custom group limit: 8 players is the standard. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. The Modded category lists it; plugins or settings change the game. The plugin framework is Oxide. Anti-cheat status: VAC on.
What is the map for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
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]. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Connection
How can a player join Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
In the Rust console (F1), enter client.connect 85.233.150.44:35015. Launch Rust on this page also works, opening Rust through Steam and connecting you.