Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO O SRV11,691online PAX35,842playing OCC2,916with players WIPED 3H97
MODModded traffic
Callsign

CLD16413

Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]

Offline EU 95.85.249.130:35015 checked 27d ago

10x biweekly wipes moddedoxide
Clearance · join
Launch Rust and join
Players now 0/ 100 0% full
7-day average0peak –
Rank#16,413top 69% · #2523 in EU
Last wipe33d agobiweekly schedule
Next wipe7d 15hThu 5 Nov, 19:00 UTC FW
Track history

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
15k10k15k20k23 Sep26 Sep29 Sep2 Oct5 Oct8 Oct

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

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h.

The force wipe · high confidence

Coming wipes

  1. 7d 15hThu 5 Nov, 19:00 UTCFW
  2. 8d 0hFri 6 Nov, 03:34 UTC
  3. 22d 0hFri 20 Nov, 03:34 UTC
  4. 35d 15hThu 3 Dec, 19:00 UTCFW
  5. 36d 0hFri 4 Dec, 03:34 UTC

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign HLL010EU · groups of 8+ · 10x · biweekly · 77 on average HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop]
    Players 30/150
  2. 02MOD
    Callsign PRS310EU · groups of 100+ · 10x · biweekly · 9 on average PROSTOJ CLASSIC #5 [X10|SKINS]
    Players 0/100
  3. 03MOD
    Callsign WLD026EU · groups of 8+ · 10x · biweekly · 3 on average [EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTS
    Players 0/50
  4. 04MOD
    Callsign TRB017EU · groups of 20+ · 10x · biweekly · 2 on average Turbo Rust 10x | PvP | MyMini | SkinBox | x10
    Players 0/10
  5. 05MOD
    Callsign ATL015EU · groups of 20+ · 10x · weekly · 348 on average Atlas - EU 10x | No BPs | Kits | Shop
    Players 116/150
  6. 06MOD
    Callsign KRK031EU · groups of 14+ · 10x · weekly · 153 on average KRAKEN | X10 | EU | KITS | RP | FPS+
    Players 15/400
ATIS · this server

Quick answers

From the figures on this page.

Tags

Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] appear in Rust Tracker lists and filters?

On Rust Tracker, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] sits in these lists: 10x Rust servers, tracked, EU Rust servers, tracked live and Modded servers, tracked live. On the server list, these filters bring it up: 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.

Which tags does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] carry, and what do they mean?

The game's server browser reads these tags from Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]: gmrust (Game mode): Rust survival, standard mode; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Teams cap at 8; this is the game default; v2633 (Protocol): To join, your game must match protocol 2633; cs165217 (Build): Build: 165217; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; listed under Modded; EU (Europe): The server browser lists it under Europe. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Times

On what schedule does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] wipe?

The prediction for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] follows its tag, as too few wipes are on record to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. 33 days 23 hours since this world was made. A two-weekly wipe schedule is published in its tags.

Location and Status

Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] up, and how does its uptime hold?

Offline now, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] was last seen 27 days 11 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. Rust Tracker logged it first on 23 September 2026.

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 what Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] runs. To join, your game must be on the same protocol; Steam handles the update.

Where does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] sit?

The EU tag places Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] in Europe, by its own listing. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 95.85.249.130:35015.

Population

How many players are on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] right now?

Offline now for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09], last seen 27 days 11 hours ago.

How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] compare in the rankings?

Seven-day player hours: #16,413 overall for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09], top 69% of ranked servers, #2,523 in Europe.

Map and Rules

Which settings and rules are confirmed on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?

The name says it: Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09] runs 10x gather. The game's default applies: groups can have up to 8 players. It runs survival, gather, build, raid, as the game intends. Players can raid and fight each other here. Plugins or settings change the game, and the server browser lists it under Modded. Plugins on it: Oxide. On: VAC, Valve's anti-cheat.

Which map is confirmed for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?

Generated by the game: the procedural map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09].

How to Join

Which steps join Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 25.09]?

To connect: start Rust, press F1, enter client.connect 95.85.249.130:35015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, standard mode.
mp100
Max players 100 slots on this server.
ts8
Group limit Teams cap at 8; this is the game default.
v2633
Protocol To join, your game must match protocol 2633.
cs165217
Build Build: 165217.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; listed under Modded.

Region

EU
Europe The server browser lists it under 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.