Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]
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 bestTop 17% of all ranked servers, top 45% in EU. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 1 October, 18:00 UTC, in 2d 6h. The force wipe · high confidence
Coming wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 14 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 25 Sep, 03:34 UTC4d ago | 4 | – | running | 0 |
| Thu 17 Sep, 19:34 UTC11d 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 pageWipes
What is the wipe schedule on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Too few of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]'s wipes are on record to confirm its schedule, so the prediction follows its tag. Its next wipe is the force wipe on Thursday 1 October at 18:00 UTC, when every Rust server wipes. Its current world was made 4 days 8 hours ago. It publishes an every-two-weeks wipe schedule in its tags.
What does wipe day look like on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Its recent wipes drew 3 players at their busiest, on average. On the latest wipe the crowd peaked 14 hours after the wipe. In 100% of its recent wipes the crowd stayed above half that peak until the next wipe.
Players
How busy is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Right now Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] has 0 players on 100 slots. Over the last seven days it averaged 1 players and peaked at 4. In the last 48 hours it was busiest at 15:00 UTC, with 2 players on average.
How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] rank against other Rust servers?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] is #3,824 on player hours over the last seven days, in the top 17% of all ranked servers and #1,369 in Europe.
Rules and map
What are the rules and settings on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] runs 10x gather, going by its name. Groups can have up to 8 players, the game's default. Its game mode is survival, the standard game: gather, build, raid. Players can fight and raid each other. It is listed under Modded in the server browser: plugins or settings change the game. It runs Oxide plugins. Valve's anti-cheat, VAC, is on.
Which map does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] run?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] runs a procedural map, generated by the game, of size 3,700 with seed 1607523453. The same size and seed give the same map, so it can be looked at on RustMaps from this page.
Tags and lists
What do the server tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] mean?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] publishes these tags, which the game's server browser reads: gmrust (Game mode): Standard Rust survival; mp100 (Max players): 100 slots; ts8 (Group limit): At most 8 per team, the game default; v2633 (Protocol): Game protocol 2633: your game has to be on the same version to join; cs165217 (Build): Game build 165217; ptrak (Networking): RakNet, the game's standard network layer; $r? (Region code): No region code set; ^b (Biweekly): Wipes every two weeks; ^o (Oxide): Runs Oxide (uMod), a plugin framework; ^z (Modded): Listed under Modded: plugins or settings change the game; EU (Europe): Listed under Europe in the server browser. Its players now, its queue and the time its world was made are in the tags too, and are shown at the top of this page.
Which Zongarust lists and filters include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] fits these Zongarust lists: Best 10x Rust servers, Best EU Rust servers and Best modded Rust servers. On the server list it comes up under these filters: 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.
The server
Where is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] located?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] lists itself in Europe with its EU tag. Zongarust shows where a server says it is; it does not look up where the machine stands. Its address is 85.233.150.44:35015.
Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] online, and how reliable is it?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] is online right now. It last restarted about 4 days 6 hours ago, going by the uptime it reports. Over the last 7 full days it was up 100% of the time, 168 of 168 hours. Zongarust first saw it on 13 September 2026.
Does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] run smoothly?
Over the last 48 hours it ran at 60 server fps on average, never below 53. It carried up to 85,731 entities: buildings, deployables and everything else in the world. It used up to 4,310 MB of memory. Low fps and a climbing entity count are what players feel as lag.
Which version of Rust does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] run?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] runs Rust network protocol 2633 and build 165217 on Linux. Your game has to be on the same protocol to join; Steam updates it for you.
Joining
How do I join Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Start Rust, press F1 to open the console and enter client.connect 85.233.150.44:35015. Or use Launch Rust and join on this page, which opens Rust through Steam and connects you.