Element card · group Modded · atomic number 3,897, its rank
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Online 85.233.150.44:35020 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
daily · 1 is best
Top 17% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 47 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 08:02 UTC12d ago | 3 | – | running | 0 |
| Fri 2 Oct, 12:59 UTC26d ago | 3 | halved by day 5 | 13.8 days | 0 |
| Thu 17 Sep, 19:34 UTC41d ago | 4 | halved by day 5 | 14.7 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 wipesQuick answers
from the figures on this pageSettings and map
What map is in play on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs a procedural map of size 3,700 with seed 81405896; the game generates it. You can view it on RustMaps from this page, since matching size and seed produce the same map.
How is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] configured, and what rules apply?
According to its name, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs 5x gather. With no change from the default, groups can hold up to 8 players. survival is the game mode, raiding, building and gathering: the standard game. Fighting and raiding between players are allowed. Plugins or settings change the game, so the browser lists it under Modded. Plugins in use: Oxide. The VAC anti-cheat from Valve is enabled.
Server details
What region hosts Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
There is no region on record for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. Connect at 85.233.150.44:35020.
On what Rust version does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] operate?
On Linux, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is running Rust network protocol 2635 and build 168909. Your game needs to match the protocol to join, and Steam updates it automatically.
How reliably does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] stay online?
At the moment, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is online. The uptime it reports suggests it restarted roughly 2 days 5 hours ago. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. The first sighting by Rust Data Lab was on 13 September 2026.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] known for smooth running?
Server fps averaged 58 over the last 48 hours, with 23 as the lowest. The maximum entity count was 92,864, covering buildings, deployables and all else in the world. Up to 3,441 MB of memory was used. Players feel lag when fps is low and the entity count climbs.
Wipe schedule
What is the wiping pattern on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
No next wipe can be predicted on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: its wipes come at irregular times. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. Counting back, the current world began 12 days 23 hours ago.
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] look on the day of a wipe?
Averaged across its recent wipes, the busiest point drew 3 players. 47 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of recent wipes. Where it did not hold, the crowd dropped below half by day 5.
Where it appears
What should you understand from the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] carries?
These are the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] makes public for the server browser to read: gmrust (Game mode): Standard Rust survival is the game here; mp100 (Max players): Player slots: 100; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins; ^z (Modded): Plugins or settings alter the game, so it lists under Modded. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.
Which Rust Data Lab filters and lists does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] appear in?
These themed Rust Data Lab lists carry Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: 5x Rust servers, measured live and Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 5x.
Player numbers
Against other Rust servers, where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] place?
The seven-day player-hours table has Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at #3,897, in the top 17% of ranked servers.
How many players does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] have at the moment?
At the moment Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] has 0 of its 100 slots filled. The week's figures average 1 players and top out at 4. The busiest point in the last 48 hours came at 13:00 UTC, averaging 2 players.
Getting on
How can you connect to Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
You can connect by pressing F1 in Rust and entering client.connect 85.233.150.44:35020, or by pressing Launch Rust here, which starts the game through Steam and joins for you. For more, visit http://cloudrust.ru/.