StatusLive Servers online11,829 Players89,289 Populated4,008 Wiped · 3 h42 Interval5 min Date28 OCT 2026

DWG RG-S3971Server sheetchecked 2h ago

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

Online 85.233.150.44:35020 checked 2h ago

5x moddedoxide
Connect
Players now 0/ 100 0% full
7-day average1peak 4
Rank#3,971top 18%
Last wipe12d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
0123420:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Fig. 1Players on Cloud #3...
Fig. 2

Server performance

02040608020:0005:0014:0023:0008:0017: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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 peak3players, last three wipes
crowd held0%else halves by day 5

The first 48 hours of its last wipes

Fri 16 OctFri 2 OctThu 17 Sep
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

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

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10xNA · groups of 8+ · 5x · monthly · 119 on average
54 / 150
02
MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10EU · groups of 1000+ · 5x · 118 on average
234 / 300
03
[EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | KitEU · groups of 100+ · 5x · 84 on average
257 / 300
04
Классика x5 для НОВИЧКОВ |Loot+|BigBoyRust|EU · groups of 8+ · 5x · weekly · 81 on average
78 / 300
05
WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPEEU · groups of 40+ · 5x · weekly · 78 on average
151 / 200
06
AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10xNA · groups of 8+ · 5x · monthly · 73 on average
78 / 150
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

What uptime is recorded for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it up?

At this moment Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is online. About 39 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. On 13 September 2026 is when Rust Graphs first saw it.

Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] stable in the figures recorded?

Average server fps over the last 48 hours is 56; the lowest was 18. Counted at its highest: 92,864 entities, buildings, deployables and the rest of the world included. 3,263 MB is the memory peak. Players feel low fps and a climbing entity count as lag.

In which location is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] hosted?

No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 85.233.150.44:35020.

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

The platform is Linux and the version is Rust network protocol 2635 and build 168909 on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. To join, your game must be on the same protocol; Steam handles the update.

Counts

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

0 of 100 slots on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] are taken at the latest refresh. Averaged across seven days, the player count is 1, with a peak of 4. Over the last 48 hours the busiest hour was 13:00 UTC, at an average of 2 players.

What rank has been recorded for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

Over the last seven days, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] records #3,971 for player hours: the top 18% of all ranked servers.

Schedules

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

At their busiest, its recent wipes drew 3 players on average. 47 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. By day 5 the crowd had fallen below half on the wipes where it did not hold.

What wipe schedule has been recorded for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

There is no next wipe to predict at Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], which wipes at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The current world has been in use since 12 days 11 hours ago.

Rules and settings

Which settings does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run, and what rules?

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] takes its gather rate from its name: 5x. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.

What is the map for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs a procedural map of size 3,700 with seed 81405896, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

On Rust Graphs, which lists and filters contain Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

The Rust Graphs lists that carry Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] are: 5x Rust servers, by gather rate and Modded Rust servers. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 5x.

Which meaning is attached to each tag on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): Slots: 100; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded are the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

How to join

What is the way to connect to Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

Enter client.connect 85.233.150.44:35020 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. http://cloudrust.ru/ is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival, as Rust plays.
mp100
Max players Slots: 100.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build 168909 is the game build.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code field is empty.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed 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.

KeyTag string decoded