Skip to the page
RUST ANALYTICS
LIVE65,847PLY11,672SRV
QUOTE 85.233.150.44:35015 Online EU checked 8m ago

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

10x biweekly wipes moddedoxide
Players · last
1/ 100
+024h
1% full
Day range 0 5
7-day avg 1 peak 5
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join

Key statistics

the figures behind the quote
Players now
1/ 100
1% full
Change · 24h
+0
no reading a day ago
7-day average
1
peak 5
Rank
#4,139
top 19% · #1444 in EU
Rank · 7d ago
#4,309
170 places up
Last wipe
5d ago
biweekly schedule
Next wipe
8d 18h
Thu 22 Oct, 16:08 UTC
Group limit
8
8, the default
Gather rate
10x
read from the name
Score
92
player hours, last seven days
Map
3700
Procedural Map · seed 68656627
First seen
13 Sep 2026
no hostname published

Players

AveragePeak
0246822:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC. Busiest hour of the two days: 5 players.

Server performance

02040608022:0007:0016:0002:0011:0020:00

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 Sep29 Sep4 Oct8 Oct13 Oct

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

Wipe schedule

from its schedule tag
Next wipeThursday 22 October, 16:08 UTCin 8d 18h

Its biweekly schedule tag · low confidence

usual gap
7.3 days
between real wipes
on rhythm
67%
of its recent wipes
wipe-day peak
4
players, last three wipes
crowd held
67%
else halves by day 5

Coming wipes

  1. 8d 18hThu 22 Oct, 16:08 UTC
  2. 22d 21hThu 5 Nov, 19:00 UTCFW
  3. 36d 18hThu 19 Nov, 16:08 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
Thu 8 Oct, 16:08 UTC5d ago 4 – running 0
Fri 2 Oct, 12:57 UTC11d ago 5 halved by day 5 6.1 days 0
Fri 25 Sep, 03:34 UTC18d ago 4 held half 7.4 days 0
Thu 17 Sep, 19:34 UTC26d 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 wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1[EU] HollowServers.co 10x No BPs [Loot++|Events|MyMini|Shop]EU · groups of 8+ · 10x · biweekly · 74 on average77/150+7+10.7%
2PROSTOJ CLASSIC #5 [X10|SKINS]EU · groups of 100+ · 10x · biweekly · 12 on average4/100+1+23.1%
3[EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTSEU · groups of 8+ · 10x · biweekly · 3 on average1/50−1−50.0%
4Turbo Rust 10x | PvP | MyMini | SkinBox | x10EU · groups of 20+ · 10x · biweekly · 3 on average0/10−2−100.0%
5Atlas - EU 10x | No BPs | Kits | ShopEU · groups of 20+ · 10x · weekly · 286 on average273/350+71+35.2%
6KRAKEN | X10 | EU | KITS | RP | FPS+EU · groups of 14+ · 10x · weekly · 120 on average62/350+9+16.3%

Quick answers

from the figures on this page

Rules & Settings

What settings and rules are in place on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] carries its gather rate in its name: 10x. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. PvP and raiding are enabled. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are in use. VAC is active.

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

A procedural map of size 3,700 with seed 68656627 runs on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10], created by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.

Activity

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

On seven-day player hours, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] sits at #4,139, in the top 19% across ranked servers and #1,444 in Europe.

How many players does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] have?

On Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10], 1 players are in now, out of 100 slots. The mean over the last seven days is 1 players, reaching 5 at its highest. The busiest hour in the last 48 hours was 15:00 UTC, with an average of 4 players.

Wipe Cycle

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

An average of 4 players marked the busiest point of its recent wipes. On the latest wipe, 28 hours after the wipe, the crowd peaked. Half the peak was held until the next wipe in 67% of its recent wipes. The crowd fell below half by day 5 when it did not hold.

When does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] schedule its wipes?

Its tag guides the prediction, as Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] has too few wipes on record to confirm its schedule. The date of its next wipe is Thursday 22 October at 16:08 UTC. 5 days 5 hours ago the current world was created. The tags show wipes every two weeks.

Server Overview

What is the server location for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?

The EU tag and Europe are what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] lists for itself. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 85.233.150.44:35015 is its address.

How is the performance on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?

Server fps over the last 48 hours: 59 on average, 24 at the lowest. The entity count reached 89,593, covering buildings, deployables and all else in the world. The memory ceiling reached 3,151 MB. Low fps and growing entities are the source of felt lag.

What Rust version is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] running?

The build is Rust network protocol 2634 and build 167398 on Linux, running on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]. Your game needs the same protocol to get in; Steam takes care of the update.

Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] up, and how consistent is its uptime?

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] is up. It is taking players now. 19 hours ago is when it last restarted, judging by the uptime it reports. 7 full days have passed with 91% uptime, 153 of 168 hours. 13 September 2026 is when Rust Analytics first saw it.

Server Tags

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

The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): It holds 100 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167398 (Build): It runs build 167398; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set; ^b (Biweekly): A fortnight between wipes; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; EU (Europe): The server browser files it under Europe, which Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] appears in which of the lists and filters on Rust Analytics?

The following Rust Analytics lists feature Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]: 10x Rust servers, Rust servers: Europe and Modded Rust servers. It appears under these filters 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.

Joining the Server

What is the process to join Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?

Type client.connect 85.233.150.44:35015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players It holds 100 slots.
ts8
Group limit 8 per team: the default setting, unchanged.
v2634
Protocol Your game must run protocol 2634 to connect.
cs167398
Build It runs build 167398.
ptrak
Networking RakNet, the network layer the game ships with.
$r?
Region code No region code has been set.

Wipe schedule

^b
Biweekly A fortnight between wipes.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

Region

EU
Europe The server browser files 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.