RUST METRICSFlight deck · live data
Data live Servers11,876 Players95,829 Populated4,104 Fresh wipes 3 h157 Scan5 min
‹ All servers98.117.202.167:28195
Offline Full Queue Fresh wipe Wipe due No query

Saltwake private client test

Offline 98.117.202.167:28195 checked 10d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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,222top 70%
Last wipe10d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

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
15k10k15k20k17 Oct18 Oct20 Oct21 Oct23 Oct24 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

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 wipe timing does Saltwake private client test follow?

To tell the rhythm of Saltwake private client test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 10 days 10 hours ago.

Tag meanings

Which tags does Saltwake private client test carry, and what do they mean?

These are the tags Saltwake private client test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; 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): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Saltwake private client test?

Rust Metrics lists featuring Saltwake private client test: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

What position does Saltwake private client test hold among Rust servers?

Player hours over seven days put Saltwake private client test at #15,222, in the top 70% of all ranked servers.

What is the population on Saltwake private client test?

Status for Saltwake private client test: offline. Last seen 10 days 9 hours ago.

Server

What location is Saltwake private client test hosted in?

No region tag on Saltwake private client test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 98.117.202.167:28195.

What Rust version is Saltwake private client test on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by Saltwake private client test. Matching protocol is required to join. Let Steam update your game.

How reliable is Saltwake private client test, and is it online now?

Reading: offline. Saltwake private client test last answered 10 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 17 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does Saltwake private client test enforce, and what are its settings?

Check: gather rate. The name Saltwake private client test does not state one. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

Which map is live on Saltwake private client test?

Check: map. Procedural, generated by the game, on Saltwake private client test.

Connection

What do you do to join Saltwake private client test?

Check: join. Open Rust, press F1, then enter client.connect 98.117.202.167:28195. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players 2 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 167781.
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 Check: category. Modded, because plugins or settings alter 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.