StatusLive Servers online11,845 Players80,760 Populated3,897 Wiped · 3 h164 Interval5 min Date27 OCT 2026

DWG RG-S3494Server sheetchecked 9m ago

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

Online EU 85.233.150.44:35015 checked 9m ago

10x biweekly wipes moddedoxide
Connect
Players now 0/ 100 0% full
7-day average1peak 6
Rank#3,494top 16% · #1302 in EU
Last wipe4d agobiweekly schedule
Next wipe2d 18hFri 30 Oct, 15:34 UTC
Fig. 1

Players

AveragePeak
0246821:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC.

Fig. 1Players on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Fig. 2

Server performance

02040608021:0006:0015:0001:0010:0019: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

a steady gap

Next wipe Friday 30 October, 15:34 UTC, in 2d 18h. Every 7 days 4 hours · medium confidence

usual gap7.3 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak3players, last three wipes
crowd held60%else halves by day 5.5

Coming wipes

  1. 2d 18hFri 30 Oct, 15:34 UTC
  2. 8d 22hThu 5 Nov, 19:00 UTCFW
  3. 9d 22hFri 6 Nov, 19:21 UTC
  4. 17d 2hFri 13 Nov, 23:08 UTC
  5. 24d 5hSat 21 Nov, 02:54 UTC
  6. 31d 9hSat 28 Nov, 06:41 UTC
  7. 36d 22hThu 3 Dec, 19:00 UTCFW
  8. 38d 13hSat 5 Dec, 10:28 UTC

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctThu 8 Oct
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 3, 6 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 11:47 UTC4d ago 3 – running 0
Fri 16 Oct, 08:01 UTC11d ago 3 halved by day 6 7.2 days 0
Thu 8 Oct, 16:08 UTC19d ago 4 held half 7.7 days 0
Fri 2 Oct, 12:57 UTC25d ago 5 halved by day 5 6.1 days 0
Fri 25 Sep, 03:34 UTC32d ago 4 held half 7.4 days 0
Thu 17 Sep, 19:34 UTC40d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop]EU · groups of 8+ · 10x · biweekly · 76 on average
132 / 175
02
PROSTOJ CLASSIC #5 [X10|SKINS]EU · groups of 100+ · 10x · biweekly · 10 on average
8 / 100
03
[EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTSEU · groups of 8+ · 10x · biweekly · 3 on average
2 / 50
04
Turbo Rust 10x | PvP | MyMini | SkinBox | x10EU · groups of 20+ · 10x · biweekly · 2 on average
2 / 10
05
Atlas - EU 10x | No BPs | Kits | ShopEU · groups of 20+ · 10x · weekly · 336 on average
460 / 550
06
KRAKEN | X10 | EU | KITS | RP | FPS+EU · groups of 14+ · 10x · weekly · 147 on average
133 / 400
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

What uptime is recorded for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], and is it up?

At this moment Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is online. About 18 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. First seen by Rust Graphs on 13 September 2026.

How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] perform, as measured?

Average server fps over the last 48 hours is 58; the lowest was 33. Counted at its highest: 88,778 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,139 MB. Players feel low fps and a climbing entity count as lag.

In which location is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hosted?

In Europe Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself, tagged EU. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 85.233.150.44:35015.

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

The platform is Linux and the version is Rust network protocol 2635 and build 168909 on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. The same protocol is required for joining, and Steam updates your game to it.

Counts

How many players are plotted on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

Current player count on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 0, of 100 slots. The seven-day mean is 1 players; the peak over the same period is 6. The 48-hour peak falls at 19:00 UTC, averaging 4 players.

In the rankings, which position does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hold?

Across seven days, player hours give Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] #3,494 globally and #1,302 in Europe, a top 16% position among ranked servers.

Wipe times

On Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], what does the data show for wipe day?

The recent wipes averaged a busiest count of 3 players. At 6 hours after the latest wipe the crowd was at its peak. The crowd stayed above half the peak until the next wipe in 60% of its recent wipes. By day 5.5 the crowd had fallen below half on the wipes where it did not hold.

On Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], when do wipes occur?

In recent times the interval between wipes at Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has been about 7.3 days. It is due to wipe next on Friday 30 October at 15:34 UTC. The world it runs now was made 4 days 9 hours ago. Its tags give a wipe schedule of one wipe every two weeks.

Rules and settings

Which settings does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run, and what rules?

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] takes its gather rate from its name: 10x. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.

On which map is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] played?

Seed 262731628 and size 3,700 define the procedural map Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] appear among the Rust Graphs lists and filters?

On Rust Graphs, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is placed in these lists: 10x Rust servers, plotted, Europe servers, plotted and Modded Rust servers. On the server list, these filters bring it up: 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.

Which meaning is attached to each tag on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

The game's server browser reads these tags from Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): Slots: 100; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; EU (Europe): The server browser lists it under Europe. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Joining the server

What is the way to connect to Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

Connect with client.connect 85.233.150.44:35015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,EU,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival, as Rust plays.
mp100
Max players Slots: 100.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

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.

KeyTag string decoded