On the class lists: C (62), with population over 48 hours and no performance mark.
Players now1/ 1001% full
7-day average1peak 6
Rank#3,483top 16% · #1302 in EU
Last wipe5d agobiweekly schedule
Next wipe2d 3hFri 30 Oct, 15:34 UTC
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
84/ 100
B+
Holds a respectable place: #3,483 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 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
60/ 100
C
Keeps a fair share of its players through a wipe: 60% of wipes kept half their crowd.
Momentumrank now against a week ago
67/ 100
C+
Climbing fast: up 1,203 places this week.
A steady term.
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 16% of all ranked servers, top 45% 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:34 UTC, in 2d 3h.
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 held60%else halves by day 5.5
Coming wipes
2d 3hFri 30 Oct, 15:34 UTC
8d 6hThu 5 Nov, 19:00 UTCFW
9d 6hFri 6 Nov, 19:21 UTC
16d 10hFri 13 Nov, 23:08 UTC
23d 14hSat 21 Nov, 02:54 UTC
30d 18hSat 28 Nov, 06:41 UTC
36d 6hThu 3 Dec, 19:00 UTCFW
37d 21hSat 5 Dec, 10:28 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 3, 6 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 11:47 UTC5d ago
3
–
running
0
Fri 16 Oct, 08:01 UTC12d ago
3
halved by day 6
7.2 days
0
Thu 8 Oct, 16:08 UTC19d ago
4
✓ held half
7.7 days
0
Fri 2 Oct, 12:57 UTC25d ago
5
halved by day 5
6.1 days
0
Fri 25 Sep, 03:34 UTC33d ago
4
✓ held half
7.4 days
0
Thu 17 Sep, 19:34 UTC40d ago
2
✓ held half
7.3 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
EU · groups of 14+ · 10x · weekly · 150 on average
148 / 400
Quick answers
from the figures on this page
Server details
In what location does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] sit?
In Europe, according to its own listing, sits Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], with the EU tag. 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:35015.
How reliable is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10], and is it up?
Right now, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is online. According to its reported uptime, the last restart was about 34 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] perform well?
It never fell below 33 server fps in the last 48 hours, averaging 58. At its peak, it held 88,778 entities, including buildings, deployables and all else in the world. Up to 3,365 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on?
You will find Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] wipe, and how often?
About every 7.3 days, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has wiped lately. Friday 30 October at 15:34 UTC is the date set for its next wipe. It has been running its current world for 5 days. Its tags say it wipes every two weeks.
What should you expect from wipe day on Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Across its recent wipes, the busiest moments averaged 3 players. 6 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 60% of its recent wipes. The crowd dropped below half by day 5.5 in the wipes where it did not hold.
Player count
What position does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] hold in the rankings?
Over the last seven days, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] has #3,483 for player hours, in the top 16% of all ranked servers and #1,302 in Europe.
Is Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] a busy server?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] is showing 1 players right now, with 100 slots in total. Averaging 1 players over seven days, it peaked at 6. The highest average in the last 48 hours came at 19:00 UTC, with 4 players.
Tags and filters
What do Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]'s tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; 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): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EU (Europe): You will find it under Europe in the browser are the tags Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.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 Rust Server Score filters and lists feature Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
Rust Server Score lists that include Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]: 10x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: 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.
Map and rules
Which rules does Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] enforce, and what are its settings?
Going by its name, Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs 10x gather. The group limit stays at the game's default of 8 players. 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. The server runs Valve's anti-cheat, VAC.
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs which map?
Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10] runs a game-generated procedural map at size 3,700, seed 262731628. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How do you get onto Cloud #2 [x10|Procedural|LOOT+|KIT|REC|WiPE 23.10]?
To connect, start Rust, press F1, and type client.connect 85.233.150.44:35015. Or click Launch Rust here, which launches Rust through Steam and joins you.
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 players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
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
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
EU
EuropeYou will find it under Europe in the browser.
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 steady term. Strongest in uptime (A+); population is the one to work on (F).