Rust Server TrendsSeismic network · station log
Recording Stations11,791 Players67,584 Active3,634 Wipes · 3 h129 48 h

Station EU-5002 · recording

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]

Online EU 85.233.150.44:35010 checked 8m ago

10x biweekly wipes moddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.2falling
−2 players on the day
7-day average
0
peak 3
Rank
#5,002
top 23% · #1699 in EU
Last wipe
5d ago
biweekly schedule
Next wipe
1d 17h
Fri 30 Oct, 15:32 UTC
Seismic record · station EU-5002 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 100 slots
Motion · 24 h
M0.2falling−2 players
Sharpest hour
−3into Wed 19:00 UTC
Peak · 48 h
3most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0123422:0007:0016:0001:0010:0020:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

02040608022:0007:0016: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 23% of all ranked servers, top 58% in EU. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

a steady gap

Next wipe Friday 30 October, 15:32 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
0%else halves by day 4

Coming wipes

  1. 1d 17hFri 30 Oct, 15:32 UTC
  2. 7d 21hThu 5 Nov, 19:00 UTCFW
  3. 8d 21hFri 6 Nov, 19:17 UTC
  4. 16d 1hFri 13 Nov, 23:02 UTC
  5. 23d 4hSat 21 Nov, 02:48 UTC
  6. 30d 8hSat 28 Nov, 06:33 UTC
  7. 35d 21hThu 3 Dec, 19:00 UTCFW
  8. 37d 12hSat 5 Dec, 10:18 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 2, 8 hours in.

Event catalogue

Wipes

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

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
110/ 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
3/ 10
Atlas - EU 10x | No BPs | Kits | Shop EU · groups of 20+ · 10x · weekly · 344 on average
390/ 500
KRAKEN | X10 | EU | KITS | RP | FPS+ EU · groups of 14+ · 10x · weekly · 152 on average
92/ 400
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] runs a procedural map of size 3,700 with seed 2090362659, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?

10x gather is what Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] runs, judging by its name. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?

0 of the 100 slots on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] are filled right now. The seven-day average is 0 players, with a peak of 3. Averaged over the last 48 hours, the busiest hour was 17:00 UTC at 3 players.

How does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] rank against other Rust servers?

For player hours across the last seven days, Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] takes #5,002 overall and #1,699 in Europe, inside the top 23% of all ranked servers.

Server details

How reliably does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] stay online?

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] is up at the moment. Its reported uptime points to a restart about 43 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. 13 September 2026 is when Rust Server Trends first recorded it.

Does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] hold a steady tick rate?

The 48-hour average is 58 server fps; 35 is the lowest observed. At its highest, it carried 82,608 entities: buildings, deployables and the world's other contents. Its highest memory use was 3,555 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] run from?

The EU tag is how Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] lists itself in Europe. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 85.233.150.44:35010.

What build of Rust does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] use?

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] is running Rust network protocol 2635 and build 168909 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?

3 players, on average, was the busiest crowd at its recent wipes. 8 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. It fell under half by day 4 in the wipes where it didn't hold.

On what timetable does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] run its wipes?

Lately the wipes at Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] have come about every 7.3 days. Friday 30 October at 15:32 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 #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] mean?

Tags published by Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp100 (Max players): Slots: 100; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^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. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

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

You will find Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] on the following Rust Server Trends lists: 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.

How to join

How do you connect to Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?

You can connect by pressing F1 in Rust and typing client.connect 85.233.150.44:35010 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. http://cloudrust.ru/ is where its website lives.

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 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

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.