Online 104.193.180.33:25565 checked 10m ago
cave testing
Connect
srv = rust.server("104.193.180.33:25567")
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 69% 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 | Sat 3 Oct, 08:06 UTC26d 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
- 104.193.180.33:25565
- region
- –
- max players
- 8
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 08:06 UTC
- hostname
- –
- first seen
- 13 Sep 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 | 178/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/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 · 94 on average | 88/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 335/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 229/700 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does cave testing rank?
Player hours over seven days put cave testing at #15,344, in the top 69% of the ranked set.
What population does cave testing carry?
The sample now reads 0 players for cave testing, out of 8 slots. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on cave testing?
Version Rust network protocol 2635 and build 168909 on Linux is reported by cave testing. Joining needs the same protocol on your game; Steam handles the update.
How reliable is cave testing, and is it up?
Online is the state at the latest refresh for cave testing. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 13 September 2026.
Which location does cave testing run from?
No region is published by cave testing. Rust Data does not look up where the machine stands; it shows where a server says it is. 104.193.180.33:25565 is its address.
Rules, settings, map
What rules and settings are recorded for cave testing?
You will not find a gather rate in the string cave testing. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is not running; Valve's anti-cheat is off.
Which map has cave testing loaded?
cave testing runs a procedural map, which the game generates.
Wipe schedule
When does cave testing wipe, and on what schedule?
Too few wipes are on record for cave testing to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 26 days 7 hours ago.
On cave testing, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which Rust Data filters and lists contain cave testing?
These Rust Data lists include cave testing: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on cave testing hold?
Read by the game's server browser, the tags cave testing publishes are: gmrust (Game mode): Survival play, standard Rust; mp8 (Max players): Slot count: 8; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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
What is the way into cave testing?
In Rust, F1 opens the console: type client.connect 104.193.180.33:25565. Launch Rust on this page does the same by opening the game through Steam and connecting.