Rust Data

rustdata.spaceservers95.85.249.130:35022.ipynb

Run all rust-data · live

‹ All servers

Offline 95.85.249.130:35020 checked 27d ago

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

5x moddedoxide

Connect

srv = rust.server("95.85.249.130:35022")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #16,413 # top 69%
last wipe 41d ago # no schedule published
next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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

srv.rank.plot(invert=True)  # 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

srv.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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
95.85.249.130:35020
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
17 Sep 2026, 19:34 UTC
hostname
–
first seen
1 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10EU · groups of 1000+ · 5x · 122 on average204/250
1HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10xNA · groups of 8+ · 5x · monthly · 116 on average127/150
2[EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | KitEU · groups of 100+ · 5x · 87 on average200/300
3WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPEEU · groups of 40+ · 5x · weekly · 80 on average103/200
4AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10xNA · groups of 8+ · 5x · monthly · 75 on average34/150
5Atlas - EU 5x | No BPs | KitsEU · groups of 20+ · 5x · weekly · 64 on average139/150

Quick answers

From the figures on this page.

Player counts

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

Rank #16,413 on seven-day player hours for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09], within the top 69% of all ranked servers.

What population does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] carry?

The current row shows Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] offline; the last response was 27 days 23 hours ago.

About the server

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

The build is Rust network protocol 2633 and build 165217 on Linux, run by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. Joining needs the same protocol on your game; Steam handles the update.

Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] up, and what does its uptime show?

The latest sample has Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] offline, with a last sighting 27 days 23 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 1 October 2026.

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

No region is published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 95.85.249.130:35020 is its address.

Settings and map

What rules and settings are recorded for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?

Gather sits at 5x, read from the server's own name: Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] selected?

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

Wipe schedule

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

The record for Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 41 days 19 hours ago.

Lists and tags

Which lists on Rust Data hold Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09], and which filters?

These Rust Data lists include Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]: Modded Rust servers and Rust servers filtered by gather rate: 5x. 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.

Which meanings do the tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] hold?

The game's server browser reads these tags from Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

How can I connect to Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?

Enter client.connect 95.85.249.130:35020 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players The server lists 100 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol To join, your game must run protocol 2633.
cs165217
Build Build number: 165217.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the 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.

Rust Data 84,816 players 11,846 servers online