RUST METRICSFlight deck · live data
Data live Servers11,750 Players60,289 Populated3,494 Fresh wipes 3 h127 Scan5 min
‹ All servers77.82.85.190:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST_KAMCHATKA

Offline 77.82.85.190:28015 checked 13d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 1 /100

Players now

1% 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#12,999top 60%
Last wipe14d 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 14 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
15k10k15k20k13 Oct15 Oct16 Oct18 Oct19 Oct21 Oct

Top 60% 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 TEST_KAMCHATKA follow?

The rhythm of TEST_KAMCHATKA's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 14 days 11 hours ago the current world was made.

Lists and filters

How should you read the tags on TEST_KAMCHATKA?

These are the tags TEST_KAMCHATKA publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; 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): No region code is 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 TEST_KAMCHATKA?

On Rust Metrics, TEST_KAMCHATKA sits in these lists: 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.

Occupancy

Where does TEST_KAMCHATKA sit in the rankings?

Player hours over seven days put TEST_KAMCHATKA at #12,999, in the top 60% of all ranked servers.

How full does TEST_KAMCHATKA get?

TEST_KAMCHATKA is not responding; status offline, last seen 13 days 14 hours ago.

Operator and location

What location is TEST_KAMCHATKA hosted in?

No region comes from TEST_KAMCHATKA. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 77.82.85.190:28015.

What Rust version is TEST_KAMCHATKA on?

Rust network protocol 2634 and build 167781 on Windows is the build TEST_KAMCHATKA runs. Matching protocol is required to join. Let Steam update your game.

Is TEST_KAMCHATKA up, and how often does it stay up?

TEST_KAMCHATKA reports offline. The last reading came 13 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 October 2026.

Map and rules

What settings and rules apply on TEST_KAMCHATKA?

No gather rate appears in the name: TEST_KAMCHATKA. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is TEST_KAMCHATKA on?

Size 3,000 and seed 618226138: the game generates the procedural map on TEST_KAMCHATKA from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How can you get onto TEST_KAMCHATKA?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
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 No region code is 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.