Artist page · Modded · on air
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Online 85.233.150.44:35020 checked 10m ago
- Last week
- No. 4,017
- Peak
- No. 3,101
- Days on chart
- 40
Rank
- 24 Sep4,260
- 1 Oct3,157
- 8 Oct4,584
- 15 Oct4,622
- 22 Oct4,017
- now3,912
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
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.
Wipe schedule
Its 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
| 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
- 1 MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10 40/ 300
- 2 HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10x 194/ 250
- 3 [EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | Kit 47/ 300
- 4 WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPE 27/ 200
- 5 Классика x5 для НОВИЧКОВ |Loot+|BigBoyRust| 7/ 300
- 6 AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10x 118/ 150
Quick answers
Reset schedule
What should you expect on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] when wipe day comes?
The busiest moments of its recent wipes averaged 3 players. It took 47 hours from the latest wipe for the crowd to peak. Above half the peak until the next wipe: that is what happened in 0% of its recent wipes. On the wipes that did not hold, the fall below half came by day 5.
On what schedule does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipe?
No next wipe can be predicted on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], which wipes at times that follow no pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, which clears every Rust server. 12 days 18 hours is how long the current world has been up.
Lists and filters
Which Rust Server Rank filters and lists does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] turn up in?
These Rust Server Rank lists feature Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: 5x Rust servers, charted and Modded Rust server rankings. Filter the server list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 5x and it shows up.
How should you read the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The game's server browser picks up the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes, which are: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The slot count is 100; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Your game has to match protocol 2635 to get in; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code is left blank; ^o (Oxide): Oxide (uMod), the plugin framework, is running here; ^z (Modded): The game is changed by plugins or settings, and the browser files it under Modded. You'll also find the current player count, the queue and when the world was made in the tags, shown at the top of this page.
Map and rules
On what map does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] play?
The map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is procedural, size 3,700, seed 81405896, generated by the game. The map is the same from the same size and seed, so RustMaps can show it from this page.
What rules apply on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and what settings does it use?
Gather rate on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is 5x, according to its name. Up to 8 players per group, which is the game's default. survival is the game mode, gather, build and raid in the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. Plugins running here: Oxide. Anti-cheat: Valve's VAC is on.
About the server
Which Rust build is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] running?
The setup is Rust network protocol 2635 and build 168909 on Linux, and that is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. Steam keeps it updated, but your game has to be on the same protocol to join.
How dependable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it online?
Right now Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is up and taking players. Its own uptime figure puts the last restart at roughly 2 days ago. Across the last 7 full days it stayed up for 167 of 168 hours, 99% of the time. It came to Rust Server Rank on 13 September 2026 for the first time.
What is performance like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The last 48 hours gave an average of 58 server fps, with a floor of 23. The world carried as many as 92,864 entities, buildings and deployables among them. Memory use reached 3,390 MB at its peak. Lag, to players, is those two things together: low fps and a rising entity count.
In which location is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] hosted?
There is no region published for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. It is where a server says it is that Rust Server Rank shows; where the machine stands is not looked up. You'll find it at 85.233.150.44:35020.
Population
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] a busy server?
Of 100 slots on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], 0 are taken at the moment. Averaging 1 players over the last week, it hit a high of 4. Its busiest hour in the last 48 hours was 13:00 UTC, when it averaged 2 players.
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] place in the rankings?
The last seven days of player hours rank Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at #3,913, inside the top 18% of ranked servers.
Join details
What is the way to join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
In Rust, press F1 and enter client.connect 85.233.150.44:35020 in the console. Launch Rust on this page is the other way: it opens the game through Steam and connects you. You can find its website at http://cloudrust.ru/.