RUST METRICSFlight deck · live data
Data live Servers11,855 Players100,368 Populated3,884 Fresh wipes 3 h533 Scan5 min
‹ All servers165.140.179.50:28015
Offline Full Queue Fresh wipe Wipe due No query

KAD test - Rust

Offline 165.140.179.50:28015 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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#16,011top 70%
Last wipe26d agono schedule published
Next wipe–too few wipes 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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct4 Oct6 Oct7 Oct9 Oct10 Oct

Top 70% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 02:48 UTC26d ago 1 – 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 happens on KAD test - Rust when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does KAD test - Rust follow?

Its rhythm cannot be told from the wipes of KAD test - Rust on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 26 days 17 hours ago.

Lists and filters

Which tags does KAD test - Rust carry, and what do they mean?

These are the tags KAD test - Rust publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show KAD test - Rust?

These Rust Metrics lists carry KAD test - Rust: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does KAD test - Rust sit in the rankings?

Player hours over seven days put KAD test - Rust at #16,011, in the top 70% of all ranked servers.

What player count does KAD test - Rust carry?

KAD test - Rust is not responding; status offline, last seen 26 days 3 hours ago.

Server details

Which location does KAD test - Rust run from?

No region comes from KAD test - Rust. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 165.140.179.50:28015.

What Rust version is KAD test - Rust on?

Reading: KAD test - Rust, Rust network protocol 2634 and build 166652, Linux. Matching protocol is required to join. Let Steam update your game.

Is KAD test - Rust up, and how often does it stay up?

KAD test - Rust reports offline. The last reading came 26 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 2 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on KAD test - Rust?

Check: gather rate. The name KAD test - Rust does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on KAD test - Rust?

Size 3,500 and seed 4242: the game generates the procedural map on KAD test - Rust from them. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

How do you connect to KAD test - Rust?

Press F1 in Rust and enter client.connect 165.140.179.50:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Build 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.