Statistical profileOffline
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]
95.85.249.130:35020 checked 28d ago
Connect to this server
1. Main points
Players now
0/ 100
0% full
7-day average
0
peak –
Rank
#16,413
top 69%
Last wipe
42d ago
no schedule published
Next wipe
–
no wipe seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 100 slots.
- It ranks #16,413 of all ranked servers, the top 69%, on player hours over the last seven days.
- Its current map went up 42d ago.
2. Players
Figure 1: Players on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 4: Map of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| MRAZ RUST [ X5/X10 | NOLIMIT | LOOT+ | KITS ] 27.10 | EU · groups of 1000+ · 5x · 124 on average | 140 / 250 |
| HollowServers.co 5x No BPs [Loot++|MyMini|Shop|Events]10x | NA · groups of 8+ · 5x · monthly · 117 on average | 142 / 150 |
| [EU/TR] Suayip 5x NO LIMIT | Loot X5 | TP | Home | Kit | EU · groups of 100+ · 5x · 89 on average | 188 / 300 |
| WARBANDITS.GG EU 5X No BPs |Loot++|PvP|MyMini|Shop|X5 JUST WIPE | EU · groups of 40+ · 5x · weekly · 80 on average | 115 / 200 |
| AceRust.com 5x No BPs [Loot++|PvP|MyMini|Shop]10x | NA · groups of 8+ · 5x · monthly · 76 on average | 43 / 150 |
| Atlas - EU 5x | No BPs | Kits | EU · groups of 20+ · 5x · weekly · 66 on average | 109 / 150 |
10. Quick answers
From the figures on this page.
Wipe schedule
When does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] wipe, and how often?
Too few wipes of Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] are on record to establish its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world was generated 42 days ago.
Server details
Is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] up, and how well has it held up?
Last seen 28 days 4 hours ago, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] is offline in this release. 0 of 168 hours on across the last 7 full days gives an uptime of 0%. First recorded by Rust Census on 1 October 2026.
In which location is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] based?
A region is not published by Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]. Rust Census does not look up where the machine stands; it shows where a server says it is. 95.85.249.130:35020 is its address.
Which Rust version is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] running?
The version in use on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] is Rust network protocol 2633 and build 165217 on Linux. Steam updates your game for you, but it has to be on the same protocol to join.
Population
What population has been recorded on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] is offline at present; its last recording was 28 days 4 hours ago.
In the rankings of Rust servers, where is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] placed?
For seven-day player hours, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] is ranked #16,413, placing it in the top 69% of all ranked servers.
Tag details
Where does Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] appear among the Rust Census lists and filters?
Included in these Rust Census lists is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]: 5x Rust servers: the counted list and Modded Rust servers, counted. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 5x.
The tags on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]: what do they indicate?
Read by the game's server browser, Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] publishes these tags: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp100 (Max players): 100 slots are available; ts8 (Group limit): 8 per team, which is the game's default limit; v2633 (Protocol): Your game must run protocol 2633 to join; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
Which map is in use on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
A procedural map runs on Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09], generated by the game.
How is Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] configured, and what rules does it keep?
Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09] carries a 5x gather rate, as stated in its name. The group cap stands at 8 players, the default for the game. survival is the game mode recorded, the standard game: gather, build, raid. Fighting other players and raiding are allowed. Plugins or settings change the game, and the browser lists it under Modded. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
How to join
How can you connect to Cloud #3 [x5|PROCEDURAL|LOOT+|TP|KIT|REC|TR|WIPE 18.09]?
Enter client.connect 95.85.249.130:35020 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp100,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp100 | Max players 100 slots are available. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2633 | Protocol Your game must run protocol 2633 to join. |
cs165217 | Build The server runs game build 165217. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code No region code is set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
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.