Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]
Offline 95.85.249.130:35020 checked 27d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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. 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
newest first| 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- 205/250
- 132/150
- 214/300
- 99/200
- 36/150
- 134/150
Quick answers
from the figures on this pageWipe timing
How often does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] wipe, and when?
Its rhythm cannot be told from the wipes of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 41 days 19 hours ago.
Lists and filters
How should you read the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
Tags published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09], read by the game's server browser: 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): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
On Rust Metrics, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] sits in these lists: Best 5x Rust servers: live readings and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 5x.
Occupancy
What position does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] hold among Rust servers?
Ranking for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]: #16,413 on seven-day player hours, top 69% of all ranked servers.
What player count does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] carry?
Status for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]: offline. Last seen 27 days 23 hours ago.
Server details
Which location does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] run from?
No region comes from Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 95.85.249.130:35020.
What Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] on?
Version check: Rust network protocol 2633 and build 165217 on Linux, run by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09], and is it online?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] reports offline. The last reading came 27 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 1 October 2026.
Rules and settings
What settings and rules apply on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
Gather rate check: 5x. That comes from the name Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] on?
Procedural map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09], made by the game's generator.
Connection
How can you get onto Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
Check: join. Open Rust, press F1, then enter client.connect 95.85.249.130:35020. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.