On air · chart position #3,943
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Online 85.233.150.44:35020 checked 11m ago
Players
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
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 18% of all ranked servers. Ranked on player hours over the last seven days.
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
Quick answers
About the server
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] online, and how reliable is it?
You will find Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] online at this moment. The uptime it reports puts its last restart about 43 hours ago. It stayed up 100% of the last 7 full days, 168 of 168 hours. Rust Charts has tracked it since 13 September 2026.
Where is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] located?
There's no region listed for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. Where a server says it is — that's what Rust Charts shows, without checking the machine's real location. Connect at 85.233.150.44:35020.
Which version of Rust does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?
Rust network protocol 2635 and build 168909 on Linux is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs. Steam updates your game for you; all you need is the same protocol to join.
Does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run smoothly?
The 48-hour average was 57 server fps; the lowest point was 18. At its fullest it held 92,864 entities: buildings, deployables and the rest of the world. Its memory climbed as high as 3,390 MB. Rising entity counts and low fps are the source of the lag players report.
Player counts
How busy is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Right now 1 players are on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], out of 100 slots. Seven-day figures: 1 players on average and 4 at the peak. The busiest stretch of the last 48 hours came at 13:00 UTC, averaging 2 players.
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] rank against other Rust servers?
Player hours over the past week put Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at #3,943, among the top 18% of ranked servers.
Wipe schedule
What does wipe day look like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The busiest point of its recent wipes averaged 3 players. 47 hours into the latest wipe, the crowd reached its peak. Half the peak was the floor until the next wipe in 0% of recent wipes. By day 5 it had fallen 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]?
With irregular wipe times on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], the next wipe cannot be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and it covers every Rust server. The world in play was made 12 days 13 hours.
How it is set up
What are the rules and settings on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
A gather rate of 5x is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] advertises in its name. The default group size of 8 players applies here. survival is the game mode, raid, build and gather: the standard game. You can fight and raid other players. Modded in the server browser is where it sits; plugins or settings alter the game. Oxide plugins are running on it. Valve's VAC anti-cheat is active.
Which map does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?
A procedural map of size 3,700 with seed 81405896, generated by the game, is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs. From this page you can look at it on RustMaps; the same size and seed make the same map.
Tag guide
Which Rust Charts lists and filters include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
These Rust Charts lists include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: Best 5x Rust servers and Modded Rust servers. These filters on the server list bring it up: 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?
gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): It has 100 slots; ts8 (Group limit): 8 per team, as the game ships it; v2635 (Protocol): Protocol 2635: join only if your game matches that version; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's usual one; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): This one is modded, so plugins or settings alter play — that's the set of tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes for the server browser. The tags also carry the current player count, the queue and when the world was made. You'll find them at the top of this page.
Join details
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, which F1 opens once Rust is running. Launch Rust and join on this page is the other way: Rust opens through Steam and connects you. You can find its website at http://cloudrust.ru/.