Rust Data

rustdata.spaceservers221.170.16.203:28017.ipynb

Run all rust-data · live

‹ All servers

Online 221.170.16.203:28015 checked 12m ago

[Whitelist]nikukyufight

moddedoxide

Connect

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

Right now

srv.summary()
players now 0/20 # 0% full
7-day average 0 # peak 3
rank #10,866 # top 49%
last wipe 7h ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeakWipe
0123412:0014:0016:0018:0020:0022:00Wiped Thu 29 Oct, 16:56 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
010020030040012:0014:0016:0018:0020:0022:00Wiped Thu 29 Oct, 16:56 UTCWIPE

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 best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k27 Oct28 Oct29 Oct

Top 49% 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 gap1.9 daysbetween real wipes
wipe-day peak3players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 45 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 29 Oct, 12:30 UTC11h ago NaN NaN running 3
1 Tue 27 Oct, 15:20 UTC2d ago 3 NaN 1.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

4000 · seed 1975682828
Map of [Whitelist]nikukyufight
map
Procedural Map
size
4000
seed
1975682828
Open on RustMaps

Server

srv.info()
address
221.170.16.203:28015
region
–
max players
20
group limit
8, the default
wipe schedule
–
last wipe
29 Oct 2026, 16:56 UTC
hostname
–
first seen
27 Oct 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 average29/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average120/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 120 on average50/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average16/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 93 on average52/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average231/260

Quick answers

From the figures on this page.

Population

What position does [Whitelist]nikukyufight take in the server rankings?

Player hours over seven days put [Whitelist]nikukyufight at #10,866, in the top 49% of the ranked set.

What population does [Whitelist]nikukyufight carry?

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

Server data

What does performance look like on [Whitelist]nikukyufight?

The 48-hour average is 143 server fps, with a low of 64. Buildings, deployables and all else in the world took the count as high as 204,620 entities. Memory peaked at 3,322 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does [Whitelist]nikukyufight run?

The build is Rust network protocol 2635 and build 168909 on Windows, run by [Whitelist]nikukyufight. Joining needs the same protocol on your game; Steam handles the update.

Is [Whitelist]nikukyufight up, and what does its uptime show?

[Whitelist]nikukyufight reports itself online at the current refresh. A restart about 5 hours ago is what its reported uptime implies. Over the last 1 full day the hours up number 0 of 24, 0%. Its earliest recorded date in Rust Data is 27 October 2026.

In which location is [Whitelist]nikukyufight hosted?

For [Whitelist]nikukyufight, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 221.170.16.203:28015 is its address.

Rules, settings, map

Which rules apply on [Whitelist]nikukyufight, and what settings?

The name [Whitelist]nikukyufight carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.

Which map has [Whitelist]nikukyufight loaded?

Size 4,000, seed 1975682828: the procedural map on [Whitelist]nikukyufight, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

On what schedule does [Whitelist]nikukyufight wipe?

Too few wipes are on record for [Whitelist]nikukyufight 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 7 hours ago.

On [Whitelist]nikukyufight, what happens on wipe day?

The average peak over recent wipes is 3 players. The crowd on the latest wipe topped out 45 hours after it began.

Tags and filters

Which lists on Rust Data hold [Whitelist]nikukyufight, and which filters?

On Rust Data, [Whitelist]nikukyufight appears in these lists: Modded Rust servers. It appears under these filters 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 should you read the server tags on [Whitelist]nikukyufight?

The game's server browser reads these tags from [Whitelist]nikukyufight: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^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.

How to join

What is the way to join [Whitelist]nikukyufight?

The manual route: launch Rust, F1, then client.connect 221.170.16.203:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp20,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp20
Max players The server lists 20 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^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 65,070 players 11,731 servers online