Online 85.233.150.44:35020 checked 9m ago
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Connect
srv = rust.server("85.233.150.44:35022")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 18% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 08:02 UTC12d ago | 3 | NaN | running | 0 |
| 1 | Fri 2 Oct, 12:59 UTC26d ago | 3 | halved by day 5 | 13.8 days | 0 |
| 2 | Thu 17 Sep, 19:34 UTC41d 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.
display(srv.map, srv.info())Map
3700 · seed 81405896![Map of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]](https://files.facepunch.com/rust/map-images/53d21a96581935b59a817f625cd16dc130a624da9e319cf8aec29598723cde0c/proceduralmap.3700.1792137700240.289_53d21a96581935b59a817f625cd16dc1.jpg)
- map
- Procedural Map
- size
- 3700
- seed
- 81405896
Server
srv.info()- 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
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10 | EU · groups of 1000+ · 5x · 119 on average | 79/300 |
| 1 | HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10x | NA · groups of 8+ · 5x · monthly · 118 on average | 170/200 |
| 2 | [EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | Kit | EU · groups of 100+ · 5x · 84 on average | 160/325 |
| 3 | Классика x5 для НОВИЧКОВ |Loot+|BigBoyRust| | EU · groups of 8+ · 5x · weekly · 80 on average | 18/300 |
| 4 | WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPE | EU · groups of 40+ · 5x · weekly · 78 on average | 101/200 |
| 5 | AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10x | NA · groups of 8+ · 5x · monthly · 74 on average | 116/150 |
Quick answers
From the figures on this page.
Player counts
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] compare in the rankings?
Player hours over seven days put Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] at #3,931, in the top 18% of the ranked set.
What population does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] carry?
The sample now reads 1 players for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], out of 100 slots. Over the last seven days it averaged 1 players and peaked at 4. The 48-hour sample puts the busiest hour at 13:00 UTC, averaging 2 players.
Server facts
What does performance look like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Averaged over 48 hours: 57 server fps, never under 18. The entity count peaked at 92,864, covering buildings, deployables and the rest of the world. Memory peaked at 3,390 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] on?
Rust network protocol 2635 and build 168909 on Linux is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it online now?
The current sample puts Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] online. The uptime it reports puts the last restart about 44 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run from?
No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 85.233.150.44:35020.
Map and rules
Which rules apply on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and what settings?
5x gather is what the name states, and the name is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The game generates the map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: procedural, size 3,700, seed 81405896. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipe, and on what schedule?
Irregular wipe times on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 12 days 14 hours ago.
On Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], what happens on wipe day?
Across recent wipes the busiest point averaged 3 players. 47 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 5.
Tags, lists
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] appear among Rust Data lists and filters?
These Rust Data lists include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: Modded Rust servers and Rust servers filtered by gather rate: 5x. 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.
Which meanings do the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] hold?
Read by the game's server browser, the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
In Rust, F1 opens the console: type client.connect 85.233.150.44:35020. Launch Rust on this page does the same by opening the game through Steam and connecting. http://cloudrust.ru/ is the website recorded for it.