Top Rust ServersObservatory · live
Live Servers11,449 Players35,804 Populated3,100 Fresh wipes · 3h68 Scanevery 5 min

RS-4856Modded server

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

Online 85.233.150.44:35020 checked 13m ago

5x moddedoxide
Connect
Players now
0/ 100
0% full
7-day average
0
peak 3
Rank
#4,856
top 22%
Last wipe
11d ago
no schedule published
Next wipe
–
too few wipes seen yet
Light curve

Players

AveragePeak
00.511.5208:0017:0002:0011:0020:0005:00

Hourly average and peak, UTC.

Systems telemetry

Server performance

02040608008:0017:0002:0011:0020:0005:00

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.

Standing

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Orbit

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap14.7 daysbetween real 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.

Record

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Nearby objects

Similar servers

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

Readouts in words

Quick answers

From the figures on this page.

Population

How populated is 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 showing 0 players on 100 slots right now. Over seven days it averaged 0, and the highest point was 3. At 09:00 UTC it was busiest in the last 48 hours, averaging 2 players.

How is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] ranked?

On player hours across seven days, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] is #4,856, inside the top 22% of all ranked servers.

Server tags and lists

Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] appear among the Top Rust Servers lists and filters?

These Top Rust Servers lists include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]: Best 5x Rust servers and Top 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.

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

The game's server browser reads the tags that Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] publishes: gmrust (Game mode): Standard survival, as in Rust; mp100 (Max players): There are 100 slots; ts8 (Group limit): The team limit is 8, which is the game default; v2634 (Protocol): Protocol 2634 is required to join; your game must be on the same version; cs167781 (Build): The game build is 167781; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): No region code is assigned; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): It appears in Modded, as plugins or settings modify the game. At the top of this page you also see its players now, its queue, and the time its world was made, taken from the tags.

Map and rules

Which map is running 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] runs a procedural map of size 3,700 with seed 1025831711, generated by the game. Viewing it on RustMaps is possible from this page: the same size and seed give the same map.

Which settings and rules apply on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?

The name Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] includes a 5x gather rate. Groups use the default maximum of 8 players. survival is the game mode, the normal mode where you gather, build and raid. Player versus player combat and raiding are enabled. The server browser lists it under Modded: plugins or settings alter the game. Oxide plugins are in use. VAC anti-cheat is active.

About the server

What version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] running?

On Linux, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] operates Rust network protocol 2634 and build 167781. Your game needs the same protocol to connect; Steam takes care of updating it.

What is the performance like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?

Over the last two days, it ran at an average of 58 server fps, minimum 39. Its entity count reached 94,545, including buildings, deployables and all other objects. Its memory use reached 3,272 MB at most. A climbing entity count and low fps are the source of the lag players feel.

Where can Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] be found?

A region is not published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. You reach it at 85.233.150.44:35020.

How reliable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?

Right now, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] is up and running. The uptime it gives suggests a restart around 4 hours ago. Across the last 7 full days, it was online for 153 of 168 hours, or 91%. It was first observed by Top Rust Servers on 13 September 2026.

Wipe details

What can you expect on wipe day on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?

Recent wipes saw an average peak of 4 players at their busiest. 46 hours after the latest wipe, the crowd hit its peak. Half the peak was held until the next wipe in 0% of recent wipes. If the crowd did not stay above half, it fell below that mark by day 5.

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

The record holds too few wipes to determine Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]'s pattern. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. Its world was last replaced 11 days 18 hours ago.

Connection

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

To connect manually, open the console with F1 and type client.connect 85.233.150.44:35020. Or click Launch Rust on this page to open Rust through Steam and connect directly. You can find its website at http://cloudrust.ru/.

Spectrum

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival, as in Rust.
mp100
Max players There are 100 slots.
ts8
Group limit The team limit is 8, which is the game default.
v2634
Protocol Protocol 2634 is required to join; your game must be on the same version.
cs167781
Build The game build is 167781.
ptrak
Networking This uses RakNet, Rust's default network layer.
$r?
Region code No region code is assigned.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded It appears in Modded, as 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.