RUST METRICSFlight deck · live data
Data live Servers11,691 Players58,743 Populated3,438 Fresh wipes 3 h104 Scan5 min
‹ All servers77.22.255.101:28015
Offline Full Queue Fresh wipe Wipe due No query

Kaito Test Server

Offline 77.22.255.101:28015 checked 20d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 1 /5

Players now

20% 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#14,199top 64%
Last wipe20d 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
15k10k15k20k7 Oct8 Oct10 Oct11 Oct13 Oct14 Oct

Top 64% 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

When does Kaito Test Server wipe?

Its rhythm cannot be told from the wipes of Kaito Test Server 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. 20 days 18 hours ago the current world was made.

Tags

Which tags does Kaito Test Server carry, and what do they mean?

These are the tags Kaito Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167058 (Build): The server runs game build 167058; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Kaito Test Server?

These Rust Metrics lists carry Kaito Test Server: 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.

Player count

Where does Kaito Test Server sit in the rankings?

Player hours over seven days put Kaito Test Server at #14,199, in the top 64% of all ranked servers.

How full does Kaito Test Server get?

Reading for Kaito Test Server: offline at this moment; last seen 20 days 18 hours ago.

Server details

Which location does Kaito Test Server run from?

Reading: location. Kaito Test Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 77.22.255.101:28015.

What Rust version is Kaito Test Server on?

Version check: Rust network protocol 2634 and build 167058 on Windows, run by Kaito Test Server. To get in, your game needs the same protocol; Steam applies the update.

Is Kaito Test Server up, and how often does it stay up?

Check: connection. Kaito Test Server is offline at this moment. Last contact was 20 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 7 October 2026, recorded by Rust Metrics.

Settings and map

How is Kaito Test Server configured, and what rules are in force?

Reading the name gives no gather rate for Kaito Test Server. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Kaito Test Server?

Procedural map on Kaito Test Server, made by the game's generator.

How to join

How can you get onto Kaito Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs167058,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players 5 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167058
Build The server runs game build 167058.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.