Station XX-3972 · recording
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Online 85.233.150.44:35020 checked 1h ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 4
- Rank
- #3,972
- top 18%
- Last wipe
- 12d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +1into Tue 02:00 UTC
- Peak · 48 h
- 3most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 18% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 14.3 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 3players, last three wipes
- crowd held
- 0%else halves by day 5
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 16 Oct, 08:02 UTC12d ago | M0.5▲rising | 3 | – | running | 0 | |
| Fri 2 Oct, 12:59 UTC26d ago | M0.5▲rising | 3 | halved by day 5 | 13.8 days | 0 | |
| Thu 17 Sep, 19:34 UTC40d ago | M0.6▲rising | 4 | halved by day 5 | 14.7 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs a procedural map of size 3,700 with seed 81405896, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
5x gather is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs, judging by its name. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] right now?
0 of the 100 slots on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] are filled right now. Across seven days this server recorded an average of 1 players and a peak of 4. Averaged over the last 48 hours, the busiest hour was 13:00 UTC at 2 players.
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] rank against other Rust servers?
Over the last seven days, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] recorded enough player hours to reach #3,972 worldwide, placing it in the top 18% of all ranked servers.
Server facts
How reliably does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] stay online?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is up at the moment. The uptime it reports puts its last restart about 39 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.
Does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] hold a steady tick rate?
Across the last 48 hours it averaged 56 server fps, with a floor of 18. The world held up to 92,864 entities at its peak, buildings and deployables included. It reached a ceiling of 3,263 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.
Which region 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]. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 85.233.150.44:35020.
Which Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] running?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
The recent wipes averaged a busiest count of 3 players. 47 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 5 it fell below half in the wipes where it didn't hold.
On what timetable does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] run its wipes?
No next wipe can be predicted for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 12 days 10 hours is how long the current world has been running.
Lists and tags
What do the server tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] mean?
These are the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): The server has 100 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] appear?
These Rust Server Trends lists include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: 5x Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 5x.
Connecting
How do you connect to Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
To join, enter client.connect 85.233.150.44:35020 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. http://cloudrust.ru/ is where its website lives.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.