Online 85.233.150.44:35020 checked 8m ago
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
By the numbersMatch stats
against its 100 slotsThe story of the match
Players, performance and rank, hour by hour and day by day.
CrowdPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
FitnessServer 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.
FormRank
daily · 1 is bestTop 18% of all ranked servers. Ranked on player hours over the last seven days.
FixturesWipe 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.
ResultsWipes
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.
Quick answers
From the figures on this page.
About the server
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] online, and how reliable is it?
Online now, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is up. Going by the uptime it reports, the last restart came about 44 hours ago. The last 7 full days put it at 168 of 168 hours up, 100% uptime. On 13 September 2026, Rust Player Stats saw it for the first time.
Does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run smoothly?
57 server fps on average over 48 hours, and never under 18. Up to 92,864 entities sat in the world, buildings and deployables included. Memory use reached 3,390 MB. Lag, to a player, is these two together: low fps and a rising entity count.
Which Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] on?
Rust network protocol 2635 and build 168909 on Linux: that is the setup at Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. Same protocol or no entry: your game must match, and Steam keeps it updated for you.
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]. Where the machine physically stands is not looked up by Rust Player Stats; it shows only what the server states. You will find it at 85.233.150.44:35020.
Lists and filters
What do the server tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] mean?
Tags published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] and picked up by the in-game browser: gmrust (Game mode): The standard Rust survival rules apply here; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default 8 per team applies here; v2635 (Protocol): Game protocol 2635: join only if your game matches that version; cs168909 (Build): The game build here is 168909; ptrak (Networking): The network layer is RakNet, the standard one; $r? (Region code): There's no region code on this one; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Modded is its category: plugins or settings change how it plays. At the top of this page the tags give you its players right now, its queue and the date its world was created.
Which Rust Player Stats lists and filters include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The Rust Player Stats lists that include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] are: 5x Rust servers, live and ranked and Modded Rust servers, live. Searching the server list with these filters returns it: 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
Which map is running on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The procedural map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is size 3,700, generated by the game from seed 81405896. You can look at it on RustMaps from this page, since size and seed give the same map.
What are the rules and settings on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Gather rate for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is 5x, straight from its name. The cap is 8 players per group, the game's default. build, gather and raid in the standard game: that is the survival game mode. PvP is on, and so is raiding. Under Modded in the server browser: the game is changed by plugins or settings. Oxide plugins are running. VAC is on, so Valve's anti-cheat is watching.
Population
How full is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] right now?
The board shows Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at 1 players, with 100 slots in total. The seven-day average sits at 1 players; the peak reached 4. The busiest stretch of the last 48 hours came at 13:00 UTC, averaging 2 players.
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sit in the rankings?
Player hours over seven days place Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at #3,923, among the top 18% of ranked servers.
Wipe schedule
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 for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe lands, and every Rust server wipes. 12 days 14 hours ago, its current world was made.
What does wipe day look like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
3 players on average is what its recent wipes drew at their busiest. 47 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. By day 5, it had fallen below half when it didn't hold.
How to join
How do I join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Press F1 in Rust, bring up the console and enter client.connect 85.233.150.44:35020. The Launch Rust button here does the same, opening Rust via Steam and connecting you. http://cloudrust.ru/ is where its website lives.
GlossaryServer tags
what each one meansPublished as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp100
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
^z
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.