Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Online EU 85.233.150.44:35015 checked 8m 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 16% of all ranked servers, top 45% in EU. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 30 October, 15:34 UTC, in 2d 4h. 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
- 60%else halves by day 5.5
Coming wipes
- in 2d 4hFri 30 Oct, 15:34 UTC
- in 8d 7hThu 5 Nov, 19:00 UTCFW
- in 9d 7hFri 6 Nov, 19:21 UTC
- in 16d 11hFri 13 Nov, 23:08 UTC
- in 23d 15hSat 21 Nov, 02:54 UTC
- in 30d 19hSat 28 Nov, 06:41 UTC
- in 36d 7hThu 3 Dec, 19:00 UTCFW
- in 37d 22hSat 5 Dec, 10:28 UTC
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
23 OCT 2026Fri 23 Oct, 11:47 UTC4d ago |
3 | – | running | 0 |
16 OCT 2026Fri 16 Oct, 08:01 UTC12d ago |
3 | halved by day 6 | 7.2 days | 0 |
8 OCT 2026Thu 8 Oct, 16:08 UTC19d ago |
4 | held half | 7.7 days | 0 |
2 OCT 2026Fri 2 Oct, 12:57 UTC25d ago |
5 | halved by day 5 | 6.1 days | 0 |
25 SEP 2026Fri 25 Sep, 03:34 UTC33d ago |
4 | held half | 7.4 days | 0 |
17 SEP 2026Thu 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.
Quick answers
From the figures on this page.
Map and rules
On Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], which rules and settings apply?
By its name, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] gathers at 10x. The group limit is 8 players, the game's default. Filed under survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. The server browser lists it under Modded; plugins or settings alter the game. Filed under plugins: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in use on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Generated by the game, the procedural map of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has size 3,700 and seed 262731628. From this page you can view the map on RustMaps; the same size and seed give the same map.
Tags
On Rust Server Index, which lists and filters carry Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
These lists on Rust Server Index take Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 10x Rust servers, Rust servers filed under Europe and Modded Rust servers, filed by play style. These filters on the server list 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.
How should you read the tags listed for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Filed under these tags, as published by Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp100 (Max players): 100 slots are available; ts8 (Group limit): Game default applies: teams of up to 8; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): It runs build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): A region code is absent; ^b (Biweekly): The cycle runs to a wipe every fortnight; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): This one is Modded, since plugins or settings change how it plays; EU (Europe): The browser files it under Europe. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipe schedule
What happens on wipe day at Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
The average peak across its recent wipes is 3 players. The latest wipe peaked 6 hours in. The crowd held above half the peak until the next wipe in 60% of its recent wipes. By day 5.5 the crowd had fallen below half when it didn't hold.
Which wipe timetable does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] follow?
About every 7.3 days is the recent interval between wipes on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. Dated for Friday 30 October at 15:34 UTC: its next wipe. 4 days 23 hours is when its current world was made. Its tags state wipes every two weeks.
Players and ranking
What position does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hold among Rust servers?
Filed under rankings: #3,491 for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on seven-day player hours, #1,302 in Europe, top 16% overall.
What does the player count on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] look like?
The live count for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] stands at 0 players, out of 100 slots. Filed under seven-day figures: an average of 1 players and a peak of 6. The busiest point in the last 48 hours was 19:00 UTC, averaging 4 players.
Server facts
What version does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] use?
Rust network protocol 2635 and build 168909 on Linux is what you will find on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. To join you need the same protocol; Steam handles the update.
Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] reachable, and does it stay up?
Right now Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is up and running. Its reported uptime gives the last restart as roughly 33 hours ago. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. The earliest sighting at Rust Server Index is 13 September 2026.
Is the performance on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] good?
Server fps held at 58 on average across the last 48 hours, never dropping below 33. Buildings, deployables and everything else in the world came to as many as 88,778 entities. Memory use reached as much as 3,365 MB. Lag, to players, is low fps and an entity count that climbs.
Which region is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] in?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|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:35015.
Connecting
What is the way onto Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
If you would rather use the console, press F1 in Rust and enter client.connect 85.233.150.44:35015. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.
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.