RUST METRICSFlight deck · live data
Data live Servers11,666 Players52,161 Populated3,273 Fresh wipes 3 h84 Scan5 min
‹ All servers31.56.185.31:28015
Online Full Queue Fresh wipe Wipe due No query

klimashook_r34

Online 31.56.185.31:28015 checked 10m 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 avg7-day peak
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 1
Rank#14,352top 65%
Last wipe3d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k30 Sep5 Oct10 Oct15 Oct20 Oct28 Oct

Top 65% 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.

usual gap22.8 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 24 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 24 Oct, 13:16 UTC3d ago 1 – running 0
Thu 1 Oct, 18:18 UTC FW26d ago – – 22.8 days 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

Wipe schedule

What should you expect from wipe day on klimashook_r34?

At their busiest, its recent wipes drew 1 players on average. 4 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does klimashook_r34 follow?

The rhythm of klimashook_r34's wipes cannot be told yet: too few are on record. 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 3 days 20 hours ago.

Tag meanings

How should you read the tags on klimashook_r34?

Tags published by klimashook_r34, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. 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 klimashook_r34?

Rust Metrics lists featuring klimashook_r34: 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; Last wipe: In the last week.

Player count

Where does klimashook_r34 sit in the rankings?

Player hours over seven days put klimashook_r34 at #14,352, in the top 65% of all ranked servers.

What is the population on klimashook_r34?

Current headcount on klimashook_r34: 0 players, 10 slots available. Check: players over seven days. Average 0, peak 1.

Server

Where does klimashook_r34 sit?

Reading: location. klimashook_r34 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 31.56.185.31:28015.

What Rust version is klimashook_r34 on?

Reading: klimashook_r34, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on klimashook_r34, and is it online?

klimashook_r34 reports online. Status: normal. Reading: 12% uptime over the last 7 full days. It was up 20 of 168 hours. Check: first contact. Rust Metrics logged it on 30 September 2026.

Rules and settings

What rules does klimashook_r34 enforce, and what are its settings?

Reading the name gives no gather rate for klimashook_r34. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is klimashook_r34 on?

The game generates a procedural map for klimashook_r34.

Connection

How do you connect to klimashook_r34?

Press F1 in Rust and enter client.connect 31.56.185.31: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?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
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.