Open every day, at every hour Admission free 11,656 servers and 41,553 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

The server's own banner, as it publishes it

Exhibit no. 3,512Acc. 2026.3512

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

Rust server, EU · in the archive since 13 September 2026

Online EU 85.233.150.44:35015 checked 10m ago

10x biweekly wipes moddedoxide
To visit
Players now 0/ 100
0% full
7-day average1peak 6
Rank#3,512top 16% · #1314 in EU
Last wipe4d agoFri 23 Oct, 11:47 UTC · biweekly schedule
Next wipe2d 13hFri 30 Oct, 15:34 UTC

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectednow, 28 Oct 2026, 02:15 UTCAll times UTC.

The record of each wipe

  1. Fri 23 Oct 202611:47 UTC4d ago
    Peak
    3
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Fri 16 Oct 202608:01 UTC11d ago
    Peak
    3
    Crowd
    halved by day 6
    Lasted
    7.2 days
    Players before
    0
  3. Thu 8 Oct 202616:08 UTC19d ago
    Peak
    4
    Crowd
    held half
    Lasted
    7.7 days
    Players before
    0
  4. Fri 2 Oct 202612:57 UTC25d ago
    Peak
    5
    Crowd
    halved by day 5
    Lasted
    6.1 days
    Players before
    0
  5. Fri 25 Sep 202603:34 UTC32d ago
    Peak
    4
    Crowd
    held half
    Lasted
    7.4 days
    Players before
    0
  6. Thu 17 Sep 202619:34 UTC40d ago
    Peak
    2
    Crowd
    held half
    Lasted
    7.3 days
    Players before
    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.

The rhythm

Wipe schedule

a steady gap

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

7.3 daysusual gapbetween real wipes
80%on rhythmof its recent wipes
3wipe-day peakplayers, last three wipes
60%crowd heldelse halves by day 5.5

Coming wipes

  1. 2d 13hFri 30 Oct, 15:34 UTC
  2. 8d 16hThu 5 Nov, 19:00 UTCFW
  3. 9d 16hFri 6 Nov, 19:21 UTC
  4. 16d 20hFri 13 Nov, 23:08 UTC
  5. 24d 0hSat 21 Nov, 02:54 UTC
  6. 31d 4hSat 28 Nov, 06:41 UTC
  7. 36d 16hThu 3 Dec, 19:00 UTCFW
  8. 38d 8hSat 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

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

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

AveragePeak
0246803:0012:0021:0007:0016:0001:00

Hourly average and peak, UTC.

Folder 2

Server performance

02040608003:0012:0021:0007:0016:0001: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.

Folder 3

Rank

RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Related exhibits

Similar servers

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

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags, lists

What do the server tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] mean?

You can see the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] publishes, read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are set on this server; ts8 (Group limit): Teams are capped at 8, the default the game ships; v2635 (Protocol): To join, your game has to be on protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): A wipe every fortnight; ^o (Oxide): A plugin framework, Oxide (uMod), is installed here; ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; EU (Europe): Europe is the region the server browser files it under. At the top of this page you also see the current players, the queue and when the world was made, all from the tags.

Which Rust Server History lists and filters include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

These Rust Server History lists include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 10x Rust servers, on record, European Rust servers and Modded Rust servers: the record. 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.

Server record

Does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run smoothly?

Across the last 48 hours it averaged 58 server fps; the low was 33. Buildings, deployables and everything else in the world came to as many as 88,778 entities. The highest memory use was 3,222 MB. What players feel as lag comes from low fps and a climbing entity count.

Which version of Rust does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run?

The recorded build for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is Rust network protocol 2635 and build 168909 on Linux. Joining requires your game to be on the same protocol; Steam keeps it updated for you.

Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] online, and how reliable is it?

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is listed as online now. About 24 hours ago is when it last restarted, judged by the uptime it reports. Of 168 hours in the last 7 full days, 168 were up: 100% of the time. 13 September 2026 is when Rust Server History first saw it.

Where is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] located?

The EU tag is how Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself in Europe. Rust Server History does not look up where the machine stands; it shows where a server says it is. Its entry gives 85.233.150.44:35015 as the address.

Wipe log

What does wipe day look like on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

At their busiest, its recent wipes drew an average of 3 players. On the latest wipe, 6 hours after the wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 60% of its recent wipes. The fall below half came by day 5.5 in those wipes where it didn't hold.

What is the wipe schedule on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

Lately the wipes on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] have come about every 7.3 days. On Friday 30 October at 15:34 UTC its next wipe is due. 4 days 14 hours ago its current world was made. The tags list a wipe schedule of every two weeks.

Player counts

How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] rank against other Rust servers?

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] ranks #3,512 on seven-day player hours: top 16% overall and #1,314 in Europe.

How busy is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

Against 100 slots, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] records 0 players right now. The seven-day average stands at 1 players; the peak is 6. An average of 4 players at 19:00 UTC made that the busiest hour of the last 48.

Rules, map

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

You can read a 10x gather rate in the name of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. The limit of 8 players per group is the game's default. Under game mode, the entry reads survival, gather, build, raid: the standard game. Fighting and raiding between players are permitted. Under Modded in the server browser, the game is changed by plugins or settings. Oxide plugins are running. The anti-cheat VAC from Valve is active.

Which map does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run?

A procedural map of size 3,700 with seed 262731628 is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs, generated by the game. One size and seed produce one map, which RustMaps can show you from this page.

How to join

How do I join Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

Enter client.connect 85.233.150.44:35015 in the console, opened with F1 in Rust. Launch Rust and join on this page also works: it opens Rust through Steam and connects you.

The label explained

Server tags

What each tag this server publishes means.

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players 100 slots are set on this server.
ts8
Group limit Teams are capped at 8, the default the game ships.
v2635
Protocol To join, your game has to be on protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet handles the network layer, as standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly A wipe every fortnight.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), is installed here.
^z
Modded Plugins or settings alter the game, so it is listed under Modded.

Region

EU
Europe Europe is the region the server browser files it under.

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.