RUST METRICSFlight deck · live data
Data live Servers11,837 Players77,657 Populated3,729 Fresh wipes 3 h257 Scan5 min
‹ All servers185.135.150.122:28015
Offline Full Queue Fresh wipe Wipe due No query

Kirill123

Offline 185.135.150.122:28015 checked 39d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 0 /15

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#15,381no region published
Last wipe41d 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
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 18 Sep, 08:53 UTC41d ago 1 – running 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 timing

What happens on Kirill123 when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 1 hours in.

How often does Kirill123 wipe, and when?

The rhythm of Kirill123'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. 41 days 5 hours ago the current world was made.

Tag meanings

How should you read the tags on Kirill123?

Tags published by Kirill123, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp15 (Max players): 15 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Kirill123 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Kirill123: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does Kirill123 sit in the rankings?

Ranking for Kirill123: #15,381 on seven-day player hours, top – of all ranked servers.

How full does Kirill123 get?

Reading for Kirill123: offline at this moment; last seen 39 days 19 hours ago.

Operator and location

Which location does Kirill123 run from?

No region comes from Kirill123. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 185.135.150.122:28015.

What Rust version is Kirill123 on?

Version check: Rust network protocol 2633 and build 164530 on Windows, run by Kirill123. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. Kirill123 is offline at this moment. Last contact was 39 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 17 September 2026.

Settings and map

How is Kirill123 configured, and what rules are in force?

Reading the name gives no gather rate for Kirill123. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Kirill123?

Procedural map on Kirill123, made by the game's generator.

How to join

How do you connect to Kirill123?

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

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp15
Max players 15 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs164530
Build Build 164530.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.