RUST METRICSFlight deck · live data
Data live Servers11,621 Players32,314 Populated2,788 Fresh wipes 3 h65 Scan5 min
‹ All servers130.49.218.38:28015
Offline Full Queue Fresh wipe Wipe due No query

Nikitikita_server

Offline 130.49.218.38:28015 checked 15d 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#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
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 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

Reset cycle

How often does Nikitikita_server wipe, and when?

To tell the rhythm of Nikitikita_server, too few of its wipes 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 it runs now was made 18 days 13 hours ago.

Tags

How should you read the tags on Nikitikita_server?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167584 (Build): Game build reading: 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from Nikitikita_server. 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.

Player count

Where does Nikitikita_server sit in the rankings?

Ranking for Nikitikita_server: #13,194 on seven-day player hours, top 61% of all ranked servers.

What player count does Nikitikita_server carry?

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

Operator and location

Which location does Nikitikita_server run from?

No region comes from Nikitikita_server. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 130.49.218.38:28015.

What Rust version is Nikitikita_server on?

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

Is Nikitikita_server up, and how often does it stay up?

Nikitikita_server reports offline. The last reading came 15 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 October 2026.

Rules and settings

What settings and rules apply on Nikitikita_server?

Check: gather rate. The name Nikitikita_server does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is Nikitikita_server on?

The game generates a procedural map for Nikitikita_server.

How to join

What do you do to join Nikitikita_server?

To join: start Rust, press F1 and type client.connect 130.49.218.38: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,cs167584,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167584
Build Game build reading: 167584.
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.