Rust Server TrendsSeismic network · station log
Recording Stations11,647 Players49,596 Active3,216 Wipes · 3 h110 48 h

Station XX-12899 · no signal

Nikitikita_server

Offline 178.66.128.173:28015 checked 11d ago

Connect
Players now
1/ 1
100% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#12,899
top 60%
Last wipe
17d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-12899 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 1 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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 peak
1players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 10 Oct, 15:59 UTC17d ago M0.0steady 1 – running 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 538 on average
472/ 475
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
293/ 225
Rustoria.co - EU Main EU · groups of 16+ · weekly · 316 on average
34/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 315 on average
35/ 250
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 275 on average
147/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 265 on average
62/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Nikitikita_server?

Nikitikita_server uses a procedural map, which the game generates.

Which settings and rules apply on Nikitikita_server?

You will find no gather rate in the name of Nikitikita_server. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on Nikitikita_server?

Nikitikita_server is not responding at this moment and is offline, last seen 11 days 16 hours ago.

How does Nikitikita_server rank against other Rust servers?

The last seven days of player hours place Nikitikita_server at #12,899, in the top 60% of all ranked servers.

Server facts

How reliably does Nikitikita_server stay online?

No contact with Nikitikita_server right now, and the last recorded contact was 11 days 16 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 25 September 2026 is when Rust Server Trends first recorded it.

Which region does Nikitikita_server run from?

Nothing about a region comes from Nikitikita_server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 178.66.128.173:28015.

What build of Rust does Nikitikita_server use?

Rust network protocol 2634 and build 167781 on Windows is what Nikitikita_server runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on Nikitikita_server?

1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 21 hours after the wipe.

How often does Nikitikita_server wipe, and on which days?

The rhythm of Nikitikita_server cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 17 days 17 hours.

Lists and tags

What do the server tags on Nikitikita_server mean?

These are the tags Nikitikita_server publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): The server has 1 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Nikitikita_server appear?

The Rust Server Trends lists that take in Nikitikita_server are: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

How do you connect to Nikitikita_server?

To join, enter client.connect 178.66.128.173:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp1
Max players The server has 1 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167781
Build It runs game build 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.