Skip to the story

Live edition40,419 playing on 11,701 servers

Rust Insights

Server profile

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

Online, with 0 of 100 players on; ranked #3,912 of every public Rust server, the top 18%. It last wiped 12d ago.

Filed under 5x moddedoxide
Launch Rust and join Website
The server's own banner, as it publishes it.
0/ 100 players now 0% full
17-day averagepeak 4
#3,912ranktop 18%
12d agolast wipeno schedule published
–next wipeno rhythm it keeps

The crowd

Players

Who is on it, hour by hour and day by day.

AveragePeak
0123402:0011:0020:0005:0014:0000:00

Note: hourly average and peak, UTC.

Under the hood

Server performance

Frames per second, entities and memory, asked of the server itself.

02040608002:0011:0020:0005:0014:0000:00

Note: 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.

The standings

Rank

Its place among every ranked server, day by day; 1 is best.

RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

The wipe cycle

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.

14.3 days usual gap between real wipes
100% on rhythm of its recent wipes
3 wipe-day peak players, last three wipes
0% crowd held else halves by day 5

The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe

Fri 16 OctFri 2 OctThu 17 Sep
01234+0h+9h+19h+28h+38h+47h

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

The record

Wipes

Every wipe we saw, 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 UTC41d ago 4 halved by day 5 14.7 days 0

Note: 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.

If you like this one

Similar servers

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

  1. MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10EU · groups of 1000+ · 5x · 120 on average37/300
  2. HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10xNA · groups of 8+ · 5x · monthly · 117 on average202/275
  3. [EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | KitEU · groups of 100+ · 5x · 85 on average58/300
  4. WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPEEU · groups of 40+ · 5x · weekly · 79 on average26/200
  5. Классика x5 для НОВИЧКОВ |Loot+|BigBoyRust|EU · groups of 8+ · 5x · weekly · 79 on average7/300
  6. AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10xNA · groups of 8+ · 5x · monthly · 74 on average110/150

The short version

Quick answers

From the figures on this page.

Wipe schedule

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

Recent wipes peaked at 3 players on average. 47 hours after the latest wipe, the crowd peaked. In 0% of recent wipes, more than half the peak was still playing at the next wipe. In the other cases, it dropped below half by day 5.

How often does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipe, and on which day?

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipes at times that vary, so its next wipe cannot be predicted. Next on Thursday 5 November at 19:00 UTC, every Rust server, this one included, takes the monthly force wipe. The world you are playing on now was made 12 days 17 hours ago.

Server

Does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] hold a steady frame rate?

Server fps averaged 58 over 48 hours; the lowest reading was 23. Buildings, deployables and the rest took the entity count as high as 92,864. Memory use peaked at 3,390 MB. What players feel as lag comes from low fps and an entity count on the rise.

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

The Rust build is network protocol 2635 and build 168909, running on Linux, for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. You can only join if your game is on the same protocol; Steam handles that update.

How reliable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it up at the moment?

Right now Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is up and running. Going by the uptime figure it gives, its last restart was around 47 hours ago. The last 7 full days gave 167 of 168 hours up, or 99% of the time. The first record Rust Insights has of it is 13 September 2026.

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

No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. Rust Insights reports the location a server declares, not the physical place of the machine. Connect through 85.233.150.44:35020.

Tags

What is meant by each tag on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

When the game's server browser reads Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): It holds 100 slots; ts8 (Group limit): This is the game default: 8 per team at most; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.

On which Rust Insights lists does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] appear?

The Rust Insights lists that carry Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] are 5x Rust servers, explained and Modded Rust servers, explained. These filters bring it up 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.

Population history

How many players are on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] right now, and how does that number move?

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] shows 0 players at the moment, against 100 slots. A weekly average of 1 players goes with a peak of 4. The busiest point of the last 48 hours fell at 13:00 UTC, averaging 2 players.

In the ranking of Rust servers, where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] place?

The player-hours ranking for the last seven days puts Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at #3,912, among the top 18% of all ranked servers.

Settings and rules

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

Going by its name, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] gathers at 5x. The default of 8 players per group is what applies here. survival is the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. It is a Modded entry: plugins or settings modify the game. Plugins: Oxide run here. Anti-cheat: VAC, from Valve, is on.

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

The game generates the map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: procedural, size 3,700, seed 81405896. You can look at the map on RustMaps from this page, since the same size and seed produce the same map.

Join

How can you get onto Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

To connect, start Rust and enter client.connect 85.233.150.44:35020 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you. http://cloudrust.ru/ is its website.

The small print

Server tags

What each one means.

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players It holds 100 slots.
ts8
Group limit This is the game default: 8 per team at most.
v2635
Protocol To join you need the same version; protocol 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking Rust's standard network layer, RakNet, carries it.
$r?
Region code No region code is set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), is in use.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Note: 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.