On the class lists: F (43), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 2
Rank#5,426top 24% · #1785 in EU
Last wipe4d agobiweekly schedule
Next wipe2d 14hFri 30 Oct, 15:32 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
76/ 100
B
Holds a respectable place: #5,426 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
96/ 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
44/ 100
F
Slipped a little: down 635 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population is 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 24% of all ranked servers, top 61% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
····W··
····W··
···W···
····W··
····W··
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
a steady gap
Next wipe Friday 30 October, 15:32 UTC, in 2d 14h.
Every 7 days 4 hours · medium confidence
usual gap7.3 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 4
Coming wipes
2d 14hFri 30 Oct, 15:32 UTC
8d 17hThu 5 Nov, 19:00 UTCFW
9d 18hFri 6 Nov, 19:17 UTC
16d 21hFri 13 Nov, 23:02 UTC
24d 1hSat 21 Nov, 02:48 UTC
31d 5hSat 28 Nov, 06:33 UTC
36d 17hThu 3 Dec, 19:00 UTCFW
38d 9hSat 5 Dec, 10:18 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 8 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 11:46 UTC4d ago
2
–
running
0
Fri 16 Oct, 08:01 UTC11d ago
4
halved by day 3
7.2 days
0
Thu 8 Oct, 16:07 UTC19d ago
4
halved by day 5
7.7 days
0
Fri 2 Oct, 12:56 UTC25d ago
5
halved by day 4
6.1 days
0
Fri 25 Sep, 03:33 UTC32d ago
3
halved by day 1
7.4 days
0
Thu 17 Sep, 19:33 UTC40d ago
3
halved by day 4
7.3 days
4
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
EU · groups of 14+ · 10x · weekly · 149 on average
39 / 400
Quick answers
from the figures on this page
About the server
Which region is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] based in?
You'll see Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] listed in Europe, tagged EU. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 85.233.150.44:35010.
Is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] up, and how steady is its uptime?
The server is up: Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] is online now. About 22 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] perform well?
The average over the last 48 hours was 58 server fps, and it never went below 24. Up to 82,608 entities were in the world, covering buildings, deployables and the rest. Up to 3,005 MB of memory was used. Players feel lag when fps drops and entities pile up.
On what Rust version does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] sit?
You will find Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] reset?
The gap between Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]'s wipes has been about 7.3 days recently. Friday 30 October at 15:32 UTC is the date set for its next wipe. 4 days 13 hours have passed since this world was made. Its tags say it wipes every two weeks.
What happens on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] when wipe day arrives?
Across its recent wipes, the busiest moments averaged 3 players. Peak numbers came 8 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. Day 4 is when it sank below half in the wipes that did not hold.
Player count
What position does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] hold in the rankings?
In Europe, Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] is #1,785, and overall it is #5,426 on player hours over the last seven days, in the top 24% of all ranked servers.
Is Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] a busy server?
Right now, 0 players are on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10], which has 100 slots. The seven-day average is 0 players, with a peak of 2. Over the last 48 hours, the peak hour was 06:00 UTC, averaging 2 players.
Lists and filters
What do Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]'s tags stand for?
The game's browser takes its cue from the tags Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] has set: gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EU (Europe): The server browser lists it under Europe. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]: 10x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters 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.
Server rules
What settings and rules apply on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] sets gather at 10x, as its name suggests. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
A procedural map of size 3,700 and seed 2090362659, generated by the game, is what Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10] runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How do you get onto Cloud #1 [x10|Procedural|LOOT+|KIT|WIPE 23.10]?
Enter client.connect 85.233.150.44:35010 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,^b,EU,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EU
EuropeThe server browser lists it under Europe.
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 uptime (A+); population is the one to work on (F).