Working its way up from the back of the class: #8,782 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
4/ 100
F
Lost ground: down 8,000 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (C); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 40% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h.
The force wipe · high confidence
wipe-day peak50players, last three wipes
Coming wipes
6d 20hThu 5 Nov, 19:00 UTCFW
34d 20hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
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
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:34 UTCFW28d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
The name of JP ShiGu Server PvE points to Asia, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 220.158.23.102:28015.
How dependable is JP ShiGu Server PvE, and is it online at the moment?
The server is down: JP ShiGu Server PvE is offline now, with the last sighting 20 days 2 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
What Rust version is JP ShiGu Server PvE on?
Rust network protocol 2634 and build 167058 on Linux is what JP ShiGu Server PvE runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does JP ShiGu Server PvE wipe, and how often?
JP ShiGu Server PvE wipes with the force wipe and at no other time. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 28 days 3 hours. Its tags record that it wipes monthly.
What happens on JP ShiGu Server PvE when wipe day arrives?
Across its recent wipes, the busiest moments averaged 50 players. The latest wipe peaked 18 hours in, with 4 more players queued at that point.
Player count
Where does JP ShiGu Server PvE place in the wider field of Rust servers?
Over the last seven days, JP ShiGu Server PvE has #8,782 for player hours, in the top 40% of all ranked servers.
How many players does JP ShiGu Server PvE usually have?
The last sighting of JP ShiGu Server PvE was 20 days 2 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on JP ShiGu Server PvE?
The game's browser takes its cue from the tags JP ShiGu Server PvE has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs167058 (Build): This runs on build 167058; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): The plugin framework in use is Oxide (uMod). Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does JP ShiGu Server PvE appear in the Rust Server Score lists and filters?
Rust Server Score lists that include JP ShiGu Server PvE: Best community servers, graded, Rust PvE servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: 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.
Map and rules
How is JP ShiGu Server PvE set up, and what rules does it keep?
The name of JP ShiGu Server PvE gives no gather rate. The default of 8 players applies as the group cap. You get pve here, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. The plugin count runs to Oxide. Vanilla is what it calls itself: facepunch's own version, with no changed rates, kits or rules. VAC, Valve's anti-cheat, is enabled.
Which map is in play on JP ShiGu Server PvE?
A procedural map of size 3,750 and seed 174958512, generated by the game, is what JP ShiGu Server PvE runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
What is the way to join JP ShiGu Server PvE?
Enter client.connect 220.158.23.102:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/QBym3xN6pF.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^m,^v,^p,gmrust,cs167058,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167058
BuildThis runs on build 167058.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxideThe plugin framework in use is 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.
A term to build on. Strongest in standing (C); momentum is the one to work on (F).