RUST METRICSFlight deck · live data
Data live Servers11,781 Players84,091 Populated3,866 Fresh wipes 3 h169 Scan5 min
‹ All servers220.158.23.102:28015
Offline Full Queue Fresh wipe Wipe due No query

JP ShiGu Server PvE

Offline 220.158.23.102:28015 checked 18d ago

monthly wipes vanillaoxidepve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 8 /50

Players now

16% 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#8,782top 40%
Last wipe26d agomonthly schedule
Next wipe8d 3hThu 5 Nov, 19:00 UTC FW
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep25 Sep30 Sep6 Oct11 Oct16 Oct

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

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 3h. The force wipe · high confidence

wipe-day peak50players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 3hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC36d 3hFW

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 50, 18 hours in, with 4 in the queue.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:34 UTC FW26d ago 50+4 queue – running 2

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 happens on JP ShiGu Server PvE when wipe day comes?

An average of 50 players came at the busiest on its recent wipes. 18 hours after the wipe the crowd peaked on the latest wipe, with 4 more in the queue.

How often does JP ShiGu Server PvE wipe, and when?

Once a month JP ShiGu Server PvE wipes, with the force wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 26 days 20 hours ago. Its tags carry a monthly wipe schedule.

Lists and filters

How should you read the tags on JP ShiGu Server PvE?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167058 (Build): Build 167058; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins from JP ShiGu Server PvE. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does JP ShiGu Server PvE appear in Rust Metrics lists and filters?

Rust Metrics lists featuring JP ShiGu Server PvE: Rust community servers: live readings, Rust PvE servers and Vanilla Rust servers, live. These filters bring it up on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Occupancy

What position does JP ShiGu Server PvE hold among Rust servers?

Player hours over seven days put JP ShiGu Server PvE at #8,782, in the top 40% of all ranked servers.

How full does JP ShiGu Server PvE get?

Reading for JP ShiGu Server PvE: offline at this moment; last seen 18 days 19 hours ago.

Operator and location

Which location does JP ShiGu Server PvE run from?

The name of JP ShiGu Server PvE points to Asia, though it publishes no region tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 220.158.23.102:28015.

What Rust version is JP ShiGu Server PvE on?

Rust network protocol 2634 and build 167058 on Linux is the build JP ShiGu Server PvE runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on JP ShiGu Server PvE, and is it online?

Check: connection. JP ShiGu Server PvE is offline at this moment. Last contact was 18 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does JP ShiGu Server PvE enforce, and what are its settings?

Check: gather rate. The name JP ShiGu Server PvE does not state one. The group cap is 8 players, which is the default in the game. The mode is pve. Note the following: no combat against other players. The server browser lists it under Community. Check: plugins. It runs Oxide of them. The server calls itself vanilla, with this meaning: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on JP ShiGu Server PvE?

Check: map. Procedural, size 3,750, seed 174958512, generated by the game on JP ShiGu Server PvE. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

What do you do to join JP ShiGu Server PvE?

Check: join. Open Rust, press F1, then enter client.connect 220.158.23.102:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://discord.com/invite/QBym3xN6pF is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,^m,^v,^p,gmrust,cs167058,ts8,^o

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167058
Build Build 167058.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.

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.