Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]
Online EU 85.233.150.44:35010 checked 10m ago
Players
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
Top 23% of all ranked servers, top 58% in EU. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 30 October, 15:32 UTC, in 1d 14h. Every 7 days 4 hours · medium confidence
- usual gap
- 7.3 daysbetween real wipes
- on rhythm
- 80%of its recent wipes
- wipe-day peak
- 3players, last three wipes
- crowd held
- 0%else halves by day 4
Coming wipes
- in 1d 14hFri 30 Oct, 15:32 UTC
- in 7d 18hThu 5 Nov, 19:00 UTCFW
- in 8d 18hFri 6 Nov, 19:17 UTC
- in 15d 22hFri 13 Nov, 23:02 UTC
- in 23d 1hSat 21 Nov, 02:48 UTC
- in 30d 5hSat 28 Nov, 06:33 UTC
- in 35d 18hThu 3 Dec, 19:00 UTCFW
- in 37d 9hSat 5 Dec, 10:18 UTC
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
23 OCT 2026Fri 23 Oct, 11:46 UTC5d ago |
2 | – | running | 0 |
16 OCT 2026Fri 16 Oct, 08:01 UTC12d ago |
4 | halved by day 3 | 7.2 days | 0 |
8 OCT 2026Thu 8 Oct, 16:07 UTC20d ago |
4 | halved by day 5 | 7.7 days | 0 |
2 OCT 2026Fri 2 Oct, 12:56 UTC26d ago |
5 | halved by day 4 | 6.1 days | 0 |
25 SEP 2026Fri 25 Sep, 03:33 UTC33d ago |
3 | halved by day 1 | 7.4 days | 0 |
17 SEP 2026Thu 17 Sep, 19:33 UTC41d 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.
Quick answers
From the figures on this page.
Map and rules
Where can you read the rules and settings that apply on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
By its name, Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] gathers at 10x. The group limit is 8 players, the game's default. The server runs survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. Plugins or settings change the game; it is listed under Modded in the server browser. Oxide plugins are run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
Generated by the game, the procedural map of Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] has size 3,700 and seed 2090362659. The map can be seen on RustMaps from this page, because the same size and seed give the same map.
Lists and filters
On Rust Server Index, which lists and filters carry Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
Filed under these Rust Server Index lists is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]: 10x Rust servers, Rust servers filed under Europe and Modded Rust servers, filed by play style. It appears under the following 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.
What is meant by the tags on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
These are the tags Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] publishes; the game's server browser reads this list: gmrust (Game mode): Rust survival, as standard; mp100 (Max players): Player cap: 100; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): It runs build 168909; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): A region code is absent; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): Plugins or changed settings put this under Modded; EU (Europe): Europe is the region shown in the server browser. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipe dates
How does a wipe day run on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
Its recent wipes averaged 3 players at peak. 8 hours into the latest wipe, the crowd reached its peak. Its recent wipes kept the crowd above half the peak until the next wipe 0% of the time. By day 4 the crowd had fallen below half when it didn't hold.
When does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] wipe?
About every 7.3 days is the recent interval between wipes on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]. Dated for Friday 30 October at 15:32 UTC: its next wipe. Its present world dates from 5 days 13 hours. Its tags state wipes every two weeks.
Player counts
What position does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] hold among Rust servers?
The seven-day player-hours ranking places Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] at #5,008 and #1,706 in Europe, among the top 23% of ranked servers.
What does the player count on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] look like?
Filed under live counts: Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10], 0 players on 100 slots at present. Averaged across seven days: 0 players, peaking at 3. Filed under busiest hour: 17:00 UTC in the last 48 hours, averaging 3 players.
Operator and status
What version does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] use?
Rust network protocol 2635 and build 168909, on Linux, is what Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] runs. The protocol must match before you can join, and Steam takes care of updating it.
What is the uptime and current status of Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
The server is live at this moment: Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]. Its reported uptime gives the last restart as roughly 46 hours ago. It was up 144 of 168 hours across the last 7 full days, or 86% of the time. The earliest sighting at Rust Server Index is 13 September 2026.
How well does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] perform?
The last 48 hours give an average of 57 server fps and a floor of 32. Buildings, deployables and everything else in the world came to as many as 83,032 entities. The peak memory figure stood at 3,555 MB. A climbing entity count and low fps are felt by players as lag.
Where in the world is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] hosted?
Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] gives Europe as its location and the tag EU. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 85.233.150.44:35010.
How to join
How can you connect to Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
Enter client.connect 85.233.150.44:35010 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you. The website can be found at http://cloudrust.ru/.
Server tags
What each one means.
Published as mp100,ptrak,$r?,v2635,^b,EU,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp100
ts8
v2635
cs168909
ptrak
$r?
Wipe schedule
^b
Mods and access
^o
^z
Region
EU
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.