Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 10m ago · 85.233.150.44:35020
Abstract
We describe the public Rust server Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], reached at 85.233.150.44:35020. At the last check it held 0 of 100 places, against a seven-day mean of 1 and a peak of 41. It ranks #3,914 of all servers, the top 18%. It last wiped 12d ago.
Keywords5x gather modded oxide
1Summary statistics

2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 18% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: 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.
| Measure | Value | Note |
|---|---|---|
| Usual gap | 14.3 days | between real wipes |
| On rhythm | 100% | of its recent wipes |
| Wipe-day peak | 3 | players, last three wipes |
| Crowd held | 0% | else halves by day 5 |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Fri 16 Oct, 08:0212d ago | 3 | – | running | 0 |
| Fri 2 Oct, 12:5926d ago | 3 | halved by day 5 | 13.8 d | 0 |
| Thu 17 Sep, 19:3441d ago | 4 | halved by day 5 | 14.7 d | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 85.233.150.44:35020 |
|---|---|
| Region | – |
| Max players | 100 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 16 Oct 2026, 08:02 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Procedural Map |
| Size | 3700 |
| Seed | 81405896 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded 5x servers [2], modded Rust servers listed live [3] and predicted wipe schedule [4].
| Server | Players |
|---|---|
| MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10EU · groups of 1000+ · 5x · 120 on average | 70/300 |
| HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10xNA · groups of 8+ · 5x · monthly · 117 on average | 215/250 |
| [EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | KitEU · groups of 100+ · 5x · 85 on average | 101/325 |
| Классика x5 для НОВИЧКОВ |Loot+|BigBoyRust|EU · groups of 8+ · 5x · weekly · 79 on average | 17/300 |
| WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPEEU · groups of 40+ · 5x · weekly · 79 on average | 53/200 |
| AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10xNA · groups of 8+ · 5x · monthly · 74 on average | 118/150 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1How well does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run?
Over the past 48 hours, it ran at an average of 58 server fps, with a low of 23. The highest number of entities it carried was 92,864, comprising buildings, deployables and all other objects. Memory use peaked at 3,390 MB. When fps is low and entity count climbs, players feel lag.
A.2What is the location of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
There is no region published for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. Rust Statistics does not look up the machine's location; it shows where the server says it is. 85.233.150.44:35020 is its address.
A.3What is the reliability of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it online?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is currently online. It last restarted around 45 hours ago, according to its reported uptime. Of the 168 hours in the last 7 full days, 144 were served, an availability of 86%. It was first observed on 13 September 2026 by Rust Statistics.
A.4What version of Rust is run on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The version of Rust on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is network protocol 2635 and build 168909, and the operating system is Linux. To join, your game must use the same protocol; Steam handles the update for you.
Wipe schedule
A.5What schedule does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] follow for wipes?
Prediction of the next wipe is impossible for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], which wipes irregularly. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The world currently in use was created 12 days 16 hours ago.
A.6What happens on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] when wipe day arrives?
Recent wipes saw an average peak of 3 players. The crowd reached its maximum 47 hours after the latest wipe. For 0% of recent wipes, the population did not fall below half the peak before the next wipe. Otherwise, a fall below half took place by day 5.
Population
A.7How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] compare with other Rust servers in the rankings?
Ranked by player hours across seven days, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] holds #3,914, in the top 18% of all ranked servers.
A.8At what level does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] operate in terms of players?
On Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], 0 of the 100 slots are occupied at present. The peak over seven days is 4, against an average of 1. The busiest hour of the last 48 is 13:00 UTC, averaging 2 players.
Tags, lists
A.9What is the meaning of the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Tags from Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], read by the game's server browser, are gmrust (Game mode): Rust survival, in its standard form; mp100 (Max players): 100 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.
A.10Where can Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] be found among the Rust Statistics lists and filters?
5x Rust servers: live statistics and Modded Rust servers are the Rust Statistics lists that Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] fits. It appears under the following 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.
Settings and map
A.11Under what rules and settings does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] operate?
The rate for gathering on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is 5x, according to its name. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. Plugins number Oxide on this server. The server has VAC on, Valve's anti-cheat.
A.12On which map does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] take place?
Generated by the game from seed 81405896, the procedural map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] measures 3,700. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.
How to join
A.13What is the process for joining Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Press F1 inside Rust to open the console and enter client.connect 85.233.150.44:35020. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection. The website for this server is http://cloudrust.ru/.
Appendix BServer tags
What each of the server's tags means. Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Rust survival, in its standard form. |
mp100 | Max players. 100 slots are available. |
ts8 | Group limit. 8 per team, the value the game sets by default. |
v2635 | Protocol. The game protocol is 2635; your client must match it to join. |
cs168909 | Build. The game build is 168909. |
ptrak | Networking. RakNet is the network layer here, as it is by default in the game. |
$r? | Region code. No region code is set. |
| Mods and access | |
^o | Oxide. Plugins are handled by Oxide (uMod). |
^z | Modded. Modded listing: plugins or settings modify the game. |
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.
Appendix CAbout this server, in its own words
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded 5x servers. ruststatistics.org/top-5x-rust-servers.
- [3]Rust Statistics. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
- [4]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.