Skip to the page
RUST ANALYTICS
LIVE85,290PLY11,689SRV
QUOTE 95.85.249.130:35020 Offline checked 13d ago

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]

5x moddedoxide
Players · last
0/ 100
n/a24h
0% full
Players · 24 hourshourly average, then now · dashed: 24 hours ago
No hourly readings in the last 24 hours.
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 100
0% full
Change · 24h
n/a
no reading a day ago
7-day average
0
peak –
Rank
#16,413
top 69%
Rank · 7d ago
#16,111
302 places down
Last wipe
26d ago
no schedule published
Next wipe
–
no wipe seen yet
Group limit
8
8, the default
Gather rate
5x
read from the name
Score
0
player hours, last seven days
Map
–
Procedural Map
First seen
1 Oct 2026
no hostname published

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

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

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
WipedPeakCrowdLastedPlayers 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

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10xNA · groups of 8+ · 5x · monthly · 111 on average50/150−6−10.2%
2MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 13.10EU · groups of 1000+ · 5x · 102 on average156/250−40−20.5%
3Классика x5 для НОВИЧКОВ |Loot+|BigBoyRust|EU · groups of 8+ · 5x · weekly · 83 on average33/300−19−36.2%
4AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10xNA · groups of 8+ · 5x · monthly · 80 on average68/150+48+248.7%
5[EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | KitEU · groups of 100+ · 5x · 72 on average259/300+177+216.8%
6Atlas - EU 5x | No BPs | KitsEU · groups of 20+ · 5x · weekly · 70 on average141/200+59+72.0%

Quick answers

from the figures on this page

Rules & Settings

How is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] configured in terms of rules and settings?

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] carries its gather rate in its name: 5x. Groups can contain a maximum of 8 players, the default for the game. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. The server has VAC, Valve's anti-cheat, switched on.

What is the current map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?

The game generates the procedural map on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09].

Player Count

What position does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] hold in the server rankings?

For the last seven days, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] holds rank #16,413 on player hours, in the top 69% of all ranked servers.

How many players does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] have?

At present, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] is offline; the last sighting was 13 days 1 hours ago.

Wipe Cycle

On what cycle does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] wipe?

No rhythm can be told for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] yet: too few of its wipes are on record. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. This world has been running for 26 days 21 hours.

Server Details

What is the location of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?

There is no region published for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 95.85.249.130:35020.

Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] is on which Rust version?

The build is Rust network protocol 2633 and build 165217 on Linux, running on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. Your game needs the same protocol to get in; Steam takes care of the update.

What is the uptime and reliability of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?

No response from Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. It was last seen 13 days 1 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. The earliest Rust Analytics saw it was 1 October 2026.

Server Tags

How should you interpret the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?

Published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): It holds 100 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2633 (Protocol): Protocol 2633: matching game versions are required to join; cs165217 (Build): Game build: 165217; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): The Modded listing applies: plugins or settings change play. The tags also carry its current players, queue and world creation time; this page shows them at the top.

On Rust Analytics, which lists and filters feature Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?

The following Rust Analytics lists feature Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]: Rust servers with 5x gather rates and Modded Rust servers. 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.

Joining the Server

What steps do I take to join Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?

Type client.connect 95.85.249.130:35020 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players It holds 100 slots.
ts8
Group limit At the game default, teams hold up to 8.
v2633
Protocol Protocol 2633: matching game versions are required to join.
cs165217
Build Game build: 165217.
ptrak
Networking Runs on RakNet, Rust's default network layer.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) is in use.
^z
Modded The Modded listing applies: plugins or settings change play.

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.