RUST METRICSFlight deck · live data
Data live Servers11,830 Players89,192 Populated3,733 Fresh wipes 3 h415 Scan5 min
‹ All servers160.251.236.248:28015
Online Full Queue Fresh wipe Wipe due No query

Ninniku_Server

Online 160.251.236.248:28015 checked 9m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Thu 20:00 UTC
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 59 SERVER FPS

Server fps

48 h low 31 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 104,656 ×1000

Entities

48 h range 87,647–104,842 · memory 3,256 MB
1239 ET SINCE RESTART 23:01

Uptime

23 h 1 min since its last restart, at the last reading
7-day average0peak 1
Rank#6,423top 29%
Last wipe28d agono schedule published
Next wipe–too few wipes seen yet
Memory3,256MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75122:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020022:0007:0016:0002:0011:0020:00

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, measured since 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct7 Oct12 Oct18 Oct23 Oct29 Oct

Top 29% 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.

usual gap0.9 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 1 OctThu 1 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 21:17 UTC FW28d ago 1 – running 0
Thu 1 Oct, 00:25 UTC28d ago 1 – 0.9 days 0

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 should you expect from wipe day on Ninniku_Server?

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

What wipe timing does Ninniku_Server follow?

The rhythm of Ninniku_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 28 days ago.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from Ninniku_Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Ninniku_Server appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Ninniku_Server: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does Ninniku_Server hold among Rust servers?

Player hours over seven days put Ninniku_Server at #6,423, in the top 29% of all ranked servers.

What player count does Ninniku_Server carry?

0 of 10 slots are filled on Ninniku_Server right now. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 03:00 UTC, 1 players on average.

Operator and location

Which location does Ninniku_Server run from?

No region tag on Ninniku_Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 160.251.236.248:28015.

What Rust version is Ninniku_Server on?

Reading: Ninniku_Server, Rust network protocol 2635 and build 167781, Linux. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for Ninniku_Server?

Over the last 48 hours the average was 70 server fps; the floor was 31. Check: entities. The peak was 104,842, counting buildings, deployables and the rest of the world. Memory peak: 4,027 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is Ninniku_Server, and is it online now?

Ninniku_Server reports online. Status: normal. Reading: uptime. About 23 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 30 September 2026, recorded by Rust Metrics.

Settings and map

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

Check: gather rate. The name Ninniku_Server does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is Ninniku_Server on?

Check: map. Procedural, size 4,250, seed 818666203, generated by the game on Ninniku_Server. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How can you get onto Ninniku_Server?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs167781
Build Build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.