Station XX-10901 · recording
[Whitelist]nikukyufight
Online 221.170.16.203:28015 checked 9m ago
- Players now
- 0/ 20
- 0% full
- Motion · 24 h
- M0.0▼falling
- −1 players on the day
- 7-day average
- 0
- peak 3
- Rank
- #10,901
- top 49%
- Last wipe
- 12h ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 20 slots
- Motion · 24 h
- M0.0▼falling−1 players
- Sharpest hour
- −1into Thu 13:00 UTC
- Peak · 48 h
- 3most players in any hour
- Events picked
- 1wipe on this record, in red
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 27 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 49% 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
- 1.9 daysbetween real wipes
- wipe-day peak
- 3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 45 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 29 Oct, 12:30 UTC17h ago | – | – | – | – | running | 3 |
| Tue 27 Oct, 15:20 UTC2d ago | M0.5▲rising | 3 | – | 1.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 [Whitelist]nikukyufight?
The procedural map on [Whitelist]nikukyufight is size 4,000 with seed 1975682828, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on [Whitelist]nikukyufight?
No gather rate appears in the name of [Whitelist]nikukyufight. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on [Whitelist]nikukyufight right now?
At this moment, [Whitelist]nikukyufight records 0 players across 20 slots. Across seven days this server recorded an average of 0 players and a peak of 3. The last 48 hours show their highest activity at 12:00 UTC, averaging 1 players.
How does [Whitelist]nikukyufight rank against other Rust servers?
On player hours for the past week, [Whitelist]nikukyufight sits at #10,901, which puts it inside the top 49% of every ranked server.
Operator and location
How reliably does [Whitelist]nikukyufight stay online?
Right now, you can reach [Whitelist]nikukyufight. Going by the uptime figure it reports, it restarted about 11 hours ago. Of the 48 hours in the last 2 full days, it was up for 12, or 25% of the time. On 27 October 2026 it was recorded for the first time by Rust Server Trends.
How well does [Whitelist]nikukyufight perform under load?
The 48-hour average is 148 server fps; 64 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 204,620. Its highest memory use was 3,322 MB. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is [Whitelist]nikukyufight hosted?
A region is not published by [Whitelist]nikukyufight. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 221.170.16.203:28015 is the address it uses.
What build of Rust does [Whitelist]nikukyufight use?
[Whitelist]nikukyufight is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on [Whitelist]nikukyufight?
3 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 45 hours after the wipe.
On what timetable does [Whitelist]nikukyufight run its wipes?
On record so far are too few of [Whitelist]nikukyufight's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 12 hours is how long the current world has been running.
Server tags
What do the server tags on [Whitelist]nikukyufight mean?
Tags published by [Whitelist]nikukyufight and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): 20 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does [Whitelist]nikukyufight appear?
These Rust Server Trends lists include [Whitelist]nikukyufight: Modded Rust servers, tracked live. 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 24 hours.
How to join
What steps get you onto [Whitelist]nikukyufight?
You can connect by pressing F1 in Rust and typing client.connect 221.170.16.203:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects 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.