Skip to the content
Dive report

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]

Online 85.233.150.44:35020 checked 8m ago

5x moddedoxide
Drop in
0/ 100 players now 0% full
07-day averagepeak 3
#4,801ranktop 22%
1d agolast wipeno schedule published
–next wipeno rhythm it keeps

Players

AveragePeakWipe
00.250.50.75105:0014:0023:0009:0018:0003:00Wiped Fri 16 Oct, 08:02 UTCWIPE

Hourly average and peak, UTC.

Server performance

Server fpsWipe
02040608005:0014:0023:0009:0018:0003:00Wiped Fri 16 Oct, 08:02 UTCWIPE

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 best
RankRank in region
12k4k6k8k20 Sep26 Sep1 Oct7 Oct12 Oct18 Oct

Top 22% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap14.3 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 5

The first 48 hours of its last wipes

Fri 2 OctThu 17 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 46 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 08:02 UTC1d ago – – running 0
Fri 2 Oct, 12:59 UTC15d ago 3 halved by day 5 13.8 days 0
Thu 17 Sep, 19:34 UTC30d 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.

Neighbouring dive spots

Similar servers

the same kind of game, then region, group limit, rate and wipes

From the figures on this page

Quick answers

Tags and search

Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] appear in Rust Going Deep lists and filters?

These Rust Going Deep lists include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: 5x Rust servers and Modded Rust servers. You can find it on the server list by these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days; Gather rate: 5x.

What's the meaning of the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

gmrust (Game mode): This is the standard Rust survival experience; mp100 (Max players): The slot count is 100; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): The build number is 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game — that is the tag list Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.

About the server

Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] lag-free?

Average server fps for the last 48 hours was 58, and the lowest was 14. At its peak it carried 92,172 entities, including buildings and deployables. 2,815 MB was the highest memory it used. What players notice as lag comes from low fps and a rising entity count.

What's the location of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 85.233.150.44:35020.

Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] up, and how often does it stay online?

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is live as of this check. According to its reported uptime, the last restart was about 2 hours ago. Over the past full 7 days it stayed up for 168 of 168 hours, or 100%. Rust Going Deep has had it on record since 13 September 2026.

What Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] on?

Rust network protocol 2634 and build 167781 is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs, on Linux. To join, your game must be on the same protocol; Steam takes care of updating it.

Wipe details

When does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipe?

There is no next wipe to predict because Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipes at irregular times. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 44 hours ago.

What happens on wipe day at Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

Recent wipes have averaged a busiest crowd of 4 players. On the latest wipe, 46 hours passed before the crowd peaked. Recent wipes kept the crowd above half that peak until the next wipe 0% of the time. It held on until day 5, then dipped below half.

Map and rules

What settings and rules have been applied to Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

Gather rates here are 5x, as Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] announces in its name. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.

Which map is active on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

The map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is procedural and size 3,700, generated by the game with seed 81405896. RustMaps can display it from this page because the same size and seed yield the same map.

Player count

What's the population like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

Out of 100 slots, 0 are filled on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] right now. The seven-day average is 0 players, with a peak of 3. At 05:00 UTC in the last 48 hours, the average reached its highest: 1 players.

Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sit in the rankings?

For player hours in the last seven days, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] ranks #4,801, within the top 22% of ranked servers.

How to join

What's the process to join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

To join, open Rust, hit F1, and enter client.connect 85.233.150.44:35020. Or click Launch Rust on this page to open the game through Steam and connect. You can find its website at http://cloudrust.ru/.

What each one means

Server tags

Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode This is the standard Rust survival experience.
mp100
Max players The slot count is 100.
ts8
Group limit The default team size of 8 applies here.
v2634
Protocol To join, your game has to be on protocol 2634.
cs167781
Build The build number is 167781.
ptrak
Networking RakNet, the network layer Rust uses by default.
$r?
Region code No region is set.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded You'll see it in Modded, since plugins or settings modify 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.