RUST METRICSFlight deck · live data
Data live Servers11,802 Players77,039 Populated3,777 Fresh wipes 3 h111 Scan5 min
‹ All servers31.76.51.111:28015
Offline Full Queue Fresh wipe Wipe due No query

Kavkaz Testing

Offline 31.76.51.111:28015 checked 40d 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#15,478top 70%
Last wipe53d 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, measured since 17 Sep. 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 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

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

Wipe timing

What wipe timing does Kavkaz Testing follow?

Its rhythm cannot be told from the wipes of Kavkaz 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. The world it runs now was made 53 days 5 hours ago.

Tag meanings

Which tags does Kavkaz Testing carry, and what do they mean?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163207 (Build): Game build reading: 163207; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Kavkaz Testing. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Kavkaz Testing appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Kavkaz Testing: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does Kavkaz Testing sit in the rankings?

Ranking for Kavkaz Testing: #15,478 on seven-day player hours, top 70% of all ranked servers.

What is the population on Kavkaz Testing?

Reading for Kavkaz Testing: offline at this moment; last seen 40 days 2 hours ago.

Operator and location

Which location does Kavkaz Testing run from?

No region comes from Kavkaz Testing. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 31.76.51.111:28015.

What Rust version is Kavkaz Testing on?

Version check: Rust network protocol 2633 and build 163207 on Linux, run by Kavkaz Testing. Check: protocol. To join, your game must match; Steam handles the update.

Is Kavkaz Testing up, and how often does it stay up?

Check: connection. Kavkaz Testing is offline at this moment. Last contact was 40 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on Kavkaz Testing?

No gather rate appears in the name: Kavkaz Testing. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is off. That is Valve's anti-cheat.

What map is Kavkaz Testing on?

From seed 12345, the game generates the procedural map on Kavkaz Testing. Its size is 1,200. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to Kavkaz Testing?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmvanilla,cs163207,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163207
Build Game build reading: 163207.
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.