RUST METRICSFlight deck · live data
Data live Servers11,614 Players34,171 Populated2,816 Fresh wipes 3 h69 Scan5 min
‹ All servers85.233.150.44:35025
Online Full Queue Fresh wipe Wipe due No query

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

Online 85.233.150.44:35025 checked 11m ago

2x moddedoxide
COM 1 · connect

Server instruments

last reading Thu 05:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 60 SERVER FPS

Server fps

48 h low 52 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 82,769 ×1000

Entities

48 h range 80,572–83,319 · memory 3,565 MB
1239 ET SINCE RESTART 2D 04H

Uptime

2 days 4 hours since its last restart, at the last reading
7-day average0peak 1
Rank#6,942top 31%
Last wipe12d agono schedule published
Next wipe–no rhythm it keeps
Memory3,565MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75107:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608007:0016:0001:0010:0020:0005: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.

REC 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

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
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]?

The busiest point of its recent wipes drew 2 players on average. 47 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 5.5 it fell below half.

How often does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] wipe, and when?

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 next monthly force wipe takes every Rust server, including this one. The world it runs now was made 12 days 18 hours ago.

Tag meanings

Which tags does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] carry, and what do they mean?

These are the tags Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] appear in Rust Metrics lists and filters?

On Rust Metrics, Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] sits in these lists: 2x Rust servers, checked live and Modded Rust servers, checked live. These filters bring it up 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.

Player count

Where does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] sit in the rankings?

Player hours over seven days put Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] at #6,942, in the top 31% of all ranked servers.

What player count does Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] carry?

Current headcount on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]: 0 players, 100 slots available. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 1 players, at 00:00 UTC over the last 48 hours.

Server

What location is Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] hosted in?

Reading: location. Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 85.233.150.44:35025.

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

Reading: Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10], Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

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

Over the last 48 hours the average was 60 server fps; the floor was 52. Peak entity count: 83,319. Buildings, deployables and all else included. Memory peak: 3,683 MB. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10], and is it online?

Reading: online. Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10] answers right now. Reading: uptime. About 2 days 4 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

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

Gather rate check: 2x. That comes from the name Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

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

From seed 1595316433, the game generates the procedural map on Cloud #4 [x2|TP|REMOVE|DUEL|SKIN|WIPE 16.10]. Its size is 3,700. View it on RustMaps from this page: matching size and seed give an identical map.

Join

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

Check: join. Open Rust, press F1, then enter client.connect 85.233.150.44:35025. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at http://cloudrust.ru/.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.