Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]
Online EU 85.233.150.44:35010 checked 8m ago
Server instruments
last reading Wed 00:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 24 · below 20 is lag, below 10 is badEntities
48 h range 79,117–82,608 · memory 3,075 MBUptime
23 h 49 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 24% of all ranked servers, top 61% in EU. Ranked on player hours over the last seven days.
Wipe schedule
a steady gapNext wipe Friday 30 October, 15:32 UTC, in 2d 13h. Every 7 days 4 hours · medium confidence
Coming wipes
- WPT 1Fri 30 Oct, 15:32 UTC2d 13h
- WPT 2Thu 5 Nov, 19:00 UTC8d 17hFW
- WPT 3Fri 6 Nov, 19:17 UTC9d 17h
- WPT 4Fri 13 Nov, 23:02 UTC16d 21h
- WPT 5Sat 21 Nov, 02:48 UTC24d 0h
- WPT 6Sat 28 Nov, 06:33 UTC31d 4h
- WPT 7Thu 3 Dec, 19:00 UTC36d 17hFW
- WPT 8Sat 5 Dec, 10:18 UTC38d 8h
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 8 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 11:46 UTC4d ago | 2 | – | running | 0 |
| Fri 16 Oct, 08:01 UTC11d ago | 4 | halved by day 3 | 7.2 days | 0 |
| Thu 8 Oct, 16:07 UTC19d ago | 4 | halved by day 5 | 7.7 days | 0 |
| Fri 2 Oct, 12:56 UTC25d ago | 5 | halved by day 4 | 6.1 days | 0 |
| Fri 25 Sep, 03:33 UTC32d ago | 3 | halved by day 1 | 7.4 days | 0 |
| Thu 17 Sep, 19:33 UTC40d ago | 3 | halved by day 4 | 7.3 days | 4 |
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- 33/150
- 2/100
- 1/50
- 0/10
- 117/150
- 30/400
Quick answers
from the figures on this pageWipe timing
What happens on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] when wipe day comes?
The busiest point of its recent wipes drew 3 players on average. Peak crowd on the latest wipe: 8 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 4 it fell below half when it didn't.
What wipe timing does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] follow?
About every 7.3 days is how often Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] has wiped lately. Friday 30 October at 15:32 UTC is when its next wipe is due. The world it runs now was made 4 days 14 hours ago. A wipe schedule of every two weeks is published in its tags.
Lists and filters
How should you read the tags on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; 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): The region field is empty; ^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): Europe is the browser category it sits in from Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
Rust Metrics lists featuring Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]: 10x Rust servers, EU Rust servers, checked and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: 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.
Player count
What position does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] hold among Rust servers?
Player hours over the last seven days put Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] at #5,424, #1,784 in Europe, in the top 24% of all ranked servers.
What player count does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] carry?
Current headcount on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]: 0 players, 100 slots available. Check: players over seven days. Average 0, peak 2. Check: 48-hour peak. 06:00 UTC, 2 players on average.
Server
What location is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] hosted in?
Reading: location. The EU tag puts Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] in Europe. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 85.233.150.44:35010.
What Rust version is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] on?
Reading: Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10], Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.
Is performance on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] within range?
Reading: 58 server fps on average across the last 48 hours. It never dropped below 24. Reading: 82,608 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 3,075 MB. What players call lag comes from low fps and an entity count on the rise.
Is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] up, and how often does it stay up?
Check: connection. Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] is online at this moment. By its reported uptime, the last restart was roughly 23 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
How is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] configured, and what rules are in force?
The name carries the rate: 10x gather on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
What map is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] on?
From seed 2090362659, the game generates the procedural map on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]. Its size is 3,700. The map repeats when size and seed match. Open it on RustMaps from this page.
How to join
What do you do to join Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
Check: join. Open Rust, press F1, then enter client.connect 85.233.150.44:35010. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at http://cloudrust.ru/.