RUST METRICSFlight deck · live data
Data live Servers11,696 Players36,352 Populated2,907 Fresh wipes 3 h94 Scan5 min
‹ All servers178.66.128.82:28015
Offline Full Queue Fresh wipe Wipe due No query

Nikitikita_server

Offline 178.66.128.82:28015 checked 36d 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,183top 57%
Last wipe36d 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
15k10k15k20k22 Sep23 Sep25 Sep26 Sep28 Sep29 Sep

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

What wipe timing does Nikitikita_server follow?

To tell the rhythm of Nikitikita_server, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 36 days 18 hours ago.

Lists and filters

How should you read the tags on Nikitikita_server?

Tags published by Nikitikita_server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): The server runs game build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Nikitikita_server appear in Rust Metrics lists and filters?

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

Population

Where does Nikitikita_server sit in the rankings?

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

How full does Nikitikita_server get?

Status for Nikitikita_server: offline. Last seen 36 days 9 hours ago.

Server details

Which location does Nikitikita_server run from?

No region tag on Nikitikita_server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 178.66.128.82:28015.

What Rust version is Nikitikita_server on?

Reading: Nikitikita_server, Rust network protocol 2633 and build 164530, Windows. Matching protocol is required to join. Let Steam update your game.

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

Nikitikita_server reports offline. The last reading came 36 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 22 September 2026.

Map and rules

What settings and rules apply on Nikitikita_server?

No gather rate appears in the name: Nikitikita_server. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is Nikitikita_server on?

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

Connection

How can you get onto Nikitikita_server?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build The server runs game build 164530.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.