RUST METRICSFlight deck · live data
Data live Servers11,791 Players67,584 Populated3,634 Fresh wipes 3 h129 Scan5 min
‹ All servers178.66.128.173:28015
Offline Full Queue Fresh wipe Wipe due No query

Nikitikita_server

Offline 178.66.128.173:28015 checked 12d ago

COM 1 · connect
Launch Rust and join

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#12,899top 60%
Last wipe18d 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
15k10k15k20k25 Sep29 Sep11 Oct15 Oct19 Oct23 Oct

Top 60% of all ranked servers. Ranked on player hours over the last seven days.

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, 21 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 15:59 UTC18d ago 1 – running 1

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

What should you expect from wipe day on Nikitikita_server?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 21 hours.

What wipe timing does Nikitikita_server follow?

The rhythm of Nikitikita_server'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. The world in play was created 18 days 5 hours ago.

Tags

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

Tags published by Nikitikita_server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Nikitikita_server?

On Rust Metrics, Nikitikita_server sits in these lists: 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.

Occupancy

What position does Nikitikita_server hold among Rust servers?

Ranking for Nikitikita_server: #12,899 on seven-day player hours, top 60% of all ranked servers.

How full does Nikitikita_server get?

Reading for Nikitikita_server: offline at this moment; last seen 12 days 5 hours ago.

Operator and location

Which location does Nikitikita_server run from?

No region comes from 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.173:28015.

What Rust version is Nikitikita_server on?

Rust network protocol 2634 and build 167781 on Windows is the build Nikitikita_server runs. Matching protocol is required to join. Let Steam update your game.

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

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

Settings and map

What rules does Nikitikita_server enforce, and what are its settings?

Check: gather rate. The name Nikitikita_server does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Nikitikita_server?

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

Join

How can you get onto Nikitikita_server?

To join: start Rust, press F1 and type client.connect 178.66.128.173:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.