Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]
Offline 95.85.249.130:35020 checked 28d ago
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players 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.
Quick answers
From the figures on this page.
Map and rules
On Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09], which rules and settings apply?
Filed under gather rates: 5x, as the name of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] states. 8 players per group is the default limit. The server runs survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. The server browser lists it under Modded; plugins or settings alter the game. Filed under plugins: Oxide. VAC is on: Valve's anti-cheat is enabled.
What is the map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
A procedural map, generated by the game, is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] runs.
Tags and filters
On Rust Server Index, which lists and filters carry Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
The Rust Server Index lists that include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] are 5x Rust servers, filed by gather rate and Modded Rust servers, filed by play style. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 5x.
How should you read the tags listed for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
The server's own tags are listed here, and the game's server browser reads them: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] gives gmrust (Game mode): Rust survival, as standard; mp100 (Max players): The queue ceiling sits at 100; ts8 (Group limit): Game default applies: teams of up to 8; v2633 (Protocol): Your client must run protocol 2633 to connect; cs165217 (Build): It runs build 165217; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): No region code has been set; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): This one is Modded, since plugins or settings change how it plays. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipe dates
Which wipe timetable does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] follow?
The record holds too few of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]'s wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. Its present world dates from 41 days 22 hours.
Player counts
How is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] ranked compared with the rest?
The seven-day player-hours ranking places Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] at #16,413, among the top 69% of ranked servers.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] quiet or crowded?
The last check found Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] offline, last seen 28 days 2 hours ago.
Operator and status
Which Rust build is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] running?
Rust network protocol 2633 and build 165217, on Linux, is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] runs. Steam keeps your game updated, but the protocol must match for you to join.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] reachable, and does it stay up?
As of now Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] is offline, with its last appearance 28 days 2 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. On 1 October 2026 it was first seen by Rust Server Index.
Which region is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] in?
No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 95.85.249.130:35020.
Connecting
What steps lead onto Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
Two ways in. Type client.connect 95.85.249.130:35020 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp100,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
mp100
ts8
v2633
cs165217
ptrak
$r?
Mods and access
^o
^z
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.