This server publishes no banner
Exhibit no. 16,413Acc. 2026.16413
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]
Rust server · in the archive since 1 October 2026
Offline 95.85.249.130:35020 checked 28d ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
The record of each wipe
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.
The rhythm
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
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.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Tags and filters
What do the server tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] mean?
You can see the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] publishes, read by the game's server browser: gmrust (Game mode): This server runs standard Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default caps teams at 8; v2633 (Protocol): To join, your game has to be on protocol 2633; cs165217 (Build): This server runs game build 165217; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. Shown at the top of this page are the current players, the queue and the world's age, also taken from the tags.
Which Rust Server History lists and filters include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
The Rust Server History lists that feature Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] are: 5x Rust servers and Modded Rust servers: the record. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 5x.
The record
Which version of Rust does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] run?
The recorded build for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] is Rust network protocol 2633 and build 165217 on Linux. Joining requires your game to be on the same protocol; Steam keeps it updated for you.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] online, and how reliable is it?
Offline now, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] was last seen 28 days 8 hours ago. 0 of 168 hours, or 0% of the time, over the last 7 full days. The first sighting by Rust Server History was on 1 October 2026.
Where is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] located?
No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. Rust Server History does not look up where the machine stands; it shows where a server says it is. Its entry gives 95.85.249.130:35020 as the address.
Wipe history
What is the wipe schedule on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
Its rhythm is not yet clear: too few of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]'s wipes are on record. Next on Thursday 5 November at 19:00 UTC is the monthly force wipe, when every Rust server wipes. 42 days 4 hours ago its current world was made.
Player counts
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] rank against other Rust servers?
Player hours over the last seven days put Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] at #16,413: a place in the top 69% of all ranked servers.
How busy is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
The last sighting of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] in the live count was 28 days 8 hours ago; it is offline now.
Rules and settings
What are the rules and settings on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
The name states a 5x gather rate for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. No group may exceed 8 players, the default set by the game. Recorded as survival, with this note: gathering, building and raiding: the standard game. You may fight and raid other players. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins are running. The anti-cheat VAC from Valve is active.
Which map does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] run?
A procedural map is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] runs; the game generates it.
Join record
How do I join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
Entering client.connect 95.85.249.130:35020 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf.
The label explained
Server tags
What each tag this server publishes 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.