Server profile · EU
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Online, with 0 of 100 players on; ranked #3,511 of every public Rust server, the top 16%. It last wiped 4d ago.
Online EU 85.233.150.44:35015 checked 10m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 16% of all ranked servers, top 45% in EU. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
A steady gap.
Next wipe Friday 30 October, 15:34 UTC, in 2d 12h. Every 7 days 4 hours · medium confidence
Coming wipes
- 2d 12hFri 30 Oct, 15:34 UTC
- 8d 15hThu 5 Nov, 19:00 UTCFW
- 9d 16hFri 6 Nov, 19:21 UTC
- 16d 20hFri 13 Nov, 23:08 UTC
- 23d 23hSat 21 Nov, 02:54 UTC
- 31d 3hSat 28 Nov, 06:41 UTC
- 36d 15hThu 3 Dec, 19:00 UTCFW
- 38d 7hSat 5 Dec, 10:28 UTC
The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 3, 6 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 11:47 UTC4d ago | 3 | – | running | 0 |
| Fri 16 Oct, 08:01 UTC11d 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 UTC32d ago | 4 | held half | 7.4 days | 0 |
| Thu 17 Sep, 19:34 UTC40d ago | 2 | held half | 7.3 days | 0 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe days
What should you expect on wipe day at Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
At their busiest, its recent wipes drew 3 players on average. The peak crowd on this wipe came 6 hours after it started. The crowd stayed above half that peak until the next wipe in 60% of its recent wipes. The cases that did not hold saw the crowd fall below half by day 5.5.
On what schedule does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] wipe?
The gap between wipes on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has averaged about 7.3 days recently. A wipe is expected on Friday 30 October at 15:34 UTC. The world you are playing on now was made 4 days 15 hours ago. Its tags carry an every-two-weeks wipe schedule.
About the server
Does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hold a steady frame rate?
The 48-hour average for server fps is 58, and 33 was the lowest seen. At its highest the entity count reached 88,778: buildings, deployables and everything else. Memory use peaked at 3,222 MB. A climbing entity count and low fps are what players experience as lag.
Which Rust version is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on?
Rust network protocol 2635 and build 168909 on Linux is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs. You can only join if your game is on the same protocol; Steam handles that update.
Has Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] stayed online, and is it up now?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is currently reachable and online. The uptime it reports puts the last restart at about 24 hours ago. The last 7 full days gave 168 of 168 hours up, or 100% of the time. Rust Insights first logged this server on 13 September 2026.
In which location does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] sit?
Its EU tag is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] uses to list itself in Europe. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. 85.233.150.44:35015 is where it answers.
Tags
How should you read the tags listed for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
When the game's server browser reads Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): It holds 100 slots; ts8 (Group limit): This is the game default: 8 per team at most; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): Build 168909 is what it runs; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is filed under Modded; EU (Europe): Find it in the browser under Europe. Current players, queue length and the age of the world sit in the tags as well, shown at the top of this page.
Which Rust Insights filters and lists feature Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
The Rust Insights lists that carry Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] are 10x Rust servers, by the numbers, Rust servers in Europe and Modded Rust servers, explained. 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
How many players are on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] right now?
At the time of this refresh, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] holds 0 players on 100 slots. A weekly average of 1 players goes with a peak of 6. The busiest point of the last 48 hours fell at 19:00 UTC, averaging 4 players.
How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] compare with other Rust servers in the ranking?
In Europe, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is #1,313; across all ranked servers it is #3,511 on seven-day player hours, in the top 16%.
Map and rules
How is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] configured, and what rules apply?
Going by its name, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] gathers at 10x. No group limit is set, so the game's default of 8 players applies. You get survival as the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. It is a Modded entry: plugins or settings modify the game. Plugins: Oxide run here. VAC is on: Valve's anti-cheat is active.
What is the map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
The game generates the map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: procedural, size 3,700, seed 262731628. You can look at the map on RustMaps from this page, since the same size and seed produce the same map.
Join
How do you connect to Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Type client.connect 85.233.150.44:35015 into the console, which you open with F1 in Rust. The Launch Rust button on this page does the same job by opening Rust through Steam.