Skip to the page
RUST ANALYTICS
LIVE38,465PLY11,453SRV
QUOTE 95.85.249.130:35010 Offline EU checked 12d ago

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

10x biweekly wipes moddedoxide
Players · last
0/ 100
n/a24h
0% full
Players · 24 hourshourly average, then now · dashed: 24 hours ago
No hourly readings in the last 24 hours.
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 100
0% full
Change · 24h
n/a
no reading a day ago
7-day average
0
peak –
Rank
#16,413
top 69% · #2523 in EU
Rank · 7d ago
#16,111
302 places down
Last wipe
19d ago
biweekly schedule
Next wipe
8d 19h
Fri 23 Oct, 03:33 UTC
Group limit
8
8, the default
Gather rate
10x
read from the name
Score
0
player hours, last seven days
Map
–
Procedural Map
First seen
1 Oct 2026
no hostname published

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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 best
RankRank in region
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

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

Wipe schedule

Next wipeFriday 23 October, 03:33 UTCin 8d 19h

Biweekly: 14 days after its last wipe

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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
#ServerLastChg 24hPlayers over the last 24 hours24h
1[EU] HollowServers.co 10x No BPs [Loot++|Events|MyMini|Shop]EU · groups of 8+ · 10x · biweekly · 75 on average35/150−12−25.9%
2PROSTOJ CLASSIC #5 [X10|SKINS]EU · groups of 100+ · 10x · biweekly · 12 on average4/100−2−38.5%
3[EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTSEU · groups of 8+ · 10x · biweekly · 3 on average3/50−2−36.8%
4Atlas - EU 10x | No BPs | Kits | ShopEU · groups of 20+ · 10x · weekly · 290 on average122/150−57−31.8%
5KRAKEN | X10 | EU | KITS | RP | FPS+EU · groups of 14+ · 10x · weekly · 121 on average37/350−28−42.9%
6[EU] Enardo - Small One Grid 10x - No BPs | OneGridEU · groups of 8+ · 10x · 16 on average1/100−2−70.0%

Quick answers

from the figures on this page

Map and Rules

How is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] configured in terms of rules and settings?

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] carries its gather rate in its name: 10x. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. Modded is its category in the server browser; plugins or settings modify the game. Plugin count: Oxide. VAC is active.

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

The game generates the procedural map on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09].

Activity

What position does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] hold in the server rankings?

On seven-day player hours, Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] sits at #16,413, in the top 69% across ranked servers and #2,523 in Europe.

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

Right now, Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] is offline; the last sighting was 12 days 16 hours ago.

Wipe Cycle

When does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] schedule its wipes?

From biweekly: 14 days after its last wipe, the next wipe at Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] is estimated. On Friday 23 October at 03:33 UTC the next wipe is due. Its world now is 19 days 4 hours old. A fortnightly wipe is published in its tags.

Server Overview

Where can Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] be found?

With the EU tag, Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] lists itself in Europe. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 95.85.249.130:35010.

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] runs which version of Rust?

The build is Rust network protocol 2633 and build 165217 on Linux, running on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]. Your game needs the same protocol to get in; Steam takes care of the update.

Is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] up, and how consistent is its uptime?

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] is down. The last time we saw it was 12 days 16 hours ago. The last 7 full days give 0% uptime, 0 hours on out of 168. 1 October 2026 is when Rust Analytics first saw it.

Tags and Rankings

How should you interpret the tags on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]?

These tags are published by Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp100 (Max players): Capacity: 100 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2633 (Protocol): Protocol 2633: matching game versions are required to join; cs165217 (Build): It runs build 165217; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): Region code: none set; ^b (Biweekly): One wipe every fortnight; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; EU (Europe): The browser places this server in Europe. The tags also carry its current players, queue and world creation time; this page shows them at the top.

Where does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] show up in Rust Analytics lists and filters?

On Rust Analytics, Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] matches these lists: 10x Rust servers, Rust servers: Europe and Modded Rust servers. It appears under these filters 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.

How to Join

How can I connect to Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]?

Type client.connect 95.85.249.130:35010 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,^b,EU,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode Rust's standard survival mode.
mp100
Max players Capacity: 100 slots.
ts8
Group limit 8 per team: the default setting, unchanged.
v2633
Protocol Protocol 2633: matching game versions are required to join.
cs165217
Build It runs build 165217.
ptrak
Networking RakNet, the network layer the game ships with.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly One wipe every fortnight.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) is in use.
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

Region

EU
Europe The browser places this server in Europe.

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.