RUST METRICSFlight deck · live data
Data live Servers11,611 Players36,787 Populated2,913 Fresh wipes 3 h75 Scan5 min
‹ All servers95.85.249.130:35010
Offline Full Queue Fresh wipe Wipe due No query

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

Offline EU 95.85.249.130:35010 checked 27d ago

10x biweekly wipes moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#16,413top 69% · #2523 in EU
Last wipe34d agobiweekly schedule
Next wipe7d 11hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe

LOG

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

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

The estimate for Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]'s next wipe comes from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 34 days 3 hours ago the current world was made. A wipe schedule of every two weeks is published in its tags.

Tags

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

These are the tags Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EU (Europe): Its browser listing: Europe. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

Rust Metrics lists featuring Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]: 10x Rust servers, EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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.

Occupancy

What position does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] hold among Rust servers?

Player hours over the last seven days put Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] at #16,413, #2,523 in Europe, in the top 69% of all ranked servers.

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

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] is not responding; status offline, last seen 27 days 15 hours ago.

Operator and location

What location is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] hosted in?

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] gives Europe as its location, with the EU tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 95.85.249.130:35010.

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

Rust network protocol 2633 and build 165217 on Linux is the build Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09], and is it online?

Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] reports offline. The last reading came 27 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 1 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09] enforce, and what are its settings?

The name carries the rate: 10x gather on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 25.09]. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

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

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

How to join

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

Press F1 in Rust and enter client.connect 95.85.249.130:35010. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

EU
Europe Its browser listing: 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.