Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]
Online 85.233.150.44:35020 checked 13m ago
Server instruments
last reading Wed 22:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 23 · below 20 is lag, below 10 is badEntities
48 h range 89,199–92,864 · memory 2,881 MBUptime
1 days 21 hours since its last restart, at the last readingPlayers
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.
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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 08:02 UTC12d ago | 3 | – | running | 0 |
| Fri 2 Oct, 12:59 UTC26d ago | 3 | halved by day 5 | 13.8 days | 0 |
| Thu 17 Sep, 19:34 UTC41d ago | 4 | halved by day 5 | 14.7 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 72/300
- 191/200
- 114/325
- 17/300
- 64/200
- 125/150
Quick answers
from the figures on this pageWipe schedule
What happens on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] when wipe day comes?
At their busiest, its recent wipes drew 3 players on average. Peak crowd on the latest wipe: 47 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 5 it fell below half when it didn't.
What wipe timing does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] follow?
There is no next wipe to predict: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 12 days 15 hours ago.
Tag meanings
How should you read the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
These are the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
On Rust Metrics, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sits in these lists: Best 5x Rust servers: live readings and Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 5x.
Player count
What position does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] hold among Rust servers?
Ranking for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]: #3,923 on seven-day player hours, top 18% of all ranked servers.
What is the population on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
0 of 100 slots are filled on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] right now. Seven-day check: 1 players on average. Peak reading: 4. The last 48 hours peaked at 13:00 UTC, averaging 2 players at that hour.
Server details
What location is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] hosted in?
Reading: location. Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 85.233.150.44:35020.
What Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] on?
Reading: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.
How does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] perform?
Over the last 48 hours the average was 58 server fps; the floor was 23. Check: entities. The peak was 92,864, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,390 MB. Lag, as players feel it, is low fps plus a climbing entity count.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] up, and how often does it stay up?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 45 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Rules and settings
How is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] configured, and what rules are in force?
The name carries the rate: 5x gather on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Size 3,700 and seed 81405896: the game generates the procedural map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] from them. View it on RustMaps from this page: matching size and seed give an identical map.
Join
What do you do to join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Check: join. Open Rust, press F1, then enter client.connect 85.233.150.44:35020. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at http://cloudrust.ru/.