Statistical profileOnline
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
EU 85.233.150.44:35015 checked 12m ago
Connect to this server
1. Main points
Players now
0/ 100
0% full
7-day average
1
peak 6
Rank
#3,488
top 16% · #1304 in EU
Last wipe
4d ago
biweekly schedule
Next wipe
2d 4h
Fri 30 Oct, 15:34 UTC
Main points
- There were 0 players on it, 0% of its 100 slots.
- Over the last seven days it averaged 1 players, with a peak of 6.
- It ranks #3,488 of all ranked servers, the top 16%, and #1304 in EU, on player hours over the last seven days.
- Its current map went up 4d ago; the next wipe is expected Friday 30 October, 15:34 UTC, every 7 days 4 hours.
2. Players
Figure 1: Players on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 16% of all ranked servers, top 45% in EU. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterna steady gap
Next wipe Friday 30 October, 15:34 UTC, in 2d 4h. Every 7 days 4 hours · medium confidence
Usual gap
7.3 days
between real wipes
On rhythm
80%
of its recent wipes
Wipe-day peak
3
players, last three wipes
Crowd held
60%
else halves by day 5.5
Table 1: Coming wipes
Expected from its own rhythm and the force wipe
| In | Date and time | Kind |
|---|---|---|
| 2d 4h | Fri 30 Oct, 15:34 UTC | Own schedule |
| 8d 8h | Thu 5 Nov, 19:00 UTC | Force wipe FW |
| 9d 8h | Fri 6 Nov, 19:21 UTC | Own schedule |
| 16d 12h | Fri 13 Nov, 23:08 UTC | Own schedule |
| 23d 16h | Sat 21 Nov, 02:54 UTC | Own schedule |
| 30d 20h | Sat 28 Nov, 06:41 UTC | Own schedule |
| 36d 8h | Thu 3 Dec, 19:00 UTC | Force wipe FW |
| 37d 23h | Sat 5 Dec, 10:28 UTC | Own schedule |
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 3, 6 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 2: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 11:47 UTC4d ago | 3 | – | running | 0 |
| Fri 16 Oct, 08:01 UTC12d 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 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
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)
Table 3: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | 3700 |
| Seed | 262731628 |
8. Server characteristics
Table 4: Characteristics of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 5: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop] | EU · groups of 8+ · 10x · biweekly · 77 on average | 67 / 150 |
| PROSTOJ CLASSIC #5 [X10|SKINS] | EU · groups of 100+ · 10x · biweekly · 10 on average | 12 / 100 |
| [EU] Wild Sanctuary • PvE X10 • XP/SHOP/EVENTS | EU · groups of 8+ · 10x · biweekly · 3 on average | 2 / 50 |
| Turbo Rust 10x | PvP | MyMini | SkinBox | x10 | EU · groups of 20+ · 10x · biweekly · 2 on average | 2 / 10 |
| Atlas - EU 10x | No BPs | Kits | Shop | EU · groups of 20+ · 10x · weekly · 341 on average | 336 / 350 |
| KRAKEN | X10 | EU | KITS | RP | FPS+ | EU · groups of 14+ · 10x · weekly · 149 on average | 145 / 400 |
10. Quick answers
From the figures on this page.
Wipe details
This release records the wipe timetable for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: what is it?
Recent wipes of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] have fallen at intervals of about 7.3 days. Friday 30 October at 15:34 UTC is the date of its next wipe. This world was generated 4 days 22 hours ago. The tags list a fortnightly wipe schedule.
On Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], what happens on wipe day?
Recent wipes drew an average peak of 3 players. 6 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 60% of recent wipes. The fall below half came by day 5.5 in those cases where it did not hold.
Server details
Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] up, and how well has it held up?
At the latest check, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] was online. By its own reported uptime, it restarted about 32 hours ago. Of the 168 hours in the last 7 full days, it was up 168 of them, or 100%. First recorded by Rust Census on 13 September 2026.
What does the performance record of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] show?
Over the last 48 hours, server fps averaged 58; the lowest reading was 33. The world carried up to 88,778 entities, including buildings, deployables and all else. Memory use reached 3,365 MB at its peak. Players feel low fps and a rising entity count as lag.
In which location is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] based?
Its EU tag is how Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] lists itself in Europe. Rust Census does not look up where the machine stands; it shows where a server says it is. 85.233.150.44:35015 is its address.
Which Rust version is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] running?
This release lists Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on Rust network protocol 2635 and build 168909, running on Linux. The same protocol is required for your game to join, and Steam updates it for you.
Population
How many players does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] carry?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] stands at 0 players from 100 slots in this release. This release records a seven-day average of 1 players and a peak of 6. An average of 4 players was recorded at 19:00 UTC, the busiest hour of the last 48.
How does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] compare with other servers in the rankings?
On player hours over the last seven days Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] stands at #3,488, #1,304 in Europe, in the top 16% of ranked servers.
Lists and tags
On Rust Census, which lists and filters carry Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
The Rust Census lists that Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] fits are: 10x Rust servers, counted, EU Rust servers: the regional count and Modded Rust servers, counted. Under these filters it comes 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.
What is meant by each tag shown on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
These are the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] publishes for the game's server browser to read: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp100 (Max players): 100 slots are available; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): A region code has not been set; ^b (Biweekly): A wipe is run once a fortnight; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): Modded: the game is changed by plugins or settings; EU (Europe): Europe is the region under which the browser lists it. At the top of this page you will find the tags for current players, queue and world creation time.
Rules, map
Which map has been recorded for Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Size 3,700 and seed 262731628: that is the procedural map on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], generated by the game. Size and seed together fix the map, so you can view it on RustMaps from this page.
On Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], what rules and settings are in force?
The name of Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] records a gather rate of 10x. The default applies: groups are capped at 8 players. survival is the game mode recorded, the standard game: gather, build, raid. Combat between players and raiding are both permitted. The server browser lists it under Modded: plugins or settings alter the game. Plugins on it number Oxide. Anti-cheat is active: VAC, Valve's system, is on.
Connecting
What steps are needed to join Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Enter client.connect 85.233.150.44:35015 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp100,ptrak,$r?,v2635,^b,EU,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp100 | Max players 100 slots are available. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs168909 | Build Game build: 168909. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code A region code has not been set. |
Wipe schedule
^b | Biweekly A wipe is run once a fortnight. |
|---|
Mods and access
^o | Oxide Plugins are handled by Oxide (uMod) on this server. |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
Region
EU | Europe Europe is the region under which the browser lists it. |
|---|
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.