An entry in the registerNo. 3,511
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Online EU 85.233.150.44:35015 checked 8m ago
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is a Rust server in Europe. At the last count it had 0 players of a possible 100; over the past week it averaged 1, with a peak of 6. It stands at No. 3,511 of the ranked servers, the top 16%, and No. 1313 in Europe. It last wiped 4d ago, on a biweekly schedule, and the next wipe is expected on Friday 30 October. Its own tags class it as 10x, modded, oxide.
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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.
§ 3Standingthe rank, daily · 1 is best
Top 16% of all ranked servers, top 45% in EU. Ranked on player hours over the last seven days.
§ 4The wipe schedulea steady gap
Next wipe Friday 30 October, 15:34 UTC, in 2d 11h. Every 7 days 4 hours · medium confidence
between real wipes
of its recent wipes
players, last three wipes
else halves by day 5.5
| Date, UTC | Hence |
|---|---|
| Fri 30 Oct, 15:34 | 2d 11h |
| Thu 5 Nov, 19:00 FW | 8d 15h |
| Fri 6 Nov, 19:21 | 9d 15h |
| Fri 13 Nov, 23:08 | 16d 19h |
| Sat 21 Nov, 02:54 | 23d 23h |
| Sat 28 Nov, 06:41 | 31d 2h |
| Thu 3 Dec, 19:00 FW | 36d 15h |
| Sat 5 Dec, 10:28 | 38d 6h |
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.
§ 5The record of wipesnewest first
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 11:47 UTC4d ago | 3 | – | running | 0 |
| Fri 16 Oct, 08:01 UTC11d ago | 3 | halved by day 6 | 7.2 days | 0 |
| Thu 8 Oct, 16:08 UTC19d ago | 4 | held half | 7.7 days | 0 |
| Fri 2 Oct, 12:57 UTC25d ago | 5 | halved by day 5 | 6.1 days | 0 |
| Fri 25 Sep, 03:34 UTC33d ago | 4 | held half | 7.4 days | 0 |
| Thu 17 Sep, 19:34 UTC40d 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.
§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes
- 1 HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop]22/150 EU · groups of 8+ · 10x · biweekly · 77 on average
- 2 PROSTOJ CLASSIC #5 [X10|SKINS]2/100 EU · groups of 100+ · 10x · biweekly · 10 on average
- 3 [EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTS1/50 EU · groups of 8+ · 10x · biweekly · 3 on average
- 4 Turbo Rust 10x | PvP | MyMini | SkinBox | x100/200 EU · groups of 20+ · 10x · biweekly · 2 on average
- 5 Atlas - EU 10x | No BPs | Kits | Shop72/100 EU · groups of 20+ · 10x · weekly · 341 on average
- 6 KRAKEN | X10 | EU | KITS | RP | FPS+15/400 EU · groups of 14+ · 10x · weekly · 149 on average
§ 7Questions answeredfrom the figures in this entry
Server details
The Rust version for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: which one?
The server Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must be on the same protocol; Steam handles the update.
What does uptime look like on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], and is it up?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] currently answers as online. Of note: the reported uptime places the last restart about 25 hours ago. Of note: 168 of 168 hours up in the last 7 full days, or 100% of the time. The first sighting at Rust Server Stats was on 13 September 2026.
Does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hold a steady frame?
The records show an average of 58 server fps over 48 hours, never below 33. The entity count reached 88,778: buildings, deployables and all else in the world. The memory peak was 3,222 MB. Lag, as players meet it, comes from low fps and an entity count on the rise.
What is the location of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Under the EU tag, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself in Europe. Rust Server Stats records the stated location of a server, not the location of the machine. At 85.233.150.44:35015 stands the address.
Settings and map
What map does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] put players on?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs a procedural map, generated by the game, of size 3,700 with seed 262731628. Because size and seed fix the map, it can be viewed on RustMaps from here.
The rules and settings of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: what are they?
A rate of 10x for gathering is what the name of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] states. Eight players per group is the default and the limit here. survival is the game mode, gather, build and raid: the standard game. Raiding and fighting other players are allowed. It sits in the Modded section, with plugins or settings that change play. Plugins run here: Oxide. The VAC anti-cheat from Valve is active.
Player record
How full does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] get?
0 players are on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] at present; the slot count is 100. Averaged across seven days, 1 players; the peak reached 6. At 19:00 UTC, over the last 48 hours, the mean was 4 players, the highest of any hour.
Against other Rust servers, how is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] ranked?
Ranked on seven-day player hours, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] holds #3,511, with #1,313 in Europe; the top 16% of ranked servers includes it.
The tags and lists
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] sits in which Rust Server Stats lists and filters?
These are the Rust Server Stats lists that include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 10x Rust servers, EU Rust servers: the records and Modded Rust servers. On the server list it comes up under these filters: 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.
How should the tags on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] be read?
gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default applies: 8 per team; v2635 (Protocol): Protocol 2635: joining needs the same game version; cs168909 (Build): The build number is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code is not set; ^b (Biweekly): The cycle is fortnightly; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded: settings or plugins have changed the game; EU (Europe): In the browser it appears under Europe — that is the set of tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] publishes for the game's browser. The tags include current players, queue and the time the world was made; the top of this page shows them.
The wipes
What happens on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] when wipe day arrives?
Across its recent wipes, the busiest point averaged 3 players. 6 hours into the latest wipe the crowd reached its peak. Above half that peak until the next wipe: the crowd held in 60% of recent wipes. In those cases the crowd dropped below half by day 5.5.
The wipe timetable for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: what does it show?
Lately a wipe has fallen about every 7.3 days on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]. On Friday 30 October at 15:34 UTC the next wipe is due. The present world dates from 4 days 16 hours. Its tags set out a fortnightly wipe schedule.
Connection
How does one connect to Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
To connect, open the console with F1 in Rust and enter client.connect 85.233.150.44:35015. The Launch Rust and join button on this page does the same through Steam.