Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10]
OVR is 100 less its top share among ranked servers: top 18%.
Power level
Players on it, from the Steam server list.
Every five minutes.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Tale of the tape
Against its closest rival: the most similar server we track.
Wipe receipt
85.233.150.44:35015
THANK YOU · COME AGAIN NEXT WIPE
The map
Under the hood
Asked of the server directly. Low fps and a climbing entity count mean lag.
The ranking
Down 755 places on last week. Top 18% of all ranked servers, top 49% in EU. Daily; 1 is best.
Spec sheet
- Address
- 85.233.150.44:35015
- Region
- EU
- Max players
- 100
- Group limit
- 8, the default
- Wipe schedule
- biweekly
- Last wipe
- 2 Oct 2026, 12:57 UTC
- Hostname
- –
- First seen
- 13 Sep 2026
Other contenders
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Server rules
What are Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10]'s rules and configuration?
By its name, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] gives you 10x gather. Up to 8 players per group, the standard default. survival is the game mode, gather, build and raid in the standard game. PvP and raiding are enabled. Modded in the browser is where it appears: plugins or settings change how the game plays. Oxide plugins are running on it. VAC is on: Valve's anti-cheat is running.
What's the map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10]?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] uses a procedural map of 3,700 that the game generates with seed 585335201. You can see it on RustMaps from this page, as the same size and seed make the same map.
Tags
How should you read the tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10]?
The game's server browser reads the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] publishes: gmrust (Game mode): The usual Rust survival setup; mp100 (Max players): Room for 100; ts8 (Group limit): Default team size is 8; v2634 (Protocol): Protocol 2634: match it or you cannot join; cs166652 (Build): Build 166652; ptrak (Networking): The network layer is RakNet, which the game uses as standard; $r? (Region code): No region code on record; ^b (Biweekly): Wipes come round every fortnight; ^o (Oxide): Oxide (uMod) handles the plugins; ^z (Modded): Modded: plugins or settings change how it plays; EU (Europe): Browser listing: Europe. From the tags, this page also pulls its live player count, its queue and its world's creation time, and puts them at the top.
Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] appear in Boongarust lists?
The Boongarust lists that take Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] are: 10x Rust servers, live, EU Rust servers and Top modded Rust servers. 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.
Server details
Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] laggy?
Server fps held an average of 58 across the last 48 hours, minimum 13. At its peak, it held 80,204 entities, including buildings and deployables. At its highest, memory consumption was 3,345 MB. Players feel lag when fps drops and entities pile up.
What's the physical location of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10]?
The EU tag is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] uses to list itself in Europe. What you see on Boongarust is where a server says it is, not where the machine is found to stand. Connect at 85.233.150.44:35015.
What's the uptime like on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10]?
Online: Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10], at this moment. A restart happened about 21 hours ago, based on the uptime figure. Uptime over the last 7 full days came to 79%, 132 hours from 168. The first record Boongarust has is 13 September 2026.
What Rust version is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] using?
On Linux, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] runs Rust network protocol 2634 and build 166652. Joining requires your game to be on the same protocol; Steam handles the update.
Wipe info
How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] handle wipe day?
Recent wipes peaked at 4 players on average. The crowd on the latest wipe peaked 6 hours in. Half the peak held until the next wipe in 100% of recent wipes.
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] wipes on what schedule?
Few of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10]'s wipes are logged, so the tag drives the prediction and the schedule stays unconfirmed. Friday 16 October at 12:57 UTC is when the next wipe comes. The world you are on was made 5 days 11 hours. Its tags say it wipes every two weeks.
Population
Ranking wise, where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] place?
Seven-day player hours put Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] at #4,332, within the top 18% of ranked servers and #1,462 across Europe.
How many players are on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10]?
0 players are on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10] at the moment, out of 100 slots. The average over the last seven days was 1 players, with a peak of 5. It was busiest at 17:00 UTC in the last 48 hours, with 2 players on average.
Join the server
What's the process to join Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 02.10]?
To connect, open the console with F1 in Rust and type client.connect 85.233.150.44:35015. You can also use Launch Rust on this page to open Rust via Steam and connect.
Sticker sheet
Every tag it publishes, and what it means. Published as mp100,ptrak,$r?,v2634,^b,EU,gmrust,cs166652,ts8,^o^z.
Flag meanings are Facepunch's.
