Skip to the page
Network live 11,829 servers online 89,289 players aboard 42 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

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

Online 85.233.150.44:35020 checked 2h ago

5x moddedoxide
Tracking number · connect
Launch Rust and join Website
Wipe progress · wiped 12d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 100 players now 0% full
17-day averagepeak 4
#3,971ranktop 18%
12d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

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

Hourly average and peak, UTC.

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.

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.

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 daysusual gapbetween real wipes
100%on rhythmof its recent wipes
3wipe-day peakplayers, last three wipes
0%crowd heldelse 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.

Wipes

every wipe as a delivery, newest first
  1. Fri 16 Oct, 08:02 UTC 09:02 UK · 12d ago
    Wipe delivered
    Peak
    3
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Fri 2 Oct, 12:59 UTC 13:59 UK · 26d ago
    Wipe delivered
    Peak
    3
    Crowd
    halved by day 5
    Lasted
    13.8 days
    Players before
    0
  3. Thu 17 Sep, 19:34 UTC 20:34 UK · 40d ago
    Wipe delivered
    Peak
    4
    Crowd
    halved by day 5
    Lasted
    14.7 days
    Players before
    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.

Similar parcels

Similar servers

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

  1. HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10xNA · groups of 8+ · 5x · monthly · 119 on average 54 / 150
  2. MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10EU · groups of 1000+ · 5x · 118 on average 234 / 300
  3. [EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | KitEU · groups of 100+ · 5x · 84 on average 257 / 300
  4. Классика x5 для НОВИЧКОВ |Loot+|BigBoyRust|EU · groups of 8+ · 5x · weekly · 81 on average 78 / 300
  5. WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPEEU · groups of 40+ · 5x · weekly · 78 on average 151 / 200
  6. AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10xNA · groups of 8+ · 5x · monthly · 73 on average 78 / 150
Help desk

Quick answers

From the figures on this page.

Population

How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] compare with other Rust servers in the rankings?

In the top 18% of all ranked servers sits Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], at #3,971 on hours played over seven days.

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

At the moment 0 players are on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], which has 100 slots. The seven-day figures show an average of 1 players and a peak of 4. The busiest hour over the last 48 hours was 13:00 UTC, averaging 2 players.

Server rules

On what map does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] take place?

Size 3,700 and seed 81405896 define the procedural map Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs, generated by the game. Size and seed match means the map matches, so you can view it on RustMaps from this page.

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

You get 5x gather on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], going by its name. Up to 8 players can join a group, the default for the game. survival is the mode, gather and build and raid: the standard game. Raiding and PvP are both on. Plugins or settings alter the game on this one, which sits under Modded in the server browser. Plugins come from Oxide. VAC, Valve's anti-cheat, is switched on.

Operator and location

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

You will find no region published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. 85.233.150.44:35020 is its address.

How smoothly does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?

The 48-hour average for server fps stands at 56, never dipping below 18. Buildings, deployables and all the rest of the world pushed its entity count as high as 92,864. 3,263 MB of memory was its top figure. What players call lag is the mix of low fps and an entity count that keeps climbing.

What is the uptime of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it online?

You can find Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] online at present. The uptime it reports puts its last restart at about 39 hours ago. It was up 168 of 168 hours over the last 7 full days, 100% of the time. It was first seen by Rust Wipe Tracker on 13 September 2026.

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

Rust network protocol 2635 and build 168909 on Linux is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs. Steam keeps your game updated; it has to be on the same protocol to join.

Wipe times

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

At their busiest, its recent wipes drew an average of 3 players. On the latest wipe, 47 hours passed before the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Where that did not hold, it dropped below half by day 5.

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

No next wipe can be predicted for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], which wipes at irregular times. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. The world it is running was made 12 days 11 hours.

Server tags

On Rust Wipe Tracker, which lists and filters is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] part of?

The Rust Wipe Tracker lists that include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] are: 5x Rust servers: wipes and live counts and Modded Rust servers. You will find it 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 server tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?

gmrust (Game mode): Survival in standard Rust; mp100 (Max players): It holds 100 slots; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code isn't set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it's listed under Modded are the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes, and the server browser takes them as read. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

How to join

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

Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 85.233.150.44:35020. Its website can be found at http://cloudrust.ru/.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp100
Max players It holds 100 slots.
ts8
Group limit 8 per team, which is the default.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code A region code isn't set.

Mods and access

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