On the class lists: F (39), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 1
Rank#6,949top 31%
Last wipe12d agono schedule published
Next wipe–no rhythm it keeps
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
69/ 100
C+
Working its way up from the back of the class: #6,949 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
99/ 100
A+
Runs smoothly: 60 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
32/ 100
F
Lost ground: down 2,538 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in performance (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 31% 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 gap13.5 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 5.5
The first 48 hours of its last wipes
Fri 16 OctFri 2 OctSat 19 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, 11:50 UTC12d ago
3
–
running
0
Fri 2 Oct, 12:58 UTC26d ago
1
halved by day 2
14 days
0
Sat 19 Sep, 11:22 UTC39d ago
3
halved by day 9
13.1 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 300+ · 2x · weekly · 313 on average
50 / 1000
Quick answers
from the figures on this page
Server details
Which region is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] based in?
No region is published for Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 85.233.150.44:35025.
How reliable is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10], and is it up?
You can join now: Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] is online. About 47 hours ago, it restarted, based on the uptime it reports. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] smooth to play on?
The average over the last 48 hours was 60 server fps, and it never went below 52. At its peak, it held 83,319 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,683 MB. When fps is low and entities climb, that is lag to players.
What Rust version is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] on?
The server Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] reset?
Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] wipes at times that vary, so no next wipe can be predicted. 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 12 days 14 hours.
What happens on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. Peak numbers came 47 hours into the latest wipe. Half the peak held until the next wipe in 0% 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 #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] hold in the rankings?
Over the last seven days, Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] has #6,949 for player hours, in the top 31% of all ranked servers.
Is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] a busy server?
Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] is showing 0 players right now, with 100 slots in total. The seven-day average is 0 players, with a peak of 1. Over the last 48 hours, the peak hour was 00:00 UTC, averaging 1 players.
Tags
How should you read the tags on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; 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): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?
Rust Server Score lists that include Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]: 2x 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: 2x.
Server rules
What settings and rules apply on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?
Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] sets gather at 2x, as its name suggests. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] runs which map?
A procedural map of size 3,700 and seed 1595316433, generated by the game, is what Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?
To connect, start Rust, press F1, and type client.connect 85.233.150.44:35025. Or click Launch Rust here, which launches Rust through Steam and joins you. 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 modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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+); population is the one to work on (F).