Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]
85.233.150.44:35020 checked 8m ago
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
Top 22% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 14.7 days between real wipes
- wipe-day peak
- 4 players, last three wipes
- crowd held
- 0% else halves by day 5
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 46 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 12:59 UTC 12d ago | 3 | – | running | 0 |
| Thu 17 Sep, 19:34 UTC 26d 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
Quick answers
Player Count
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] ranking: what position does it hold?
Over the last seven days, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] ranks #4,812 in player hours, which is in the top 22% of ranked servers.
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]: 0 players now, with 100 slots available. The average player count over the last seven days is 0, with a peak of 3. In the last 48 hours, 15:00 UTC saw the highest activity, with an average of 2 players.
Tags and Filters
How should the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] be interpreted?
For Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10], the game's server browser reads the following tags: gmrust (Game mode): Standard survival gameplay; mp100 (Max players): Slot count is 100; ts8 (Group limit): The game default is 8 per team; v2634 (Protocol): Protocol 2634: join only if your game matches this version; cs167781 (Build): Running build 167781; ptrak (Networking): Network layer: RakNet, the standard; $r? (Region code): Region code missing; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it appears under Modded. Current players, queue and world creation time come from the tags and appear at the top of this page.
Which lists and filters on BestRustServers.xyz contain Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
These BestRustServers.xyz lists include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]: Best 5x Rust servers and Best modded Rust servers. It appears under these filters 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.
Server Details
What Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] on?
Rust network protocol 2634 and build 167781 on Linux is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] uses. Joining requires the same protocol; Steam updates your game for you.
Is the performance on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] smooth?
Its average server fps over the last 48 hours was 58, with a low of 39. Buildings, deployables and the rest of the world accounted for up to 92,353 entities. Memory use peaked at 3,272 MB. What players experience as lag is low fps combined with a rising entity count.
What is the uptime and reliability of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
The server is online: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]. About 11 hours ago is when it last restarted, based on its uptime. It was up 91% of the time over the last 7 full days, 153 of 168 hours. On 13 September 2026, BestRustServers.xyz saw it for the first time.
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] location: where is it?
No region is given by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]. BestRustServers.xyz shows the stated location of a server; the actual location of the machine is not looked up. 85.233.150.44:35020 is its address.
Rules and Settings
Which map is used on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
A procedural map of size 3,700 and seed 1025831711 is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] runs, generated by the game. On RustMaps, from this page, the same size and seed show the same map.
What are the settings and rules for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] carries its gather rate in its name: 5x. The default cap of 8 players per group is in force. Listed as survival, gather, build, raid: the standard game. Player combat and raiding are enabled. The Modded section of the browser holds it: plugins or settings apply. Plugins in use: Oxide. VAC: on.
Wipe Schedule
When does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] wipe?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]'s wipe rhythm cannot be told from the wipes on record, which are too few. On Thursday 5 November at 19:00 UTC the next force wipe arrives, when all Rust servers wipe. Its world dates from 12 days.
What happens on wipe day on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
The average busiest point of its recent wipes was 4 players. 46 hours into the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 0% of its recent wipes. In the wipes where it did not hold, half the peak was lost by day 5.
Connect
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] joining: how is it done?
To connect, type client.connect 85.233.150.44:35020 in the F1 console. Launch Rust on this page opens Rust through Steam and joins you. http://cloudrust.ru/ is its website.
Server tags
Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust- Game mode Standard survival gameplay.
mp100- Max players Slot count is 100.
ts8- Group limit The game default is 8 per team.
v2634- Protocol Protocol 2634: join only if your game matches this version.
cs167781- Build Running build 167781.
ptrak- Networking Network layer: RakNet, the standard.
$r?- Region code Region code missing.
Mods and access
^o- Oxide Plugin framework: Oxide (uMod).
^z- Modded Plugins or settings alter the game, so it appears under Modded.
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.