Skip to the content
Dive report

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]

Online EU 85.233.150.44:35015 checked 9m ago

10x biweekly wipes moddedoxide
Drop in
1/ 100 players now 1% full
17-day averagepeak 5
#4,048ranktop 18% · #1450 in EU
1d agolast wipebiweekly schedule
12d 10hnext wipeFri 30 Oct, 08:01 UTC

Players

AveragePeakWipe
0123422:0007:0016:0002:0011:0020:00Wiped Fri 16 Oct, 08:01 UTCWIPE

Hourly average and peak, UTC.

Server performance

Server fpsWipe
02040608022:0007:0016:0002:0011:0020:00Wiped Fri 16 Oct, 08:01 UTCWIPE

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
RankRank in region
12k4k6k8k20 Sep25 Sep1 Oct6 Oct12 Oct17 Oct

Top 18% of all ranked servers, top 50% in EU. Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 08:01 UTC, in 12d 10h. Its biweekly schedule tag · low confidence

usual gap7.4 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak4players, last three wipes
crowd held75%else halves by day 5

Coming wipes

  • 12d 10h
    Fri 30 Oct, 08:01 UTC
  • 18d 21h
    Thu 5 Nov, 19:00 UTC
    FW
  • 26d 10h
    Fri 13 Nov, 08:01 UTC
  • 40d 10h
    Fri 27 Nov, 08:01 UTC

The first 48 hours of its last wipes

Thu 8 OctFri 2 OctFri 25 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 28 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 08:01 UTC1d ago – – running 0
Thu 8 Oct, 16:08 UTC9d ago 4 held half 7.7 days 0
Fri 2 Oct, 12:57 UTC15d ago 5 halved by day 5 6.1 days 0
Fri 25 Sep, 03:34 UTC22d ago 4 held half 7.4 days 0
Thu 17 Sep, 19:34 UTC30d 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.

Neighbouring dive spots

Similar servers

the same kind of game, then region, group limit, rate and wipes

From the figures on this page

Quick answers

Tags and search

Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] appear in Rust Going Deep lists and filters?

The Rust Going Deep lists that carry Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] are: Best 10x Rust servers, EU Rust servers, live and Modded Rust servers. You can find it on the server list by 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 3 days; Gather rate: 10x.

How should you read the tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]?

gmrust (Game mode): Survival, as standard Rust does it; mp100 (Max players): It holds 100 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167781 (Build): It's on build 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^b (Biweekly): Every fortnight, it wipes; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; EU (Europe): The server browser lists it under Europe — that is the tag list Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] puts out for the game's server browser. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.

Server info

Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] lag-free?

The last 48 hours saw an average of 58 server fps, never dropping below 46. Buildings, deployables and all other world objects added up to as many as 87,179 entities. Memory use peaked at 3,029 MB. Players experience lag when fps drops and entities climb.

What location is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] in?

Its location is Europe, according to the EU tag Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] displays. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 85.233.150.44:35015.

What's the uptime like for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]?

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] is live as of this check. Its reported uptime shows a restart about 19 hours ago. It was up 100% of the time over the last full 7 days, 168 of 168 hours. 13 September 2026 is when Rust Going Deep first saw it.

What is the Rust version for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]?

Rust network protocol 2634 and build 167781 is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] runs, on Linux. To join, your game must be on the same protocol; Steam takes care of updating it.

Wipe details

What schedule does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] follow for wipes?

Its tag guides the prediction since Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] has too few wipes on record to confirm the schedule. Expect the next wipe on Friday 30 October at 08:01 UTC. This world has been running since 37 hours ago. A wipe schedule covering every two weeks is published in its tags.

What can you expect on wipe day at Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]?

Across its recent wipes, the average busiest point drew 4 players. 28 hours after the latest wipe started, the crowd hit its peak. Above half that peak until the next wipe: the crowd managed this in 75% of recent wipes. By day 5, the pop had dropped under half.

Map and rules

What settings and rules have been applied to Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]?

Gather rates here are 10x, as Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] announces in its name. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. VAC, Valve's anti-cheat, is enabled.

Which map is active on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]?

A game-generated procedural map of size 3,700 with seed 34519301 is in play on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]. The map is reproducible from its size and seed, so RustMaps can show it from this page.

Player count

What's the population like on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]?

Right now 1 players are on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10], which has 100 slots. The seven-day average is 1 players, with a peak of 5. At 13:00 UTC in the last 48 hours, the average reached its highest: 2 players.

Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] sit in the rankings?

Over the last seven days Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10] sits at #4,048 on player hours, which is #1,450 in Europe and inside the top 18% of all ranked servers.

Join info

How do you get into Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 16.10]?

Open Rust and press F1, then type client.connect 85.233.150.44:35015. Alternatively, click Launch Rust on this page to join via Steam.

What each one means

Server tags

Published as mp100,ptrak,$r?,v2634,^b,EU,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust does it.
mp100
Max players It holds 100 players.
ts8
Group limit Teams cap at 8, which is the game default.
v2634
Protocol The protocol is 2634; a different version won't get you in.
cs167781
Build It's on build 167781.
ptrak
Networking RakNet, the network layer Rust uses by default.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Every fortnight, it wipes.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded You'll see it in Modded, since plugins or settings modify the game.

Region

EU
Europe The server browser lists it under Europe.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.