Station EU-16413 · no signal
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]
Offline EU 95.85.249.130:35015 checked 26d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,413
- top 69% · #2523 in EU
- Last wipe
- 33d ago
- biweekly schedule
- Next wipe
- 8d 6h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers, top 86% in EU. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 8d 6h. The force wipe · high confidence
Coming wipes
- 8d 6hThu 5 Nov, 19:00 UTCFW
- 8d 14hFri 6 Nov, 03:34 UTC
- 22d 14hFri 20 Nov, 03:34 UTC
- 36d 6hThu 3 Dec, 19:00 UTCFW
- 36d 14hFri 4 Dec, 03:34 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 25 Sep, 03:34 UTC33d ago | – | – | – | – | running | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] uses a procedural map, which the game generates.
Which settings and rules apply on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Going by its name, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] runs 10x gather. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
A reading taken now finds Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] offline; the most recent activity was 26 days 21 hours ago.
How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] rank against other Rust servers?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] is #2,523 in Europe and #16,413 worldwide on the past week's player hours, within the top 69% of ranked servers.
Server details
How reliably does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] stay online?
As recorded now, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] is not reachable, the last contact having been 26 days 21 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 23 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] hosted?
The EU tag is how Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] 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 95.85.249.130:35015.
What build of Rust does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] use?
Rust network protocol 2633 and build 165217 on Linux is what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
How often does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] wipe, and on which days?
The prediction follows its tag, because too few of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]'s wipes are on record to confirm its schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 33 days 9 hours is how long the current world has been running. Its tags state that it wipes every two weeks.
Lists and tags
What do the server tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] mean?
Tags published by Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): Slots: 100; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): It runs game build 165217; 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): A wipe comes every second week; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EU (Europe): The server browser files it under Europe. 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 25.09] appear?
The Rust Server Trends lists that take in Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] are: 10x Rust servers, EU Rust servers and Modded Rust servers, tracked live. These filters bring it up 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; Gather rate: 10x.
Connecting
What steps get you onto Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
To join, enter client.connect 95.85.249.130:35015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
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.