Rust Server IndexCard catalogue of Rust servers

Holdings11,846 servers84,816 players288 fresh wipes

Call no.5X3901 On the shelf · online

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

Online 85.233.150.44:35020 checked 9m ago

Subjects 1. 5x 2. modded3. oxide
Players now
0/ 100
0% full
7-day average
1
peak 4
Rank
#3,901
top 18%
Last wipeWiped16 OCT2026 · 13d 6h ago
13d ago · no schedule published
Next wipe
–
no rhythm it keeps
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
0123415:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

02040608015:0000:0009:0019:0004:0013: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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Record sheet D · loan terms

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 gap
14.3 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
0%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

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

Record sheet E · date due

Wipes

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

Shelf list · shelved beside it

Similar servers

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

EU5X
MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10EU · groups of 1000+ · 5x · 122 on average
204/ 250
NA5X
HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10xNA · groups of 8+ · 5x · monthly · 116 on average
127/ 150
EU5X
[EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | KitEU · groups of 100+ · 5x · 87 on average
200/ 300
EU5X
WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPEEU · groups of 40+ · 5x · weekly · 80 on average
103/ 200
NA5X
AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10xNA · groups of 8+ · 5x · monthly · 75 on average
34/ 150
EU5X
Atlas - EU 5x | No BPs | KitsEU · groups of 20+ · 5x · weekly · 64 on average
139/ 150
Reference desk

Quick answers

From the figures on this page.

Rules and settings

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

By its name, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] gathers at 5x. The default group limit of 8 players applies. Filed under survival, building, gathering and raiding in the standard game. Combat and raiding between players are possible. Plugins or settings change the game; it is listed under Modded in the server browser. Oxide plugins are run on it. The server has VAC, Valve's anti-cheat, turned on.

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

Size 3,700, seed 81405896: the game generates the procedural map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. From this page you can view the map on RustMaps; the same size and seed give the same map.

Tags

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

These lists on Rust Server Index take Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: 5x Rust servers, filed by gather rate and Modded Rust servers, filed by play style. These filters on the server list 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.

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

The server's own tags are listed here, and the game's server browser reads them: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] gives gmrust (Game mode): Rust survival, as standard; mp100 (Max players): Player cap: 100; ts8 (Group limit): Game default applies: teams of up to 8; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): Build on file: 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): A region code is absent; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or changed settings put this under Modded. The top of this page shows three items from the tags: players at present, queue and world creation time.

Wipe schedule

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

The average peak across its recent wipes is 3 players. 47 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases, numbers dropped below half by day 5.

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

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipes at times that follow no pattern, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The world it runs now was made 13 days 6 hours.

Players and ranking

What position does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] hold among Rust servers?

The seven-day player-hours ranking places Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at #3,901, among the top 18% of ranked servers.

What does the player count on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] look like?

Filed under live counts: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], 0 players on 100 slots at present. Filed under seven-day figures: an average of 1 players and a peak of 4. The busiest point in the last 48 hours was 16:00 UTC, averaging 1 players.

Server details

What version does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] use?

Rust network protocol 2635 and build 168909, on Linux, is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs. To join you need the same protocol; Steam handles the update.

How reliable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it online now?

The server is live at this moment: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. The uptime it reports puts the last restart at about 2 days 12 hours ago. It was up 167 of 168 hours across the last 7 full days, or 99% of the time. The earliest sighting at Rust Server Index is 13 September 2026.

Is the performance on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] good?

Server fps held at 58 on average across the last 48 hours, never dropping below 23. The entity count reached 92,864, covering buildings, deployables and all else in the world. Up to 3,529 MB of memory was in use. Lag, to players, is low fps and an entity count that climbs.

Where in the world 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 position is made by Rust Server Index; it shows where the server says it is. You will reach it at 85.233.150.44:35020.

How to join

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

If you would rather use the console, press F1 in Rust and enter client.connect 85.233.150.44:35020. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you. You will find its website at http://cloudrust.ru/.

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, as standard.
mp100
Max players Player cap: 100.
ts8
Group limit Game default applies: teams of up to 8.
v2635
Protocol The protocol is 2635; older or newer clients cannot join.
cs168909
Build Build on file: 168909.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code A region code is absent.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded Plugins or changed settings put this 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.