Element card · group Modded · atomic number 2,969, its rank
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Online EU 85.233.150.44:35015 checked 8m ago
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 best
Top 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 UTC, in 15h. Every 7 days 4 hours · medium confidence
Coming wipes
- 15hFri 30 Oct, 15:34 UTC
- 6d 19hThu 5 Nov, 19:00 UTCFW
- 7d 19hFri 6 Nov, 19:21 UTC
- 14d 23hFri 13 Nov, 23:08 UTC
- 22d 3hSat 21 Nov, 02:54 UTC
- 29d 6hSat 28 Nov, 06:41 UTC
- 34d 19hThu 3 Dec, 19:00 UTCFW
- 36d 10hSat 5 Dec, 10:28 UTC
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 UTC6d ago | 3 | – | running | 0 |
| Fri 16 Oct, 08:01 UTC13d ago | 3 | halved by day 6 | 7.2 days | 0 |
| Thu 8 Oct, 16:08 UTC21d ago | 4 | held half | 7.7 days | 0 |
| Fri 2 Oct, 12:57 UTC27d ago | 5 | halved by day 5 | 6.1 days | 0 |
| Fri 25 Sep, 03:34 UTC34d ago | 4 | held half | 7.4 days | 0 |
| Thu 17 Sep, 19:34 UTC42d 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 wipesQuick answers
from the figures on this pageMap and rules
What map is in play on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
A procedural map of size 3,700 with seed 262731628 runs on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], generated by the game. You can view it on RustMaps from this page, since matching size and seed produce the same map.
What settings and rules apply on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] carries a 10x gather rate, as its name states. Eight players per group is the limit, the game's default. Play runs as survival, raiding, building and gathering: the standard game. Fighting and raiding between players are allowed. The server browser lists it under Modded, where plugins or settings change the game. Plugins in use: Oxide. Anti-cheat is on: Valve's VAC.
Server details
Which location is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] based in?
The EU tag is how Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself, in Europe. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. You will find it at 85.233.150.44:35015.
What Rust version does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] currently run?
On Linux, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is running Rust network protocol 2635 and build 168909. Your game needs to match the protocol to join, and Steam updates it automatically.
How reliably does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] stay online?
At the moment, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is online. According to the uptime it reports, the last restart was about 2 days 21 hours ago. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. The first sighting by Rust Data Lab was on 13 September 2026.
How well does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] perform?
Server fps averaged 57 over the last 48 hours, with 22 as the lowest. Buildings, deployables and everything else in the world added up to as many as 87,459 entities. Up to 3,931 MB of memory was used. Lag, as players feel it, is caused by low fps and an increasing entity count.
Wipe schedule
When does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] wipe, and how often?
Lately the gap between wipes on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has averaged about 7.3 days. Due next on Friday 30 October at 15:34 UTC is its wipe. The world it is running now dates from 6 days 12 hours ago. A two-weekly wipe schedule is published in its tags.
How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] look on the day of a wipe?
At their busiest, recent wipes averaged 3 players. 6 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 60% of its recent wipes. Where it did not hold, the crowd dropped below half by day 5.5.
Where it appears
What should you understand from the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] carries?
The game's server browser reads the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] publishes, which are gmrust (Game mode): Standard Rust survival is the game here; mp100 (Max players): Player slots: 100; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): It runs build 168909; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): The region field is left blank; ^b (Biweekly): The map wipes on a two-week cycle; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded; EU (Europe): In the browser it sits under Europe. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.
Where among the Rust Data Lab lists and filters does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] come up?
The Rust Data Lab lists that include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] are: 10x Rust servers, counted live, EU Rust servers, measured and Modded Rust servers, measured. Applying these filters on the server list returns it: 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 does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] compare with other servers in the rankings?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is #2,969 on seven-day player hours, #1,122 in Europe, and in the top 13% of all ranked servers.
What does the current player count on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] tell you?
At the moment Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has 0 of its 100 slots filled. The week's figures average 1 players and top out at 8. The busiest point in the last 48 hours came at 15:00 UTC, averaging 6 players.
Getting on
How can you connect to Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Open the console with F1 in Rust and type client.connect 85.233.150.44:35015. The Launch Rust button on this page does the same job through Steam.