RUST METRICSFlight deck · live data
Data live Servers11,752 Players56,681 Populated3,410 Fresh wipes 3 h130 Scan5 min
‹ All servers60.150.188.67:28015
Offline Full Queue Fresh wipe Wipe due No query

Kakapo_server

Offline 60.150.188.67:28015 checked 14d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /500

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#13,027top 60%
Last wipe24d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct7 Oct10 Oct15 Oct18 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

Wipe timing

When does Kakapo_server wipe?

Its rhythm cannot be told from the wipes of Kakapo_server on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 24 days 4 hours ago.

Tags

Which tags does Kakapo_server carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from Kakapo_server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Kakapo_server appear in Rust Metrics lists and filters?

On Rust Metrics, Kakapo_server sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does Kakapo_server hold among Rust servers?

Player hours over seven days put Kakapo_server at #13,027, in the top 60% of all ranked servers.

What player count does Kakapo_server carry?

Kakapo_server is not responding; status offline, last seen 14 days 18 hours ago.

Operator and location

What location is Kakapo_server hosted in?

Reading: location. Kakapo_server gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 60.150.188.67:28015.

What Rust version is Kakapo_server on?

Reading: Kakapo_server, Rust network protocol 2634 and build 167781, Windows. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Kakapo_server, and is it online now?

Kakapo_server reports offline. The last reading came 14 days 18 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 4 October 2026.

Settings and map

What settings and rules apply on Kakapo_server?

No gather rate appears in the name: Kakapo_server. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is Kakapo_server on?

Check: map. Procedural, generated by the game, on Kakapo_server.

Join

How can you get onto Kakapo_server?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players The server holds 500 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.