Skip to the page
RUST ANALYTICS
LIVE32,798PLY11,453SRV
QUOTE 160.251.236.248:28015 Online checked 12m ago

Ninniku_Server

moddedoxide
Players · last
0/ 10
+024h
0% full
Day range 0 1
7-day avg 0 peak 1
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 10
0% full
Change · 24h
+0
no reading a day ago
7-day average
0
peak 1
Rank
#5,687
top 26%
Rank · 7d ago
#5,318
369 places down
Last wipe
13d ago
no schedule published
Next wipe
–
too few wipes seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
34
player hours, last seven days
Map
4250
Procedural Map · seed 818666203
First seen
30 Sep 2026
no hostname published

Players

AveragePeak
00.250.50.75106:0015:0000:0009:0018:0003:00

Hourly average and peak, UTC. Busiest hour of the two days: 1 players.

Server performance

02040608006:0015:0000:0009:0018:0003: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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct4 Oct7 Oct9 Oct12 Oct15 Oct

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

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 gap
0.9 days
between real wipes
wipe-day peak
1
players, 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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 21:17 UTC FW13d ago 1 – running 0
Thu 1 Oct, 00:25 UTC14d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1ShockRust | Blue | NoLimitno group limit · 129 on average24/300−29−55.0%
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 109 on average26/225−17−39.5%
3МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average89/100−2−1.7%
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 87 on average3/1000−12−79.5%
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 75 on average0/1000−6−100.0%
6404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average5/700−9−64.7%

Quick answers

from the figures on this page

Server Rules

How is Ninniku_Server configured in terms of rules and settings?

No gather rate appears in the name of Ninniku_Server. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are in use. VAC, Valve's anti-cheat, is enabled.

What is the current map on Ninniku_Server?

Ninniku_Server uses a procedural map of size 4,250 with seed 818666203, generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.

Player Count

What position does Ninniku_Server hold in the server rankings?

In the top 26% of all ranked servers, Ninniku_Server is #5,687 on player hours over the last seven days.

What is the population on Ninniku_Server?

0 of 10 slots on Ninniku_Server are filled right now. Average players over seven days: 0; peak: 1. The busiest hour in the last 48 hours was 08:00 UTC, with an average of 1 players.

Wipe Frequency

How does Ninniku_Server handle wipe day?

Recent wipes at this server drew an average peak of 1 players. On the latest wipe, 5 hours after the wipe, the crowd peaked.

When does Ninniku_Server schedule its wipes?

The record holds too few of Ninniku_Server's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 13 days 7 hours ago the current world was created.

Server Details

Where can Ninniku_Server be found?

There is no region published for Ninniku_Server. Rust Analytics reports the location a server claims, not the machine's actual location. 160.251.236.248:28015 is its address.

How is the performance on Ninniku_Server?

Average server fps for the last 48 hours is 49; the floor was 27. At its peak it held 111,003 entities: buildings, deployables and the rest of the world. The memory ceiling reached 3,958 MB. Low fps and growing entities are the source of felt lag.

Ninniku_Server runs which version of Rust?

Rust network protocol 2634 and build 166494 on Linux is what Ninniku_Server runs. Joining requires the same protocol on your game, which Steam updates.

What is the uptime and reliability of Ninniku_Server?

Ninniku_Server is up. It is taking players now. The reported uptime puts its last restart at about 11 hours ago. 7 full days have passed with 100% uptime, 168 of 168 hours. 30 September 2026 is when Rust Analytics first saw it.

Tags and Rankings

What is the meaning of the tags on Ninniku_Server?

The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp10 (Max players): Slot count: 10; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166494 (Build): Build 166494; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): Region code: none set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which Ninniku_Server publishes. The top of this page and the tags both show its players now, its queue and when its world was made.

Where does Ninniku_Server show up in Rust Analytics lists and filters?

These Rust Analytics lists include Ninniku_Server: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How to Join

What steps do I take to join Ninniku_Server?

Type client.connect 160.251.236.248:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode Rust's standard survival mode.
mp10
Max players Slot count: 10.
ts8
Group limit At the game default, teams hold up to 8.
v2634
Protocol Your game must run protocol 2634 to connect.
cs166494
Build Build 166494.
ptrak
Networking RakNet, the network layer the game ships with.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

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.