Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]
Key statistics
the figures behind the quote- Players now
- 0/ 100 0% full
- Change · 24h
- ▪+0 no reading a day ago
- 7-day average
- 0 peak 3
- Rank
- #4,860 top 22%
- Rank · 7d ago
- #4,566 ▼294 places down
- Last wipe
- 11d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- 5x read from the name
- Score
- 56 player hours, last seven days
- Map
- 3700 Procedural Map · seed 1025831711
- First seen
- 13 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 2 players.
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
daily · 1 is bestTop 22% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- usual gap
- 14.7 days between real wipes
- wipe-day peak
- 4 players, last three wipes
- crowd held
- 0% else halves by day 5
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 46 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 12:59 UTC11d ago | 3 | – | running | 0 |
| Thu 17 Sep, 19:34 UTC26d ago | 4 | halved by day 5 | 14.7 days | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10xNA · groups of 8+ · 5x · monthly · 112 on average | 64/150 | ▼−6−8.5% | |
| 2 | MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 13.10EU · groups of 1000+ · 5x · 106 on average | 27/250 | ▲+15+131.4% | |
| 3 | Классика x5 для НОВИЧКОВ |Loot+|BigBoyRust|EU · groups of 8+ · 5x · weekly · 89 on average | 10/300 | ▼−13−57.1% | |
| 4 | AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10xNA · groups of 8+ · 5x · monthly · 79 on average | 123/150 | ▲+81+190.0% | |
| 5 | [EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | KitEU · groups of 100+ · 5x · 72 on average | 1/300 | ▼−12−92.2% | |
| 6 | Atlas - EU 5x | No BPs | KitsEU · groups of 20+ · 5x · weekly · 72 on average | 8/100 | ▼−4−33.3% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] carries its gather rate in its name: 5x. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are in use. VAC, Valve's anti-cheat, is enabled.
Which map is played on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
A procedural map of size 3,700 with seed 1025831711 runs on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10], created by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.
Activity
What is the rank of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
For the last seven days, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] holds rank #4,860 on player hours, in the top 22% of all ranked servers.
How full is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
0 of 100 slots on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] are filled at the moment. Average players over seven days: 0; peak: 3. The busiest hour in the last 48 hours was 09:00 UTC, with an average of 2 players.
Wipe Schedule
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] handle wipe day?
An average of 4 players marked the busiest point of its recent wipes. 46 hours after the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 0% of its recent wipes. Below half by day 5 is where the crowd fell when it did not hold.
On what cycle does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] wipe?
The record holds too few of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]'s wipes to establish its rhythm. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. This world has been running for 11 days 16 hours.
Server Details
What is the location of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
There is no region published for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 85.233.150.44:35020.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] performing well?
Server fps over the last 48 hours: 58 on average, 39 at the lowest. 94,545 entities is the maximum carried: buildings, deployables and everything else. Up to 3,272 MB of memory was used. Low fps and growing entities are the source of felt lag.
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] is on which Rust version?
The build is Rust network protocol 2634 and build 167781 on Linux, running on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]. Your game needs the same protocol to get in; Steam takes care of the update.
How reliable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] and is it currently online?
The server is live: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] is online. 2 hours ago is when it last restarted, judging by the uptime it reports. 7 full days have passed with 91% uptime, 153 of 168 hours. The earliest Rust Analytics saw it was 13 September 2026.
Tags and Rankings
How should you interpret the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp100 (Max players): Capacity: 100 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167781 (Build): Build 167781; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings, which Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10] publishes. The top of this page and the tags both show its players now, its queue and when its world was made.
On Rust Analytics, which lists and filters feature Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
The following Rust Analytics lists feature Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]: Rust servers with 5x gather rates and Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 5x.
How to Join
What steps do I take to join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 02.10]?
Type client.connect 85.233.150.44:35020 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you. For more information, go to http://cloudrust.ru/.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
mp100
ts8
v2634
cs167781
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.