Local forecast
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Online 85.233.150.44:35020 checked 8m ago
Current conditions
observed 8m agoplayers now
0% full
- 7-day average
- 1
- peak 4
- Rank
- #3,893
- top 17%
- Last wipe
- 13d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
Next wipe
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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 bestTop 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.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 09:02 UKFri 16 Oct, 08:02 UTC · 13d ago | 3 | – | running | 0 |
| Fri 2 Oct, 13:59 UKFri 2 Oct, 12:59 UTC · 27d ago | 3 | halved by day 5 | 13.8 days | 0 |
| Thu 17 Sep, 20:34 UKThu 17 Sep, 19:34 UTC · 41d 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer details
Does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] hold a steady performance?
Server fps averaged 58 in the last 48 hours; the lowest was 23. At its peak the world had 92,864 entities, counting buildings, deployables and the rest. The peak memory draw was 3,529 MB. Players feel lag when fps drops and the entity count climbs.
How reliable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it online now?
Right now Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is up and running. Going by its reported uptime, the last restart was about 2 days 12 hours ago. In the last 7 full days it stayed up 167 of 168 hours, 99% of the time. It came to Rust Wipe Stats's notice first on 13 September 2026.
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run from?
There is no published region for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. The location Rust Wipe Stats shows is the one the server claims; the machine's real position is not looked up. 85.233.150.44:35020 is its address.
What version of Rust is running on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Rust network protocol 2635 and build 168909 on Linux is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs. The protocol must match for you to join, and Steam keeps it updated.
Lists and tags
Which meaning sits behind each tag on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
For the game's server browser, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes these tags: gmrust (Game mode): The mode is plain Rust survival; mp100 (Max players): Capacity: 100; ts8 (Group limit): Teams are at the game default of 8; v2635 (Protocol): Joining needs game protocol 2635 on your copy of the game; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the network layer, as standard for the game; $r? (Region code): This server carries no region code; ^o (Oxide): The plugins run through Oxide (uMod); ^z (Modded): Plugins or settings alter the game here, so it is listed under Modded. The tags hold the current players, the queue length and the world's creation time, and these appear at the top of this page.
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] appear among the Rust Wipe Stats lists and filters?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] appears in the following Rust Wipe Stats lists: 5x Rust servers: wipe and player forecast and Modded Rust servers. These filters on the server list will 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.
Map and rules
What map is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] on?
A procedural map of size 3,700 with seed 81405896, generated by the game, runs on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. From this page RustMaps opens it, since equal size and seed give an equal map.
What settings does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] use, and what rules does it enforce?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sets gather at 5x, according to its own name. No group setting is published, so the game default of 8 players applies. This server runs survival, gathering, building and raiding, as the game normally plays. You can fight other players and raid their bases. The server browser lists it as Modded, where plugins or settings alter the game. Plugin frameworks in use: Oxide. This server has VAC switched on.
Wipe times
On what schedule does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipe?
There is no next wipe to predict, because Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipes at irregular times. A monthly force wipe hits every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it is running now dates from 13 days 7 hours.
What should you expect from wipe day on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
At their busiest, its recent wipes averaged 3 players. Peak numbers on the latest wipe arrived 47 hours after the reset. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it did not hold, the crowd dropped under half by day 5.
Population
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] busy or quiet?
Out of 100 slots, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] has 0 filled right now. The seven-day average is 1 players, with a peak of 4. At 16:00 UTC it was busiest over the past 48 hours, averaging 1 players.
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] compare with other Rust servers in the rankings?
Player hours over the past week put Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at #3,893, inside the top 17% of all ranked servers.
Join the server
What do you do to join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Open the console in Rust with F1, then type client.connect 85.233.150.44:35020 to join. On this page, Launch Rust does the same through Steam. You can find its website at http://cloudrust.ru/.