Rust Data

rustdata.spaceservers220.158.23.102:29015.ipynb

Run all rust-data · live

‹ All servers

Offline 220.158.23.102:28015 checked 19d ago

JP ShiGu Server PvE

monthly wipes vanillaoxidepve

Connect

srv = rust.server("220.158.23.102:29015")
print(srv.connect_command)

Right now

srv.summary()
players now 8/50 # 16% full
7-day average 0 # peak –
rank #8,782 # top 40%
last wipe 28d ago # monthly schedule
next wipe 6d 23h # Thu 5 Nov, 19:00 UTC FW
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h. # The force wipe · high confidence

wipe-day peak50players, last three wipes

Coming wipes

inatkind
06d 23hThu 5 Nov, 19:00 UTCFW force wipe
134d 23hThu 3 Dec, 19:00 UTCFW force wipe

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 18:34 UTC FW28d ago 50+4 queue NaN 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.

display(srv.map, srv.info())

Map

3750 · seed 174958512
Map of JP ShiGu Server PvE
map
Procedural Map
size
3750
seed
174958512
Open on RustMaps

Server

srv.info()
address
220.158.23.102:28015
region
–
max players
50
group limit
8, the default
wipe schedule
monthly
last wipe
1 Oct 2026, 18:34 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
【お知らせ】この鯖はPVEですが建築などの理由により鯖主の意向で設定がPVPになっております。 レイドなどの荒らしがあるかもしれませんので拠点はできるだけ石以上にすることをお勧めします。 詳しくは鯖の説明欄を読んでください。(discordもあります)

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍EA · groups of 30+ · monthly · 22 on average10/200
1[SEA] RustEZ Pure PvE | Low Decay | No Killing | No RaidingEA · groups of 8+ · monthly · 17 on average12/200
2JP RustPvE kokuu Server No kill No raid beeginnerEA · groups of 8+ · monthly · 15 on average5/200
3Kiyo Server JP PVEEA · groups of 20+ · monthly · 5 on average2/30
4[SEA] tRust SG PvE Monthly VanillaEA · groups of 8+ · monthly · 5 on average2/50
5【旧梦PVE】 萌新学习 | 原版养老 | 禁抄家打架EA · groups of 15+ · monthly · 5 on average3/100

Quick answers

From the figures on this page.

Population

What position does JP ShiGu Server PvE take in the server rankings?

Rank #8,782 on seven-day player hours for JP ShiGu Server PvE, within the top 40% of all ranked servers.

How full does JP ShiGu Server PvE run?

Offline now for JP ShiGu Server PvE, with the last sample 19 days 23 hours ago.

About the server

What Rust version does JP ShiGu Server PvE run?

The build is Rust network protocol 2634 and build 167058 on Linux, run by JP ShiGu Server PvE. The protocol has to match before you can join, and Steam does the updating.

How reliable is JP ShiGu Server PvE, and is it up?

The latest sample has JP ShiGu Server PvE offline, with a last sighting 19 days 23 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is JP ShiGu Server PvE hosted?

The name of JP ShiGu Server PvE points to Asia, even though no region tag is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 220.158.23.102:28015 is its address.

Rules, settings, map

Which rules apply on JP ShiGu Server PvE, and what settings?

The name JP ShiGu Server PvE carries no gather rate. The group limit sits at the default of 8 players. Recorded as pve, player combat is not allowed. The server browser lists it under Community. Plugins installed: Oxide. The description says vanilla, which here means untouched settings: rates, kits and rules as shipped. VAC, Valve's anti-cheat, is enabled.

What is the map on JP ShiGu Server PvE?

Size 3,750, seed 174958512: the procedural map on JP ShiGu Server PvE, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe schedule

On what schedule does JP ShiGu Server PvE wipe?

Once a month JP ShiGu Server PvE wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 28 days ago, and that is the one in play. Its tags carry a monthly wipe schedule.

On JP ShiGu Server PvE, what happens on wipe day?

Across recent wipes the busiest point averaged 50 players. A peak 18 hours into the latest wipe, plus 4 waiting in the queue.

Tags, lists

Which Rust Data filters and lists contain JP ShiGu Server PvE?

These Rust Data lists include JP ShiGu Server PvE: Rust community servers, unfiltered, Rust PvE servers and Vanilla Rust servers. It appears under these filters 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.

Which meanings do the tags on JP ShiGu Server PvE hold?

The game's server browser reads these tags from JP ShiGu Server PvE: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): Recorded game build: 167058; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod). At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

How can I connect to JP ShiGu Server PvE?

The manual route: launch Rust, F1, then client.connect 220.158.23.102:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. You will find its website at https://discord.com/invite/QBym3xN6pF.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players 50 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167058
Build Recorded game build: 167058.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Wipe schedule

^m
Monthly Monthly: the wipe lands with Facepunch's force wipe.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

Gameplay

^p
PvE No player-versus-player combat; the danger comes from the world.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

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 103,409 players 11,892 servers online