Rust Server IndexCard catalogue of Rust servers

Holdings11,830 servers81,821 players270 fresh wipes

Call no.6617 On the shelf · online

Ninniku_Server

Online 160.251.236.248:28015 checked 13m ago

Subjects 1. modded2. oxide
Players now
0/ 10
0% full
7-day average
0
peak 1
Rank
#6,617
top 30%
Last wipeWiped1 OCT2026 · 27d 17h ago
27d ago · no schedule published
Next wipe
–
too few wipes seen yet
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
00.250.50.75115:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

05010015020015:0000:0009:0019:0004:0013: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.

Record sheet C · appended

Rank

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

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

Record sheet D · loan terms

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 daysbetween real wipes
wipe-day peak
1players, 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.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
1 OCT 2026Thu 1 Oct, 21:17 UTC FW27d ago
1 – running 0
1 OCT 2026Thu 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

ShockRust | Blue | NoLimitno group limit · 149 on average
182/ 500
EU
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
121/ 100
EU
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 119 on average
108/ 225
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average
75/ 700
EU
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
38/ 200
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 85 on average
246/ 700
Reference desk

Quick answers

From the figures on this page.

Rules and settings

What settings and rules does Ninniku_Server run?

The name of Ninniku_Server does not state a gather rate. The default group limit of 8 players applies. Filed under survival, gather, build and raid: the standard game. PvP and raiding are allowed. The server browser lists it under Modded; plugins or settings alter the game. Plugins in use: Oxide. The server has VAC, Valve's anti-cheat, turned on.

What is the map on Ninniku_Server?

Size 4,250, seed 818666203: the game generates the procedural map on Ninniku_Server. The map can be seen on RustMaps from this page, because the same size and seed give the same map.

Tags

On Rust Server Index, which lists and filters carry Ninniku_Server?

The Rust Server Index lists that include Ninniku_Server are Modded Rust servers, filed by play style. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which tags are attached to Ninniku_Server, and what do they stand for?

These are the tags Ninniku_Server publishes; the game's server browser reads this list: gmrust (Game mode): Rust survival, as standard; mp10 (Max players): The queue ceiling sits at 10; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): Your client must run protocol 2635 to connect; cs167781 (Build): Build on file: 167781; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): A region code is absent; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): This one is Modded, since plugins or settings change how it plays. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.

Wipe schedule

What should you expect on Ninniku_Server when wipe day comes?

The average peak across its recent wipes is 1 players. The latest wipe peaked 5 hours in.

How often is Ninniku_Server wiped, and on what schedule?

Ninniku_Server's rhythm cannot be told yet: too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. Its present world dates from 27 days 17 hours.

Players and ranking

Where does Ninniku_Server sit in the rankings?

On player hours over seven days, Ninniku_Server takes #6,617, within the top 30% of ranked servers.

How many players are on Ninniku_Server at the moment?

The live count for Ninniku_Server stands at 0 players, out of 10 slots. Averaged across seven days: 0 players, peaking at 1. Over the last 48 hours, 20:00 UTC drew the highest average: 1 players.

Operator and status

What Rust version is Ninniku_Server on?

Rust network protocol 2635 and build 167781 on Linux is what you will find on Ninniku_Server. The protocol must match before you can join, and Steam takes care of updating it.

Is Ninniku_Server reachable, and does it stay up?

You will find Ninniku_Server online as of now. The uptime it reports puts the last restart at about 16 hours ago. Of the last 7 full days, 167 of 168 hours were up, 99% of the time. The earliest sighting at Rust Server Index is 30 September 2026.

Is the performance on Ninniku_Server good?

The last 48 hours give an average of 67 server fps and a floor of 31. Buildings, deployables and everything else in the world came to as many as 104,837 entities. Up to 4,027 MB of memory was in use. Lag, to players, is low fps and an entity count that climbs.

What is the location of Ninniku_Server?

There is no region on record for Ninniku_Server; it publishes none. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 160.251.236.248:28015.

Connecting

What steps lead onto Ninniku_Server?

Two ways in. Type client.connect 160.251.236.248:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, as standard.
mp10
Max players The queue ceiling sits at 10.
ts8
Group limit Teams cap at 8, the default setting.
v2635
Protocol Your client must run protocol 2635 to connect.
cs167781
Build Build on file: 167781.
ptrak
Networking RakNet is the network layer, as standard for Rust.
$r?
Region code A region code is absent.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded This one is Modded, since plugins or settings change how it plays.

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.