Online EU 85.233.150.44:35015 checked 9m ago
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Connect
srv = rust.server("85.233.150.44:35017")
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 14% of all ranked servers, top 41% in EU. Ranked on player hours over the last seven days.
Wipe schedule · a steady gap
srv.wipe_schedule()Next wipe Friday 30 October, 15:34 UTC, in 1d 14h. # Every 7 days 4 hours · medium confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 1d 14h | Fri 30 Oct, 15:34 UTC | wipe |
| 1 | 7d 17h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 8d 17h | Fri 6 Nov, 19:21 UTC | wipe |
| 3 | 15d 21h | Fri 13 Nov, 23:08 UTC | wipe |
| 4 | 23d 1h | Sat 21 Nov, 02:54 UTC | wipe |
| 5 | 30d 5h | Sat 28 Nov, 06:41 UTC | wipe |
| 6 | 35d 17h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 37d 8h | Sat 5 Dec, 10:28 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 6 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 11:47 UTC5d ago | 3 | NaN | running | 0 |
| 1 | Fri 16 Oct, 08:01 UTC12d ago | 3 | halved by day 6 | 7.2 days | 0 |
| 2 | Thu 8 Oct, 16:08 UTC20d ago | 4 | held half | 7.7 days | 0 |
| 3 | Fri 2 Oct, 12:57 UTC26d ago | 5 | halved by day 5 | 6.1 days | 0 |
| 4 | Fri 25 Sep, 03:34 UTC33d ago | 4 | held half | 7.4 days | 0 |
| 5 | Thu 17 Sep, 19:34 UTC41d ago | 2 | held half | 7.3 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 262731628![Map of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]](https://files.facepunch.com/rust/map-images/80e0194431bd7c786508587122830a19536ea1f8c8296afb45354f58408104b7/proceduralmap.3700.1792756046827.289_80e0194431bd7c786508587122830a19.jpg)
- map
- Procedural Map
- size
- 3700
- seed
- 262731628
Server
srv.info()- address
- 85.233.150.44:35015
- region
- EU
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 23 Oct 2026, 11:47 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop] | EU · groups of 8+ · 10x · biweekly · 77 on average | 35/150 |
| 1 | PROSTOJ CLASSIC #5 [X10|SKINS] | EU · groups of 100+ · 10x · biweekly · 9 on average | 0/100 |
| 2 | [EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTS | EU · groups of 8+ · 10x · biweekly · 3 on average | 0/50 |
| 3 | Turbo Rust 10x | PvP | MyMini | SkinBox | x10 | EU · groups of 20+ · 10x · biweekly · 2 on average | 0/10 |
| 4 | Atlas - EU 10x | No BPs | Kits | Shop | EU · groups of 20+ · 10x · weekly · 347 on average | 183/250 |
| 5 | KRAKEN | X10 | EU | KITS | RP | FPS+ | EU · groups of 14+ · 10x · weekly · 152 on average | 25/400 |
Quick answers
From the figures on this page.
Population
How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] compare in the rankings?
On seven-day player hours Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is #3,197 overall and #1,190 in Europe, inside the top 14% of all ranked servers.
What population does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] carry?
Current row: 2 players on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], against 100 slots. Over the last seven days it averaged 1 players and peaked at 6. Averaged by hour over 48 hours, 14:00 UTC is the busiest, at 3 players.
About the server
How well does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] perform?
The 48-hour average is 57 server fps, with a low of 22. Entity numbers reached 88,778, and that includes buildings, deployables and the rest. The memory field tops out at 3,563 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. Steam updates your game for you, but the protocol must match to join.
Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] up, and what does its uptime show?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] reports itself online at the current refresh. Count back 47 hours from its reported uptime to get the last restart. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
In which location is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hosted?
In Europe, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself, using the EU tag. 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:35015.
Settings and map
Which settings and rules does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] run?
Gather sits at 10x, read from the server's own name: Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs a procedural map of size 3,700 with seed 262731628, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] wipe, and how often?
About every 7.3 days is how often Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has wiped of late. The schedule puts the next wipe on Friday 30 October at 15:34 UTC. This world was created 5 days 13 hours ago. The tags list a two-weekly wipe cycle.
On Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], what happens on wipe day?
Across recent wipes the busiest point averaged 3 players. The crowd on the latest wipe topped out 6 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 60% of the time. The drop under half arrived by day 5.5 in the other cases.
Lists and tags
Which lists on Rust Data hold Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], and which filters?
These Rust Data lists include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: EU Rust servers, Modded Rust servers and 10x Rust servers: the live sample. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week; Gather rate: 10x.
Which meanings do the tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hold?
The game's server browser reads these tags from Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; EU (Europe): The server browser files it under Europe. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
In Rust, F1 opens the console: type client.connect 85.233.150.44:35015. Launch Rust on this page does the same by opening the game through Steam and connecting.