Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Online EU 85.233.150.44:35015 checked 7m ago
Server instruments
last reading Wed 00:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 33 · below 20 is lag, below 10 is badEntities
48 h range 84,916–88,778 · memory 2,753 MBUptime
23 h 48 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 16% of all ranked servers, top 45% in EU. Ranked on player hours over the last seven days.
Wipe schedule
a steady gapNext wipe Friday 30 October, 15:34 UTC, in 2d 14h. Every 7 days 4 hours · medium confidence
Coming wipes
- WPT 1Fri 30 Oct, 15:34 UTC2d 14h
- WPT 2Thu 5 Nov, 19:00 UTC8d 17hFW
- WPT 3Fri 6 Nov, 19:21 UTC9d 17h
- WPT 4Fri 13 Nov, 23:08 UTC16d 21h
- WPT 5Sat 21 Nov, 02:54 UTC24d 1h
- WPT 6Sat 28 Nov, 06:41 UTC31d 5h
- WPT 7Thu 3 Dec, 19:00 UTC36d 17hFW
- WPT 8Sat 5 Dec, 10:28 UTC38d 9h
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 6 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 35/150
- 2/100
- 1/50
- 0/10
- 130/150
- 30/400
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
At their busiest, its recent wipes drew 3 players on average. 6 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 60% of recent wipes. By day 5.5 it fell below half when it didn't.
When does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] wipe?
Lately its wipes have been about every 7.3 days on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. Friday 30 October at 15:34 UTC is when its next wipe is due. 4 days 13 hours ago the current world was made. A wipe schedule of every two weeks is published in its tags.
Tag meanings
How should you read the tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
These are the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Two-week wipe schedule; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server; EU (Europe): Its browser listing: Europe. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 10x Rust servers, EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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.
Occupancy
Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] sit in the rankings?
Ranked by seven-day player hours, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] sits at #3,507 and #1,312 in Europe, inside the top 16%.
How full does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] get?
Current headcount on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 0 players, 100 slots available. Seven-day check: 1 players on average. Peak reading: 6. Check: 48-hour peak. 19:00 UTC, 4 players on average.
Operator and location
Which location does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run from?
Its EU tag places Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] in Europe. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 85.233.150.44:35015.
What Rust version is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on?
Reading: Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.
Is performance on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] within range?
Over the last 48 hours the average was 58 server fps; the floor was 33. Peak entity count: 88,778. Buildings, deployables and all else included. Check: memory. Peak use was 3,222 MB. Expect lag when fps falls and entities climb.
What is the uptime on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], and is it online?
Check: connection. Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is online at this moment. Reading: uptime. About 23 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
What rules does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] enforce, and what are its settings?
Gather rate check: 10x. That comes from the name Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
What map is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on?
From seed 262731628, the game generates the procedural map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. Its size is 3,700. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
How can you get onto Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Check: join. Open Rust, press F1, then enter client.connect 85.233.150.44:35015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.