A168/ 150 players
Modded#4,860
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]
Online 85.233.150.44:35020 checked 8m ago
5x
moddedoxide
players now0of 100 slots
7-day average0peak 3
rank#4,860top 22%
last wipe · restocked11d agono schedule published
next wipe · restock–too few wipes seen yet
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 bestRankRank in region
Top 22% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
14.7 daysusual gapbetween real wipes
4wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 5
The first 48 hours of its last wipes
Fri 2 OctThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 3, 46 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 12:59 UTC11d ago | 3 | – | running | 0 |
| Thu 17 Sep, 19:34 UTC26d 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.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A225/ 250 players
A311/ 300 players
B1118/ 150 players
B20/ 300 players
B37/ 100 players
On the back of the pack
Quick answers
From the figures on this page.
Lists and tags
What is the meaning of the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
The server browser reads these tags that Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] publishes: gmrust (Game mode): The standard survival game mode; mp100 (Max players): 100 player slots; ts8 (Group limit): Teams cap at 8, the standard game limit; v2634 (Protocol): To join, your game version must line up with protocol 2634; cs167781 (Build): It runs on build 167781; ptrak (Networking): Network runs on RakNet, the game's standard; $r? (Region code): Region code not set; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): Modded is its category, with plugins or settings changing the game. You will find its live player count, queue and world creation time in the tags too, displayed at the top here.
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] appear in the lists and filters on Rust Vending Machine?
The Rust Vending Machine lists that feature Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] are: Top 5x Rust servers and Modded Rust servers. 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.
Rules & map
Which map is currently on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
A procedural map, size 3,700 with seed 1025831711, generated by the game, is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] runs. The map is the same for a given size and seed, so RustMaps can show it from this page.
Which settings and rules apply on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] is named for its 5x gather rate. The group limit is 8 players, the game's default. This server runs survival, the usual 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. The plugins it runs number Oxide. The server has VAC, Valve's anti-cheat, switched on.
Server info
What location is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] in?
No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]. Rust Vending Machine reports the location a server claims, not where the machine actually sits. You can reach it at 85.233.150.44:35020.
How stable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10], and is it currently online?
The shelves show Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] in stock and online right now. Its uptime figure puts the last restart at roughly 2 hours ago. Over 7 full days, the shelves were stocked for 153 of 168 hours (91%). It came to Rust Vending Machine's notice on 13 September 2026.
What is the performance like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
Server fps over the last 48 hours averaged 58 and never dropped below 39. At its peak it held 94,545 entities, counting buildings, deployables and all else in the world. The highest memory reading was 3,272 MB. Lag, as players feel it, is low fps plus a growing entity count.
Which Rust build is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] running?
The setup: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] on Linux, Rust network protocol 2634 and build 167781. The protocol has to line up on your side to join, and Steam does the updating.
Live players
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] compare to other Rust servers in the rankings?
The last seven days of player hours place Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] at #4,860, in the top 22% of all ranked servers.
How many players are on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] right now?
Right now 100 slots in Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] hold 0 players. It peaked at 3 this week, and the average was 0. The last 48 hours peaked at 09:00 UTC, when it averaged 2 players.
Wipe info
When does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] wipe?
The wipes of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] on record are too few to show its rhythm. The next force wipe is on Thursday 5 November at 19:00 UTC, when every Rust server wipes. The world it has now started 11 days 15 hours ago.
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] handle wipe day?
An average of 4 players turned up at the peak of its recent wipes. On the latest wipe, 46 hours after it began, the crowd peaked. Until the next wipe, in 0% of recent wipes, the crowd remained above half that peak. By day 5 the crowd had dropped below half in the wipes that failed to hold.
Join the server
What steps do you take to join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
Open Rust and press F1 for the console, then type client.connect 85.233.150.44:35020. Or use the Launch Rust button here to open the game through Steam and connect. You can find its website at http://cloudrust.ru/.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game mode The standard survival game mode.
mp100
Max players 100 player slots.
ts8
Group limit Teams cap at 8, the standard game limit.
v2634
Protocol To join, your game version must line up with protocol 2634.
cs167781
Build It runs on build 167781.
ptrak
Networking Network runs on RakNet, the game's standard.
$r?
Region code Region code not set.
Mods and access
^o
Oxide It uses Oxide (uMod) for plugins.
^z
Modded Modded is its category, with plugins or settings changing the game.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.