Rust Server TrendsSeismic network · station log
Recording Stations11,789 Players63,543 Active3,532 Wipes · 3 h121 48 h

Station EU-3288 · recording

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

Online EU 85.233.150.44:35015 checked 14m ago

10x biweekly wipes moddedoxide
Connect
Players now
3/ 100
3% full
Motion · 24 h
M0.0rising
+1 players on the day
7-day average
1
peak 6
Rank
#3,288
top 15% · #1224 in EU
Last wipe
5d ago
biweekly schedule
Next wipe
1d 17h
Fri 30 Oct, 15:34 UTC
Seismic record · station EU-3288 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
3of 100 slots
Motion · 24 h
M0.0rising+1 players
Sharpest hour
−2into Tue 20:00 UTC
Peak · 48 h
5most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0246823:0008:0017:0001:0010:0020:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

02040608023:0008:0017:0001:0010:0020: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.

Channel 3 · rank movement

Rank

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

Top 15% of all ranked servers, top 42% in EU. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

a steady gap

Next wipe Friday 30 October, 15:34 UTC, in 1d 17h. Every 7 days 4 hours · medium confidence

usual gap
7.3 daysbetween real wipes
on rhythm
80%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
60%else halves by day 5.5

Coming wipes

  1. 1d 17hFri 30 Oct, 15:34 UTC
  2. 7d 20hThu 5 Nov, 19:00 UTCFW
  3. 8d 21hFri 6 Nov, 19:21 UTC
  4. 16d 0hFri 13 Nov, 23:08 UTC
  5. 23d 4hSat 21 Nov, 02:54 UTC
  6. 30d 8hSat 28 Nov, 06:41 UTC
  7. 35d 20hThu 3 Dec, 19:00 UTCFW
  8. 37d 12hSat 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 23 Oct, 11:47 UTC5d ago M0.5rising 3 – running 0
Fri 16 Oct, 08:01 UTC12d ago M0.5rising 3 halved by day 6 7.2 days 0
Thu 8 Oct, 16:08 UTC20d ago M0.6rising 4 held half 7.7 days 0
Fri 2 Oct, 12:57 UTC26d ago M0.7rising 5 halved by day 5 6.1 days 0
Fri 25 Sep, 03:34 UTC33d ago M0.6rising 4 held half 7.4 days 0
Thu 17 Sep, 19:34 UTC41d ago M0.3rising 2 held half 7.3 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop] EU · groups of 8+ · 10x · biweekly · 77 on average
97/ 150
PROSTOJ CLASSIC #5 [X10|SKINS] EU · groups of 100+ · 10x · biweekly · 9 on average
0/ 100
[EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTS EU · groups of 8+ · 10x · biweekly · 3 on average
0/ 50
Turbo Rust 10x | PvP | MyMini | SkinBox | x10 EU · groups of 20+ · 10x · biweekly · 2 on average
2/ 10
Atlas - EU 10x | No BPs | Kits | Shop EU · groups of 20+ · 10x · weekly · 344 on average
345/ 400
KRAKEN | X10 | EU | KITS | RP | FPS+ EU · groups of 14+ · 10x · weekly · 152 on average
74/ 400
Readings, in words

Quick answers

from the figures on this page

Map and rules

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

Generated by the game, the map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is procedural, size 3,700 with seed 262731628. From this page you can look at it on RustMaps, since the same size and seed give the same map.

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

10x gather is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs, judging by its name. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?

At this moment, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] records 3 players across 100 slots. Averaged across the last seven days the population was 1 players, reaching a peak of 6. The last 48 hours show their highest activity at 14:00 UTC, averaging 3 players.

How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] rank against other Rust servers?

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is #1,224 in Europe and #3,288 worldwide on the past week's player hours, within the top 15% of ranked servers.

Operator and location

How reliably does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] stay online?

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is up at the moment. Going by the uptime figure it reports, it restarted about 43 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] perform under load?

Across the last 48 hours it averaged 58 server fps, with a floor of 22. The world held up to 88,778 entities at its peak, buildings and deployables included. It reached a ceiling of 3,563 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.

Which region does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run from?

In Europe Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself, with the tag EU. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 85.233.150.44:35015.

Which Rust version 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. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

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

3 players, on average, was the busiest crowd at its recent wipes. 6 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 60% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 5.5.

How often does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] wipe, and on which days?

About every 7.3 days is how often Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has wiped lately. Friday 30 October at 15:34 UTC is when its next wipe is due. It has run its current world for 5 days 10 hours. Every two weeks it wipes, according to the schedule in its tags.

Tags

What do the server tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] mean?

These are the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): Slots: 100; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^b (Biweekly): It wipes once a fortnight; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EU (Europe): Europe is the region it's listed under in the browser. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] appear?

The Rust Server Trends lists that take in Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] are: 10x Rust servers, EU Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: 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.

Join the server

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

Enter client.connect 85.233.150.44:35015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp100
Max players Slots: 100.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Mods and access

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

Region

EU
Europe Europe is the region it's listed under in the browser.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.