Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]
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 19% of all ranked servers, top 51% in EU. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 22 October, 16:08 UTC, in 8d 19h. Its biweekly schedule tag · low confidence
- usual gap
- 7.3 days between real wipes
- on rhythm
- 67% of its recent wipes
- wipe-day peak
- 4 players, last three wipes
- crowd held
- 67% else halves by day 5
Coming wipes
- 8d 19hThu 22 Oct, 16:08 UTC
- 22d 22hThu 5 Nov, 19:00 UTCFW
- 36d 19hThu 19 Nov, 16:08 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 28 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 8 Oct, 16:08 UTC 5d ago | 4 | – | running | 0 |
| Fri 2 Oct, 12:57 UTC 11d ago | 5 | halved by day 5 | 6.1 days | 0 |
| Fri 25 Sep, 03:34 UTC 18d ago | 4 | held half | 7.4 days | 0 |
| Thu 17 Sep, 19:34 UTC 26d 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
Quick answers
Player Count
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] ranking: what position does it hold?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] ranks #1,447 in Europe and #4,156 overall on player hours over the last seven days, in the top 19% of ranked servers.
What is the player count on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?
1 of 100 slots are filled on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] at the moment. The seven-day average player count stands at 1, and the highest point was 5. Over the last 48 hours, the peak hour was 15:00 UTC, averaging 4 players.
Server Tags
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] tags: what do they indicate?
The game's server browser reads these tags from Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]: gmrust (Game mode): Rust survival, standard; mp100 (Max players): The server has 100 slots; ts8 (Group limit): Default team size: 8; v2634 (Protocol): Protocol 2634: join only if your game matches this version; cs167398 (Build): Running build 167398; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): Region code missing; ^b (Biweekly): Two-week wipe cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded category applies; plugins or settings alter gameplay; EU (Europe): In the server browser it appears under Europe. Current players, queue and world creation time come from the tags and appear at the top of this page.
Which lists and filters on BestRustServers.xyz contain Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?
The BestRustServers.xyz lists that include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] are: 10x Rust servers, Rust servers in Europe and Best modded Rust servers. 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 Overview
What Rust version is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] on?
On Linux, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] runs Rust network protocol 2634 and build 167398. Steam updates your game automatically, but it needs to match the protocol to join.
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] performance: is it smooth?
Its average server fps over the last 48 hours was 59, with a low of 24. Buildings, deployables and the rest of the world accounted for up to 89,593 entities. At its highest, memory usage was 3,322 MB. What players experience as lag is low fps combined with a rising entity count.
What is the uptime and reliability of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] is currently online. About 18 hours ago is when it last restarted, based on its uptime. Over the past 7 full days, it was online 153 of 168 hours, 91% of the time. It was first seen by BestRustServers.xyz on 13 September 2026.
What is the location of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?
Its EU tag places Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] in Europe. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. 85.233.150.44:35015 is its address.
Rules & Map
Which map is used on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?
Generated by the game, the map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] is procedural, size 3,700, seed 68656627. View it on RustMaps from this page: identical size and seed produce an identical map.
What are the settings and rules for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?
By its name, the gather rate is 10x on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]. No group limit is stated; the game's default of 8 players applies. Listed as survival, gather, build, raid: the standard game. Raids and PvP are on. Plugins or settings change the game, so it appears under Modded. Oxide plugins are used. VAC protection is on.
Wipe Schedule
On what schedule does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10] wipe?
As Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]'s record holds too few wipes to confirm its schedule, its tag drives the prediction. On Thursday 22 October at 16:08 UTC the next wipe is due. Its world dates from 5 days 4 hours. The tags list a wipe every two weeks.
What happens on wipe day on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?
The average busiest point of its recent wipes was 4 players. 28 hours into the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 67% of its recent wipes. When it fell, the crowd dropped under half by day 5.
How to Join
How can I connect to Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 08.10]?
Enter client.connect 85.233.150.44:35015 in the console (F1 in Rust), or use Launch Rust on this page to open Steam and connect.
Server tags
Published as mp100,ptrak,$r?,v2634,^b,EU,gmrust,cs167398,ts8,^o^z
Game
gmrust- Game mode Rust survival, standard.
mp100- Max players The server has 100 slots.
ts8- Group limit Default team size: 8.
v2634- Protocol Protocol 2634: join only if your game matches this version.
cs167398- Build Running build 167398.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code Region code missing.
Wipe schedule
^b- Biweekly Two-week wipe cycle.
Mods and access
^o- Oxide Plugin framework: Oxide (uMod).
^z- Modded The Modded category applies; plugins or settings alter gameplay.
Region
EU- Europe In the server browser it appears under Europe.
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.