Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO F SRV11,829online PAX89,289playing OCC4,008with players WIPED 3H74
MODModded traffic
Callsign

CLD3368=

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]

Online EU 85.233.150.44:35015 checked 1h ago

10x biweekly wipes moddedoxide
Clearance · join
Launch Rust and join
Players now 2/ 100 2% full
7-day average1peak 6
Rank#3,368top 15% · #1259 in EU
Last wipe5d agobiweekly schedule
Next wipe1d 20hFri 30 Oct, 15:34 UTC
Track history

Players

AveragePeak
0246819:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

02040608019:0004:0013: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 15% of all ranked servers, top 43% in EU. Ranked on player hours over the last seven days.

Flight plan

Wipe schedule

a steady gap
ETD · next wipe

Next wipe Friday 30 October, 15:34 UTC, in 1d 20h.

Every 7 days 4 hours · medium confidence

usual gap7.3 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak3players, last three wipes
crowd held60%else halves by day 5.5

Coming wipes

  1. 1d 20hFri 30 Oct, 15:34 UTC
  2. 8d 0hThu 5 Nov, 19:00 UTCFW
  3. 9d 0hFri 6 Nov, 19:21 UTC
  4. 16d 4hFri 13 Nov, 23:08 UTC
  5. 23d 8hSat 21 Nov, 02:54 UTC
  6. 30d 11hSat 28 Nov, 06:41 UTC
  7. 36d 0hThu 3 Dec, 19:00 UTCFW
  8. 37d 15hSat 5 Dec, 10:28 UTC

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctThu 8 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 11:47 UTC5d ago 3 – running 0
Fri 16 Oct, 08:01 UTC12d ago 3 halved by day 6 7.2 days 0
Thu 8 Oct, 16:08 UTC20d ago 4 held half 7.7 days 0
Fri 2 Oct, 12:57 UTC26d ago 5 halved by day 5 6.1 days 0
Fri 25 Sep, 03:34 UTC33d ago 4 held half 7.4 days 0
Thu 17 Sep, 19:34 UTC40d ago 2 held half 7.3 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 traffic

Similar servers

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

  1. 01MOD
    Callsign HLL010EU · groups of 8+ · 10x · biweekly · 77 on average HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop]
    Players 140/150
  2. 02MOD
    Callsign PRS310EU · groups of 100+ · 10x · biweekly · 9 on average PROSTOJ CLASSIC #5 [X10|SKINS]
    Players 18/100
  3. 03MOD
    Callsign WLD026EU · groups of 8+ · 10x · biweekly · 3 on average [EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTS
    Players 2/50
  4. 04MOD
    Callsign TRB017EU · groups of 20+ · 10x · biweekly · 2 on average Turbo Rust 10x | PvP | MyMini | SkinBox | x10
    Players 4/10
  5. 05MOD
    Callsign ATL015EU · groups of 20+ · 10x · weekly · 340 on average Atlas - EU 10x | No BPs | Kits | Shop
    Players 577/650
  6. 06MOD
    Callsign KRK031EU · groups of 14+ · 10x · weekly · 151 on average KRAKEN | X10 | EU | KITS | RP | FPS+
    Players 185/400
ATIS · this server

Quick answers

From the figures on this page.

Tags

Which Rust Tracker filters and lists carry Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

10x Rust servers, tracked, EU Rust servers, tracked live and Modded servers, tracked live — the Rust Tracker lists that include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. It comes up under these filters on the server list: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week; Gather rate: 10x.

How should you read the tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

These tags are published by Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp100 (Max players): Capacity: 100 slots; ts8 (Group limit): Default team size: 8; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Plugin framework confirmed: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; listed under Modded; EU (Europe): The server browser lists it under Europe. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Times

What happens on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on wipe day?

Recent wipes averaged a peak of 3 players. The peak on the latest wipe came 6 hours after it. The crowd stayed above half the peak until the next wipe in 60% of recent wipes. In the other cases, half the peak was lost by day 5.5.

On what schedule does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] wipe?

The recent gap between wipes at Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is about 7.3 days. Friday 30 October at 15:34 UTC is when the next wipe falls due. Its world went live 5 days 7 hours. A two-weekly wipe schedule is published in its tags.

Server Details

How reliable is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], and is it online now?

Right now Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is online. By its own uptime figure, the last restart was roughly 39 hours ago. 100% uptime over the last 7 full days, with 168 of 168 hours up. Rust Tracker logged it first on 13 September 2026.

Which Rust build is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] running?

Rust network protocol 2635 and build 168909 on Linux is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs. To join, your game must be on the same protocol; Steam handles the update.

What is performance like on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

Average server fps over the last 48 hours: 57, with a low of 22. Buildings, deployables and the rest of the world took it to a maximum of 88,778 entities. Peak memory use: 3,563 MB. Lag, as players experience it, comes from low fps and a rising entity count.

Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] sit?

In Europe, under its EU tag, is where Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 85.233.150.44:35015.

Population

Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] busy?

Tracking Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 2 of 100 slots filled. Peak of 6 in the last seven days, average 1 players. Busiest window in 48 hours: 19:00 UTC, 4 players on average.

What rank does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] carry among Rust servers?

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] places #3,368 on seven-day player hours, #1,259 in Europe and in the top 15% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

The name says it: Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs 10x gather. Up to 8 players per group, the game's default. It runs survival, gather, build, raid, as the game intends. Players can raid and fight each other here. Plugins or settings change the game, and the server browser lists it under Modded. The plugin count stands at Oxide. On: VAC, Valve's anti-cheat.

Which map is confirmed for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

The map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is procedural, size 3,700, seed 262731628, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map.

How to Join

How do you get onto Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

Open the console in Rust with F1 after starting the game, then type client.connect 85.233.150.44:35015. Alternatively, Launch Rust here opens Rust via Steam and connects you.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, standard mode.
mp100
Max players Capacity: 100 slots.
ts8
Group limit Default team size: 8.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Mods and access

^o
Oxide Plugin framework confirmed: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; listed under Modded.

Region

EU
Europe The server browser lists it under Europe.

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.