RUST METRICSFlight deck · live data
Data live Servers11,739 Players61,775 Populated3,380 Fresh wipes 3 h186 Scan5 min
‹ All servers213.202.222.91:28015
Offline Full Queue Fresh wipe Wipe due No query

Nikitikita_server

Offline 213.202.222.91:28015 checked 15d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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,194top 61%
Last wipe18d 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
15k10k15k20k11 Oct13 Oct15 Oct16 Oct18 Oct20 Oct

Top 61% 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 schedule

When does Nikitikita_server wipe?

The rhythm of Nikitikita_server'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 18 days 19 hours ago.

Tag meanings

How should you read the tags on Nikitikita_server?

Tags published by Nikitikita_server, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167584 (Build): Game build reading: 167584; 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 Nikitikita_server?

Rust Metrics lists featuring Nikitikita_server: 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.

Population

What position does Nikitikita_server hold among Rust servers?

Player hours over seven days put Nikitikita_server at #13,194, in the top 61% of all ranked servers.

What is the population on Nikitikita_server?

Nikitikita_server is not responding; status offline, last seen 15 days 21 hours ago.

Operator and location

Which location does Nikitikita_server run from?

No region comes from Nikitikita_server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 213.202.222.91:28015.

What Rust version is Nikitikita_server on?

Reading: Nikitikita_server, Rust network protocol 2634 and build 167584, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. Nikitikita_server last answered 15 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 11 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Nikitikita_server?

Reading the name gives no gather rate for Nikitikita_server. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is Nikitikita_server on?

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

Join

How can you get onto Nikitikita_server?

Press F1 in Rust and enter client.connect 213.202.222.91: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 mp1,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players The server holds 1 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167584
Build Game build reading: 167584.
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.