Working its way up from the back of the class: #16,413 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 302 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
Which region is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] based in?
No region is published for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 95.85.249.130:35020.
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] up, and how steady is its uptime?
The server is down: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] is offline now, with the last sighting 27 days 23 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 1 October 2026.
Which Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] running?
You will find Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] on Rust network protocol 2633 and build 165217, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] wipe its map?
There are too few wipes on record for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 41 days 19 hours.
Player count
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] place in the wider field of Rust servers?
In the top 69% of all ranked servers, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] sits at #16,413 for player hours over the last seven days.
What does the population on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] look like?
It has been 27 days 23 hours since Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
You'll see Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. 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 18.09]?
These Rust Server Score lists count Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] among them: 5x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 5x.
Server rules
Which rules does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] enforce, and what are its settings?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] sets gather at 5x, 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. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
A procedural map, generated by the game, is what Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] runs.
Connecting
How should you connect to Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
To connect, start Rust, press F1, and type client.connect 95.85.249.130:35020. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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 momentum (D); standing is the one to work on (F).