RUST METRICSFlight deck · live data
Data live Servers11,768 Players60,085 Populated3,517 Fresh wipes 3 h135 Scan5 min
‹ All servers176.98.202.61:28015
Offline Full Queue Fresh wipe Wipe due No query

KIBA pvp/pve zone x1

Offline 176.98.202.61:28015 checked 27m ago

1x vanillamoddedoxide
COM 1 · connect

Server instruments

last reading Wed 21:00 UTC
0 75 150 225 300 PAX 0 /300

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 236 SERVER FPS

Server fps

48 h low 202 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 43,270 ×1000

Entities

48 h range 43,206–45,311 · memory 2,923 MB
1239 ET SINCE RESTART 2D 06H

Uptime

2 days 6 hours since its last restart, at the last reading
7-day average0peak 1
Rank#9,635top 43%
Last wipe11d agono schedule published
Next wipe–too few wipes seen yet
Memory2,923MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75123:0008:0017:0001:0010:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040023:0008:0017:0001:0010:0021: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 10 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k8 Oct12 Oct16 Oct20 Oct24 Oct28 Oct

Top 43% of all ranked servers. Ranked on player hours over the last seven days.

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.

usual gap4.9 daysbetween real wipes
wipe-day peak4players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sat 17 OctMon 12 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 27 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 11:59 UTC11d ago 4 – running 0
Mon 12 Oct, 14:59 UTC16d ago 4 held half 4.9 days 1

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 schedule

What happens on KIBA pvp/pve zone x1 when wipe day comes?

The busiest point of its recent wipes drew 4 players on average. Peak crowd on the latest wipe: 27 hours in. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.

What wipe timing does KIBA pvp/pve zone x1 follow?

To tell the rhythm of KIBA pvp/pve zone x1, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 11 days 9 hours ago the current world was made.

Lists and filters

How should you read the tags on KIBA pvp/pve zone x1?

These are the tags KIBA pvp/pve zone x1 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp300 (Max players): The server holds 300 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show KIBA pvp/pve zone x1?

On Rust Metrics, KIBA pvp/pve zone x1 sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 1x.

Occupancy

Where does KIBA pvp/pve zone x1 sit in the rankings?

Player hours over seven days put KIBA pvp/pve zone x1 at #9,635, in the top 43% of all ranked servers.

How full does KIBA pvp/pve zone x1 get?

Reading for KIBA pvp/pve zone x1: offline at this moment; last seen 27 minutes ago. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 09:00 UTC, averaging 1 players at that hour.

Server

Which location does KIBA pvp/pve zone x1 run from?

No region comes from KIBA pvp/pve zone x1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 176.98.202.61:28015.

What Rust version is KIBA pvp/pve zone x1 on?

Rust network protocol 2635 and build 168909 on Windows is the build KIBA pvp/pve zone x1 runs. Matching protocol is required to join. Let Steam update your game.

How does KIBA pvp/pve zone x1 perform?

Reading: 235 server fps on average across the last 48 hours. It never dropped below 202. Peak entity count: 45,311. Buildings, deployables and all else included. Check: memory. Peak use was 3,116 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is KIBA pvp/pve zone x1, and is it online now?

KIBA pvp/pve zone x1 reports offline. The last reading came 27 minutes ago. By its reported uptime, the last restart was roughly 2 days 6 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 8 October 2026.

Rules and settings

What rules does KIBA pvp/pve zone x1 enforce, and what are its settings?

The name carries the rate: 1x gather on KIBA pvp/pve zone x1. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. The server calls itself vanilla, with this meaning: rates, kits and rules are exactly as Facepunch ships them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on KIBA pvp/pve zone x1?

Check: map. Procedural, size 3,000, seed 17102026, generated by the game on KIBA pvp/pve zone x1. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto KIBA pvp/pve zone x1?

Check: join. Open Rust, press F1, then enter client.connect 176.98.202.61:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp300
Max players The server holds 300 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Difficulty

^v
Vanilla Rates, kits and rules are exactly as Facepunch ships them.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.