Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]
Offline EU 95.85.249.130:35015 checked 27d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 7d 17h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 17hFW
- WPT 2Fri 6 Nov, 03:34 UTC8d 1h
- WPT 3Fri 20 Nov, 03:34 UTC22d 1h
- WPT 4Thu 3 Dec, 19:00 UTC35d 17hFW
- WPT 5Fri 4 Dec, 03:34 UTC36d 1h
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 25 Sep, 03:34 UTC33d ago | – | – | running | 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 servers
the same kind of game, then region, group limit, rate and wipes- 33/150
- 0/100
- 0/50
- 0/10
- 176/250
- 27/400
Quick answers
from the figures on this pageWipe timing
What wipe timing does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] follow?
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. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 33 days 22 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.
Tag meanings
How should you read the tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
These are the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^b (Biweekly): Two-week wipe schedule; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EU (Europe): The server browser files it under Europe. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
On Rust Metrics, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] sits in these lists: 10x Rust servers, EU Rust servers, checked and Modded Rust servers, checked 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.
Population
What position does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] hold among Rust servers?
Top 69% of all ranked servers: Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] takes #16,413 on seven-day player hours and #2,523 in Europe.
What is the population on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] is not responding; status offline, last seen 27 days 10 hours ago.
Operator and location
What location is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] hosted in?
Reading: location. The EU tag puts Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] in Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 95.85.249.130:35015.
What Rust version is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] on?
Rust network protocol 2633 and build 165217 on Linux is the build Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] runs. Check: protocol. To join, your game must match; Steam handles the update.
Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] up, and how often does it stay up?
Check: connection. Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] is offline at this moment. Last contact was 27 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 23 September 2026.
Map and rules
How is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] configured, and what rules are in force?
Gather rate check: 10x. That comes from the name Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
What map is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] on?
The game generates a procedural map for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09].
Join
How do you connect to Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?
Press F1 in Rust and enter client.connect 95.85.249.130:35015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.