Online 85.233.150.44:35025 checked 7m ago
Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]
Connect
srv = rust.server("85.233.150.44:35027")
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 31% 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, 11:50 UTC12d ago | 3 | NaN | running | 0 |
| 1 | Fri 2 Oct, 12:58 UTC26d ago | 1 | halved by day 2 | 14 days | 0 |
| 2 | Sat 19 Sep, 11:22 UTC39d ago | 3 | halved by day 9 | 13.1 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 1595316433![Map of Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]](https://files.facepunch.com/rust/map-images/93b995ddaf67148236217d5b205adc8e4badf5edcbc8c89d77827a0cc562dba0/proceduralmap.3700.1792151410557.289_93b995ddaf67148236217d5b205adc8e.jpg)
- map
- Procedural Map
- size
- 3700
- seed
- 1595316433
Server
srv.info()- address
- 85.233.150.44:35025
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 11:50 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 | Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 804 on average | 270/350 |
| 1 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 599 on average | 128/150 |
| 2 | Atlas - US 2X Monthly | Vanilla+ | No BP Wipes | NA · groups of 16+ · 2x · monthly · 370 on average | 146/200 |
| 3 | EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 349 on average | 43/150 |
| 4 | Magic Rust #18 — Vanilla 2x | Baйп 28.10 | EU · groups of 150+ · 2x · weekly · 329 on average | 392/430 |
| 5 | MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 | EU · groups of 300+ · 2x · weekly · 313 on average | 43/1000 |
Quick answers
From the figures on this page.
Player counts
How does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] compare in the rankings?
Rank #6,937 on seven-day player hours for Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10], within the top 31% of all ranked servers.
How full does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] run?
Current row: 0 players on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10], against 100 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 00:00 UTC is the busiest, at 1 players.
About the server
How well does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] perform?
Server fps over the last 48 hours averages 60; the floor is 52. The entity count peaked at 83,319, covering buildings, deployables and the rest of the world. The memory field tops out at 3,683 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10], and is it online now?
Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] reports itself online at the current refresh. The uptime it reports puts the last restart about 2 days ago. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] hosted?
For Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10], no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 85.233.150.44:35025.
Settings and map
Which rules apply on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10], and what settings?
2x gather is what the name states, and the name is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] selected?
The game generates the map on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]: procedural, size 3,700, seed 1595316433. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] wipe, and how often?
Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] wipes on no fixed rhythm, so there is nothing to predict. 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 15 hours ago.
What is wipe day on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] like?
Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 47 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 5.5.
Tags and filters
Where does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] appear among Rust Data lists and filters?
The Rust Data lists that Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] fits are: Modded Rust servers and 2x Rust servers. These filters bring it up 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: 2x.
How should you read the server tags on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?
These tags are published by Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 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): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?
In Rust, F1 opens the console: type client.connect 85.233.150.44:35025. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at http://cloudrust.ru/.