Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Online 85.233.150.44:35020 checked 10m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 18% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The average peak across its recent wipes is 3 players. The crowd on the latest wipe reached its peak 47 hours in. Above half the peak until the next wipe: that held in 0% of its recent wipes. By day 5 it was below half in the wipes that did not hold.
What is the wipe schedule on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
There is no next wipe to predict on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], which wipes at irregular times. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 12 days 16 hours ago.
Population
How busy is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The current population of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is 0, against 100 slots. Averaged over the past week: 1 players, peaking at 4. Look at 13:00 UTC for the last 48 hours: that hour averaged 2 players.
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] rank against other Rust servers?
The top 18% of ranked servers includes Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], at #3,914 for player hours over the last seven days.
Rules and settings
Which map does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?
The map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is procedural, size 3,700 with seed 81405896, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map.
What are the rules and settings 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]'s name indicates a gather rate of 5x. 8 players is the default group size, and that is the limit here. survival is the game mode, standard play: gathering, building and raiding. You can fight other players and raid their bases. In the server browser it is Modded, meaning plugins or settings modify the game. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?
The build on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is Rust network protocol 2635 and build 168909, running on Linux. Your game must run the same protocol to join, and Steam takes care of updating it.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] online, and how reliable is it?
Online now: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. The uptime it reports puts the last restart at about 46 hours ago. 144 of 168 hours up over the last 7 full days, which is 86%. The first record of it on Rust Heatmap is 13 September 2026.
Where is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] located?
A region is not published for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. Rust Heatmap shows the location a server states. It does not look up the machine's location. To connect, use 85.233.150.44:35020.
Does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run smoothly?
It averaged 58 server fps over the last 48 hours, with a low of 23. Entities peaked at 92,864, counting buildings, deployables and all the rest of the world. Memory use reached 3,390 MB at most. Players feel lag when fps falls and the entity count climbs.
Lists and filters
Which Rust Heatmap lists and filters include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The Rust Heatmap lists that Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] fits are: 5x Rust servers, listed by population and Modded Rust servers, by live population. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 5x.
What do the server tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] mean?
These are the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp100 (Max players): The slot count is 100; ts8 (Group limit): At most 8 per team: the default the game ships with; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): This build is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Listed as Modded, since settings or plugins change the game. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
How to join
How do I join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Enter client.connect 85.233.150.44:35020 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you. You can find it online at http://cloudrust.ru/.