LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 3, 47 hours in.
The current map
Friday 16 October 2026, 08:02 UTC
Wipe
Friday 2 October 2026, 12:59 UTC
Wipe
Thursday 17 September 2026, 19:34 UTC
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.
The average peak across its recent wipes is 3 players. Peak population on the latest wipe came 47 hours after it. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. In the other cases it dropped under half by day 5.
Wipes on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] come at irregular times, and no next date can be given. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The world you are playing on was built 12 days 22 hours.
On Rust Live Stats, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is listed under 5x Rust servers, live now and Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 5x it appears on the server list.
The server browser reads gmrust (Game mode): Survival here follows standard Rust; mp100 (Max players): 100 slots are available; ts8 (Group limit): Team cap: 8, which is the game default; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Plugins or settings changes put this under Modded, which Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
0 of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]'s 100 slots are filled right now. The seven-day average is 1 players, with a peak of 4. Between now and 48 hours back, 13:00 UTC drew the most players, 2 on average.
On player hours for the past seven days, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sits at #3,908, inside the top 18% of ranked servers.
Gather rates on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] are 5x, as its name states. No custom limit is set, so groups hold the default 8 players. survival applies here, the standard game: gather, build, raid. You can raid and fight other players. The server browser files it under Modded: plugins or settings alter the game. The plugin load is Oxide. Anti-cheat: VAC from Valve is enabled.
Size 3,700, seed 81405896: that is the procedural map the game generates for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. RustMaps shows it from this page, since equal size and seed give an equal map.
No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 85.233.150.44:35020 is its address.
The average server fps was 58 over the last 48 hours; the lowest was 23. Buildings, deployables and everything else in the world added up to a maximum of 92,864 entities. Memory use peaked at 3,441 MB. Lag, as players feel it, comes from low fps and a rising entity count.
The setup on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is Rust network protocol 2635 and build 168909 with Linux. Joining requires the same protocol on your game; Steam takes care of updating it.
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is up and running at this moment. Based on the uptime it reports, the last restart was about 2 days 4 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. The first sighting by Rust Live Stats was on 13 September 2026.
Enter client.connect 85.233.150.44:35020 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you. The server's website: http://cloudrust.ru/.
