Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Online 85.233.150.44:35020 checked 9m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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| Server | Profile | Players now |
|---|---|---|
| MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10 | EU · groups of 1000+ · 5x · 121 on average | 45 / 250 |
| HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10x | NA · groups of 8+ · 5x · monthly · 116 on average | 129 / 150 |
| [EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | Kit | EU · groups of 100+ · 5x · 86 on average | 32 / 300 |
| WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPE | EU · groups of 40+ · 5x · weekly · 79 on average | 19 / 200 |
| AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10x | NA · groups of 8+ · 5x · monthly · 75 on average | 65 / 150 |
| Atlas - EU 5x | No BPs | Kits | EU · groups of 20+ · 5x · weekly · 63 on average | 17 / 100 |
Quick answers
from the figures on this pageWipe data
On what cycle does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipe?
The next wipe on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] cannot be predicted, because it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. 12 days 21 hours ago the current world was made.
Wipe day on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: what should you expect?
The average busiest count over recent wipes is 3 players. 47 hours after the latest wipe the crowd peaked. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. By day 5 it had fallen below half where the hold failed.
Server details
What is the hosting location of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
No region appears in what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 85.233.150.44:35020.
Which Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] on?
On Linux, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs Rust network protocol 2635 and build 168909. Your game must match the protocol to join, and Steam applies that update.
How reliable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it online now?
As of the latest refresh, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is online. The uptime it reports puts the last restart at about 2 days 3 hours ago. Uptime over the last full days (7) was 99%, or 167 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.
What performance does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] show?
Over 48 hours the average held at 58 server fps, and the minimum was 23. Entity count reached 92,864, covering buildings, deployables and the rest of the world. Memory use reached 3,390 MB at peak. A climbing entity count and low fps are the lag players perceive.
Lists and tags
Which meanings do the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] carry?
gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): Player slots: 100; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Plugins or settings change the game, so it sits under Modded are the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: 5x Rust servers, measured live and Modded Rust servers: live data. 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.
Population
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sit among Rust servers?
The seven-day player-hours rank for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is #3,910, inside the top 18% of all ranked servers.
At what level does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run its population?
Of 100 slots, 0 are filled on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at this refresh. Seven-day figures: an average of 1 players and a peak of 4. Averaged over 48 hours, activity is highest at 13:00 UTC with 2 players.
Map and rules
What settings and rules does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] use?
5x gathering is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] states in its name. The game's default 8-player group limit is in force. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. The Modded category lists it; plugins or settings change the game. Plugins from Oxide are in use. The server runs with VAC, Valve's anti-cheat, enabled.
The map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: which one is it?
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]. Size and seed fix the map, so a RustMaps view is available from this page.
How to join
What is the way onto Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 85.233.150.44:35020. http://cloudrust.ru/ is its website.