Station XX-6442 · recording
Ninniku_Server
Online 160.251.236.248:28015 checked 9m ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #6,442
- top 29%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −1into Thu 06:00 UTC
- Peak · 48 h
- 1most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 29% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot 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
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 21:17 UTC FW27d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 1 Oct, 00:25 UTC28d ago | M0.0▲rising | 1 | – | 0.9 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on Ninniku_Server?
Ninniku_Server runs a procedural map of size 4,250 with seed 818666203, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on Ninniku_Server?
The name of Ninniku_Server gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on Ninniku_Server right now?
A reading taken now shows 0 players on Ninniku_Server, which has 10 slots. Across seven days this server recorded an average of 0 players and a peak of 1. The last 48 hours show their highest activity at 20:00 UTC, averaging 1 players.
How does Ninniku_Server rank against other Rust servers?
Over the last seven days, Ninniku_Server recorded enough player hours to reach #6,442 worldwide, placing it in the top 29% of all ranked servers.
Server facts
How reliably does Ninniku_Server stay online?
As recorded now, Ninniku_Server is running. The uptime it reports puts its last restart about 20 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. 30 September 2026 is when Rust Server Trends first recorded it.
How well does Ninniku_Server perform under load?
Its average server fps over the last 48 hours was 69, and it never dropped below 31. Buildings, deployables and all the rest of the world's entities brought it to a high of 104,842. Memory use peaked at 4,027 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does Ninniku_Server run from?
A region is not published by Ninniku_Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 160.251.236.248:28015.
What build of Rust does Ninniku_Server use?
On Linux, Ninniku_Server runs Rust network protocol 2635 and build 167781. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Ninniku_Server?
1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 5 hours after the wipe.
How often does Ninniku_Server wipe, and on which days?
On record so far are too few of Ninniku_Server's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 27 days 21 hours is how long the current world has been running.
Lists and tags
What do the server tags on Ninniku_Server mean?
The game's server browser reads the tags Ninniku_Server publishes: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs167781 (Build): It runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Ninniku_Server appear?
You will find Ninniku_Server on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
What steps get you onto Ninniku_Server?
To join, enter client.connect 160.251.236.248:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.