The server's own banner, as it publishes it
Exhibit no. 3,888Acc. 2026.3888
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Rust server · in the archive since 13 September 2026
Online 85.233.150.44:35020 checked 6m 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.
13 Sep Now 17 Sep19:34 2 Oct12:59 16 Oct08:02
a wipe on recordthe monthly force wipeexpectednow, 29 Oct 2026, 09:10 UTCAll times UTC.
The record of each wipe
-
Fri 16 Oct 202608:02 UTC13d ago
- Peak
- 3
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Fri 2 Oct 202612:59 UTC26d ago
- Peak
- 3
- Crowd
- halved by day 5
- Lasted
- 13.8 days
- Players before
- 0
-
Thu 17 Sep 202619:34 UTC41d ago
- Peak
- 4
- Crowd
- halved by day 5
- Lasted
- 14.7 days
- Players before
- 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.
The rhythm
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 47 hours in.
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 17% 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, lists
What do the server tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] mean?
The game's server browser reads these tags published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are set on this server; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): To join, your game has to be on protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework, Oxide (uMod), is installed here; ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.
Which Rust Server History lists and filters include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The Rust Server History lists that feature Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] 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; Last wipe: In the last 2 weeks; Gather rate: 5x.
The record
Does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run smoothly?
58 server fps on average over the last 48 hours, never below 23. Buildings, deployables and everything else in the world came to as many as 92,864 entities. Memory use peaked at 3,441 MB. What players feel as lag comes from low fps and a climbing entity count.
Which version of Rust does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?
The recorded build for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is Rust network protocol 2635 and build 168909 on Linux. Steam updates your game for you; joining needs the same protocol.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] online, and how reliable is it?
At this moment Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is online. About 2 days 6 hours ago is when it last restarted, judged by the uptime it reports. 167 of 168 hours, or 99% of the time, over the last 7 full days. The first sighting by Rust Server History was on 13 September 2026.
Where is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] located?
There is no region published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. Rust Server History does not look up where the machine stands; it shows where a server says it is. You will find it at 85.233.150.44:35020.
Wipe history
What does wipe day look like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
At their busiest, its recent wipes drew an average of 3 players. On the latest wipe, 47 hours after the wipe, the crowd peaked. Above half that peak until the next wipe it stayed in 0% of its recent wipes. By day 5 the crowd fell to below half when it did not hold.
What is the wipe schedule on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
No next wipe can be predicted: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipes at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, when every Rust server wipes. Made 13 days 1 hours ago, the current world is what it runs now.
Player record
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] rank against other Rust servers?
Over seven days of player hours, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] ranks #3,888, inside the top 17% of all ranked servers.
How busy is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Against 100 slots, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] records 0 players right now. A seven-day average of 1 players is recorded, with a peak of 4. An average of 2 players at 13:00 UTC made that the busiest hour of the last 48.
Rules and settings
What are the rules and settings on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
5x gathering is what the name of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] records. At 8 players, the group limit matches the game's default. Recorded as survival, with this note: gathering, building and raiding: the standard game. PvP and raiding are enabled. Plugins or settings alter the game here, and the browser lists the server under Modded. Plugins in use: Oxide. The anti-cheat VAC from Valve is active.
Which map does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?
A procedural map of size 3,700 with seed 81405896 is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs, generated by the game. One size and seed produce one map, which RustMaps can show you from this page.
Joining the server
How do I join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Press F1 in Rust to open the console, then enter client.connect 85.233.150.44:35020 to connect. Launch Rust from this page instead and you join through Steam with the connect already made. http://cloudrust.ru/ is where its website is.
The label explained
Server tags
What each tag this server publishes means.
Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp100
ts8
v2635
cs168909
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.