Offline 69.230.70.17:28015 checked 24d ago
Clouder Test Two
Connect
srv = rust.server("69.230.70.17:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 03:50 UTC25d ago | 0 | NaN | running | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 69.230.70.17:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 03:50 UTC
- hostname
- –
- first seen
- 4 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 143/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 10/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 20/1000 |
Quick answers
From the figures on this page.
Population data
How does Clouder Test Two compare in the rankings?
Rank #15,991 on seven-day player hours for Clouder Test Two, within the top 71% of all ranked servers.
How full does Clouder Test Two run?
Clouder Test Two returns no live count at this refresh, having last been seen 24 days 18 hours ago.
About the server
What Rust version does Clouder Test Two run?
The build is Rust network protocol 2634 and build 166652 on Linux, run by Clouder Test Two. Steam updates your game for you, but the protocol must match to join.
How reliable is Clouder Test Two, and is it online now?
Offline now for Clouder Test Two, last seen 24 days 18 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 4 October 2026.
In which location is Clouder Test Two hosted?
For Clouder Test Two, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 69.230.70.17:28015.
Map and rules
Which rules apply on Clouder Test Two, and what settings?
No gather rate appears in the name: Clouder Test Two. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has Clouder Test Two loaded?
Clouder Test Two runs a procedural map, which the game generates.
Wipe schedule
When does Clouder Test Two wipe, and how often?
Too few wipes are on record for Clouder Test Two to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 25 days 6 hours ago.
What is wipe day on Clouder Test Two like?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which lists on Rust Data hold Clouder Test Two, and which filters?
The Rust Data lists that Clouder Test Two fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Clouder Test Two hold?
The game's server browser reads these tags from Clouder Test Two: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into Clouder Test Two?
In Rust, F1 opens the console: type client.connect 69.230.70.17:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.