On the class lists: D (46), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average1peak 4
Rank#3,923top 18%
Last wipe12d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
82/ 100
B+
Holds a respectable place: #3,923 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
97/ 100
A+
Runs smoothly: 58 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 109 places this week.
A term to build on.
Strongest in performance (A+); wipes are the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
····W··
·······
····W··
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.
usual gap14.3 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 5
The first 48 hours of its last wipes
Fri 16 OctFri 2 OctThu 17 Sep
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
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sit?
You'll find no region listed by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 85.233.150.44:35020.
How reliable is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10], and is it up?
The server is up: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] is online now. According to its reported uptime, the last restart was about 45 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] smooth to play on?
The average over the last 48 hours was 58 server fps, and it never went below 23. Buildings, deployables and everything else in the world added up to as many as 92,864 entities. Memory use reached up to 3,390 MB. Players feel lag when fps drops and entities pile up.
What Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] on?
Rust network protocol 2635 and build 168909 on Linux is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipe, and how often?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 12 days 15 hours.
What happens on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] when wipe day arrives?
Recent wipes have peaked at 3 players on average. 47 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. Day 5 is when it sank below half in the wipes that did not hold.
Player numbers
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sit among Rust servers?
In the top 18% of all ranked servers, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sits at #3,923 for player hours over the last seven days.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] a busy server?
With 100 slots available, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] currently has 0 players. It peaked at 4 and averaged 1 players over the last seven days. The busiest time in the last 48 hours was 13:00 UTC, with an average of 2 players.
Tags
What is meant by the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
These Rust Server Score lists count Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] among them: 5x Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 5x.
Map and rules
Which rules does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] enforce, and what are its settings?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] sets gather at 5x, as its name suggests. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
A procedural map of size 3,700 and seed 81405896, generated by the game, is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10] runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 16.10]?
Enter client.connect 85.233.150.44:35020 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at http://cloudrust.ru/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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.
A term to build on. Strongest in performance (A+); wipes are the one to work on (F).