Rust Server TrendsSeismic network · station log
Recording Stations11,752 Players57,724 Active3,422 Wipes · 3 h129 48 h

Station XX-7197 · recording

Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]

Online 85.233.150.44:35025 checked 7m ago

2x moddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#7,197
top 32%
Last wipe
12d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-7197 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 100 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+0into Tue 17:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75123:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

02040608023:0008:0017:0002:0011:0021:00

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 32% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

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 gap
13.5 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
0%else halves by day 5.5

The first 48 hours of its last wipes

Fri 16 OctFri 2 OctSat 19 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 47 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 16 Oct, 11:50 UTC12d ago M0.5rising 3 – running 0
Fri 2 Oct, 12:58 UTC26d ago M0.0rising 1 halved by day 2 14 days 0
Sat 19 Sep, 11:22 UTC39d ago M0.5rising 3 halved by day 9 13.1 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 791 on average
531/ 650
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 591 on average
262/ 350
Atlas - US 2X Monthly | Vanilla+ | No BP Wipes NA · groups of 16+ · 2x · monthly · 366 on average
169/ 200
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr EU · groups of 50+ · 2x · monthly · 346 on average
170/ 205
Magic Rust #18 — Vanilla 2x | Baйп 28.10 EU · groups of 150+ · 2x · weekly · 321 on average
703/ 900
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 EU · groups of 300+ · 2x · weekly · 311 on average
103/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?

Generated by the game, the map on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] is procedural, size 3,700 with seed 1595316433. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?

2x gather is what Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] runs, judging by its name. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] right now?

At this moment, Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] records 0 players across 100 slots. Across seven days this server recorded an average of 0 players and a peak of 1. The last 48 hours show their highest activity at 17:00 UTC, averaging 0 players.

How does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] rank against other Rust servers?

On player hours for the past week, Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] sits at #7,197, which puts it inside the top 32% of every ranked server.

Server facts

How reliably does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] stay online?

As recorded now, Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] is running. Going by the uptime figure it reports, it restarted about 44 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] hold a steady tick rate?

Its average server fps over the last 48 hours was 60, and it never dropped below 52. At its highest, it carried 83,319 entities: buildings, deployables and the world's other contents. It reached a ceiling of 3,683 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] run from?

Nothing about a region comes from Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 85.233.150.44:35025.

Which Rust version is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] running?

Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] is running Rust network protocol 2635 and build 168909 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?

On average, the busiest point of its recent wipes drew 2 players. The peak on the most recent wipe came 47 hours after the wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell under half by day 5.5 in the wipes where it didn't hold.

On what timetable does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] run its wipes?

No next wipe can be predicted for Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10], which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 12 days 11 hours.

Server tags

What do the server tags on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] mean?

The game's server browser reads the tags Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] publishes: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): 100 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] appear?

You will find Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] on the following Rust Server Trends lists: 2x Rust servers, listed live and Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 2x.

Connecting

How do you connect to Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?

To join, enter client.connect 85.233.150.44:35025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at http://cloudrust.ru/.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp100
Max players 100 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.