Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Online 85.233.150.44:35020 checked 10m ago
Players now
Live- Full
- 0%
- In queue
- 0
- Peak, 48 hours
- 3
- Peak, 7 days
- 4
0% full
Rank
top 18%
7-day average
peak 4
Last wipe
no schedule published
Next wipe
no rhythm it keeps
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 18% 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 wipes- 1 39/ 300
- 2 213/ 250
- 3 42/ 300
- 4 29/ 200
- 5 115/ 150
- 6 25/ 100
Quick answers
from the figures on this pageServer details
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] online, and how reliable is it?
Players can join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: it is online. About 2 days ago it restarted, judging by the uptime figure it gives. It was online 99% of the last 7 full days, which is 167 of 168 hours. The first time Rust Dashboard recorded it was 13 September 2026.
Which version of Rust does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?
On Linux, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs Rust network protocol 2635 and build 168909. Steam keeps your game updated, so it will be on the same protocol and able to join.
Where is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] located?
No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. The location shown at Rust Dashboard is the one the server states; no lookup of the machine's position happens. 85.233.150.44:35020 is where it lives.
Does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run smoothly?
Server fps averaged 58 over the last 48 hours and never dropped below 23. Buildings, deployables and everything else added up to a peak of 92,864 entities. At its highest, it took 3,390 MB of memory. Players feel lag when fps drops and the entity count climbs.
Lists
Which Rust Dashboard lists and filters include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
You'll find Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] on these themed lists at Rust Dashboard: 5x Rust servers and Modded Rust servers, live now. These filters bring it up 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?
The game's server browser reads these tags from Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: gmrust (Game mode): This is Rust as it comes, with survival rules unchanged; mp100 (Max players): It holds 100 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build 168909 is what it runs; ptrak (Networking): RakNet is the standard network layer for the game, and it is what runs here; $r? (Region code): The region code is blank; ^o (Oxide): This server runs Oxide (uMod) for plugins; ^z (Modded): Modded is where it sits: plugins or settings change how the game plays. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
Population
How busy is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] has 0 of its 100 slots filled at the moment. Its seven-day average is 1 players, and it reached 4 at the highest. It was busiest at 13:00 UTC over the last 48 hours, when it averaged 2 players.
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] rank against other Rust servers?
Player hours over seven days put Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at #3,917, in the top 18% of all ranked servers.
Reset times
What does wipe day look like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
At their busiest, its recent wipes drew 3 players on average. On the latest wipe, 47 hours passed before the crowd peaked. Above half that peak until the next wipe: that held in 0% of recent wipes. When that did not happen, the crowd was below half by day 5.
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: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipes at irregular times. The monthly force wipe applies to every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it runs now dates from 12 days 19 hours ago.
Map and rules
What are the rules and settings on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
A gather rate of 5x appears in the name of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. Groups hold up to 8 players, the default for the game. It runs survival, the usual game, where you gather, build and raid. Raids and player fights are part of the game here. Plugins or settings alter the game, so the browser puts it under Modded. Oxide plugins run on it. The anti-cheat from Valve, VAC, is active.
Which map does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?
The game generates the procedural map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], size 3,700 with seed 81405896. Because size and seed fix the map, a RustMaps view is available from this page.
Connect
How do I join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Type client.connect 85.233.150.44:35020 in the Rust console, which F1 opens. Launch Rust on this page also works: Steam opens Rust and connects you. You can find it online at http://cloudrust.ru/.