RUST METRICSFlight deck · live data
Data live Servers11,694 Players52,148 Populated3,104 Fresh wipes 3 h109 Scan5 min
‹ All servers202.226.243.14:28015
Offline Full Queue Fresh wipe Wipe due No query

Nishida

Offline 202.226.243.14:28015 checked 39d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 0 /15

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,516no region published
Last wipe39d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance
This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
PLAN

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.

wipe-day peak1players, 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 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 20 Sep, 05:05 UTC39d ago 1 – running 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on Nishida?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

How often does Nishida wipe, and when?

The rhythm of Nishida's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 39 days 20 hours ago.

Tags

How should you read the tags on Nishida?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp15 (Max players): The server holds 15 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Nishida. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Nishida appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Nishida: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does Nishida hold among Rust servers?

Ranking for Nishida: #15,516 on seven-day player hours, top – of all ranked servers.

How full does Nishida get?

Reading for Nishida: offline at this moment; last seen 39 days 14 hours ago.

Operator and location

What location is Nishida hosted in?

Reading: location. Nishida gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 202.226.243.14:28015.

What Rust version is Nishida on?

Reading: Nishida, Rust network protocol 2633 and build 164530, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Nishida, and is it online now?

Nishida reports offline. The last reading came 39 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 19 September 2026.

Settings and map

What settings and rules apply on Nishida?

Check: gather rate. The name Nishida does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Nishida?

Check: map. Procedural, generated by the game, on Nishida.

How to join

How do you connect to Nishida?

To join: start Rust, press F1 and type client.connect 202.226.243.14:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2633,gmvanilla,cs164530,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp15
Max players The server holds 15 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build Build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.