Rust Data

rustdata.spaceservers160.251.236.248:28017.ipynb

Run all rust-data · live

‹ All servers

Online 160.251.236.248:28015 checked 10m ago

Ninniku_Server

moddedoxide

Connect

srv = rust.server("160.251.236.248:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 1
rank #6,617 # top 30%
last wipe 27d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75115:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 21:17 UTC FW27d ago 1 NaN running 0
1 Thu 1 Oct, 00:25 UTC28d ago 1 NaN 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.

display(srv.map, srv.info())

Map

4250 · seed 818666203
Map of Ninniku_Server
map
Procedural Map
size
4250
seed
818666203
Open on RustMaps

Server

srv.info()
address
160.251.236.248:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 21:17 UTC
hostname
–
first seen
30 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 149 on average182/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average121/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 119 on average108/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average75/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average38/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 85 on average246/700

Quick answers

From the figures on this page.

Population

What position does Ninniku_Server take in the server rankings?

Player hours over seven days put Ninniku_Server at #6,617, in the top 30% of the ranked set.

How many players does Ninniku_Server hold at once?

The sample now reads 0 players for Ninniku_Server, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 20:00 UTC is the busiest, at 1 players.

About the server

How well does Ninniku_Server perform?

The 48-hour average is 67 server fps, with a low of 31. The entity count peaked at 104,837, covering buildings, deployables and the rest of the world. The memory field tops out at 4,027 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is Ninniku_Server on?

The build is Rust network protocol 2635 and build 167781 on Linux, run by Ninniku_Server. Steam updates your game for you, but the protocol must match to join.

How reliable is Ninniku_Server, and is it up?

The current sample puts Ninniku_Server online. The uptime it reports puts the last restart about 16 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 30 September 2026.

Where does Ninniku_Server sit?

There is no region published for Ninniku_Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 160.251.236.248:28015 is its address.

Settings and map

Which settings and rules does Ninniku_Server run?

No gather rate appears in the name: Ninniku_Server. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

What is the map on Ninniku_Server?

Size 4,250, seed 818666203: the procedural map on Ninniku_Server, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does Ninniku_Server wipe, and on what schedule?

Too few wipes are on record for Ninniku_Server to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 27 days 17 hours ago.

What is wipe day on Ninniku_Server like?

Recent wipes averaged 1 players at their peak. 5 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Where does Ninniku_Server appear among Rust Data lists and filters?

The Rust Data lists that Ninniku_Server fits are: 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.

Which meanings do the tags on Ninniku_Server hold?

Read by the game's server browser, the tags Ninniku_Server publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

How can I connect to Ninniku_Server?

Enter client.connect 160.251.236.248:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs167781
Build Recorded game build: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 81,821 players 11,830 servers online