Station EU-16413 · no signal
Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]
Offline EU 95.85.249.130:35010 checked 27d 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
- 7d 19h
- 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 19h. The force wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 pageRules and settings
Which map is running on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]?
A procedural map runs on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09], generated by the game.
Which settings and rules apply on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]?
Its name points to a gather rate of 10x on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] right now?
A reading taken now finds Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] offline; the most recent activity was 27 days 8 hours ago.
How does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] rank against other Rust servers?
Cloud #1 [x10|Procedural|LOOT+|KIT|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.
Operator and location
How reliably does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] stay online?
As recorded now, Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] is not reachable, the last contact having been 27 days 8 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 1 October 2026 is when Rust Server Trends first recorded it.
Where in the world is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] hosted?
With its EU tag, Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] lists itself in Europe. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 95.85.249.130:35010.
Which Rust version is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] running?
Rust network protocol 2633 and build 165217 on Linux is what Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
How often does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] wipe, and on which days?
An estimate from the force wipe gives Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]'s next wipe. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 33 days 20 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.
Lists and tags
What do the server tags on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] mean?
Tags published by Cloud #1 [x10|Procedural|LOOT+|KIT|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): 100 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): Game build: 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; EU (Europe): In the server browser it appears under Europe. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] appear?
These Rust Server Trends lists include Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]: 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; Gather rate: 10x.
Join the server
What steps get you onto Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]?
Enter client.connect 95.85.249.130:35010 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects 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.