Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h95 48 h

Station XX-15478 · no signal

Kavkaz Testing

Offline 31.76.51.111:28015 checked 40d ago

Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,478
top 70%
Last wipe
53d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15478 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 550 on average
636/ 675
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
485/ 525
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 300 on average
59/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 300 on average
36/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 269 on average
138/ 200
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 257 on average
255/ 300
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Kavkaz Testing?

Kavkaz Testing runs a procedural map of size 1,200 with seed 12345, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on Kavkaz Testing?

No gather rate appears in the name of Kavkaz Testing. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Community, as a community server. Anti-cheat is off: VAC, from Valve.

Player counts

How many players are recorded on Kavkaz Testing right now?

No players are recorded on Kavkaz Testing at this moment; it is offline, and the last sighting was 40 days ago.

How does Kavkaz Testing rank against other Rust servers?

On player hours for the past week, Kavkaz Testing sits at #15,478, which puts it inside the top 70% of every ranked server.

Operator and location

How reliably does Kavkaz Testing stay online?

As recorded now, Kavkaz Testing is not reachable, the last contact having been 40 days ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is Kavkaz Testing hosted?

A region is not published by Kavkaz Testing. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 31.76.51.111:28015 is the address it uses.

What build of Rust does Kavkaz Testing use?

On Linux, Kavkaz Testing runs Rust network protocol 2633 and build 163207. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

On what timetable does Kavkaz Testing run its wipes?

Too few wipes of Kavkaz Testing are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 53 days 3 hours.

Tags

What do the server tags on Kavkaz Testing mean?

The game's server browser reads the tags Kavkaz Testing publishes: gmvanilla (Game mode): You'll find vanilla survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs163207 (Build): It runs game build 163207; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Kavkaz Testing appear?

You will find Kavkaz Testing on the following Rust Server Trends lists: Rust community servers without the side modes. 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.

How to join

How do you connect to Kavkaz Testing?

To join, enter client.connect 31.76.51.111:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

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

Game

gmvanilla
Game mode You'll find vanilla survival here.
mp10
Max players The server has 10 slots.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs163207
Build It runs game build 163207.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.