RUST METRICSFlight deck · live data
Data live Servers11,837 Players81,308 Populated3,746 Fresh wipes 3 h263 Scan5 min
‹ All servers104.193.180.33:25565
Online Full Queue Fresh wipe Wipe due No query

cave testing

Online 104.193.180.33:25565 checked 13m ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 4 6 8 PAX 0 /8

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,335top 69%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

AveragePeak
0123415:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 08:06 UTC26d ago 0 – 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on cave testing?

The busiest point of its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

How often does cave testing wipe, and when?

Its rhythm cannot be told from the wipes of cave testing on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 26 days 6 hours ago the current world was made.

Tags

How should you read the tags on cave testing?

These are the tags cave testing publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp8 (Max players): 8 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show cave testing?

On Rust Metrics, cave testing sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does cave testing hold among Rust servers?

Player hours over seven days put cave testing at #15,335, in the top 69% of all ranked servers.

How full does cave testing get?

0 of 8 slots are filled on cave testing right now. Seven-day reading: 0 players on average.

Operator and location

Which location does cave testing run from?

No region comes from cave testing. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 104.193.180.33:25565.

What Rust version is cave testing on?

Rust network protocol 2635 and build 168909 on Linux is the build cave testing runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on cave testing, and is it online?

Reading: online. cave testing answers right now. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What rules does cave testing enforce, and what are its settings?

Check: gather rate. The name cave testing does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on cave testing?

Check: map. Procedural, generated by the game, on cave testing.

Connection

How do you connect to cave testing?

To join: start Rust, press F1 and type client.connect 104.193.180.33:25565. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp8,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp8
Max players 8 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock 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.