Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]
OVR is 100 less its top share among ranked servers: top 19%.
Power level
Players on it, from the Steam server list.
Every five minutes.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Tale of the tape
Against its closest rival: the most similar server we track.
Wipe receipt
85.233.150.44:35020
THANK YOU · COME AGAIN NEXT WIPE
The map
Under the hood
Asked of the server directly. Low fps and a climbing entity count mean lag.
The ranking
Down 1397 places on last week. Top 19% of all ranked servers. Daily; 1 is best.
In its own words
Добро пожаловать на сервер Cloud #3 Карта: Procedural Увеличеные рейты: 5x Дата вайпа: 02.10 Продолжительность вайпа: раз в две недели Дискорд сервер: discord.gg/4qdMrnF Телеграм канал: t.me/cloudrust Сайт сервера: cloudrust.ru Группа ВК: vk.com/cloud9rust
Spec sheet
- Address
- 85.233.150.44:35020
- Region
- –
- Max players
- 100
- Group limit
- 8, the default
- Wipe schedule
- –
- Last wipe
- 2 Oct 2026, 12:59 UTC
- Hostname
- –
- First seen
- 13 Sep 2026
Other contenders
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Server rules
What are Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]'s rules and configuration?
5x gather. That is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] runs. It uses the default group size of 8 players. It plays as survival, the default game of gathering, building and raiding. You can fight and raid other players. The server browser lists it as Modded: plugins or settings alter the game. Oxide plugins are running on it. VAC is on: Valve's anti-cheat is running.
What's the map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
A procedural map of 3,700 with seed 1025831711 is in use on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10], made by the game. View it on RustMaps from this page: identical size and seed give an identical map.
Server tags
What are the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] for?
These tags come from Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] and go straight into the game's server browser: gmrust (Game mode): Survival as Rust normally plays; mp100 (Max players): Slot count: 100; ts8 (Group limit): The game default: 8 to a team; v2634 (Protocol): Get on protocol 2634 or the door stays shut; cs166652 (Build): Build 166652; ptrak (Networking): This runs on RakNet, the game's default network layer; $r? (Region code): Region code left blank; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): It is Modded: plugins or settings make the difference. From the tags, this page also pulls its live player count, its queue and its world's creation time, and puts them at the top.
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] appear in Boongarust lists?
On these Boongarust lists you will find Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]: 5x Rust servers and Top modded Rust servers. It appears on the server list when you filter by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 5x.
Server info
Performance of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]: does it hold up?
The 48-hour average was 59 server fps; the floor was 53. The entity count reached 91,298: buildings, deployables and the rest of the world. Memory use peaked at 3,132 MB. What players call lag is low fps plus a rising entity count.
Where can you find Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]. Boongarust takes the server at its word on location and does not check where the machine sits. Connect at 85.233.150.44:35020.
How often is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] online?
Offline now, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] was last seen 6 hours ago. The uptime it reports suggests a restart around 23 hours ago. 156 hours out of 168 across the last 7 full days. 93% uptime. It entered Boongarust's records on 13 September 2026.
What Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] using?
On Linux, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] runs Rust network protocol 2634 and build 166652. Steam keeps your game updated; you need the same protocol to connect.
Wipe times
Wipe day at Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]: what's it like?
Across recent wipes, the average peak was 4 players. 46 hours after the latest wipe, the crowd hit its peak. In 0% of recent wipes, half the peak was the floor until the next wipe. The fall below half came by day 5 when it did not hold.
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] wipes on what schedule?
The record holds too few of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]'s wipes to tell its rhythm. The monthly force wipe hits every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world you are on was made 5 days 18 hours.
Player counts
Ranking wise, where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] place?
In the top 19% of all ranked servers, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] is #4,554 on player hours over the last seven days.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] busy?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] last showed life 6 hours ago; it is offline now. It averaged 1 players over the last seven days and peaked at 4. Over the last 48 hours, the busiest hour was 19:00 UTC, averaging 2 players.
How to join
How can you get into Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
To connect, open the console with F1 in Rust and type client.connect 85.233.150.44:35020. You can also use Launch Rust on this page to open Rust via Steam and connect. You can find its website at http://cloudrust.ru/.
Sticker sheet
Every tag it publishes, and what it means. Published as mp100,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z.
Flag meanings are Facepunch's.
