StatusLive Servers online11,869 Players90,153 Populated3,832 Wiped · 3 h374 Interval5 min Date29 OCT 2026

DWG RG-S4779Server sheetchecked 8m ago

[JP] PVE テスト用サーバー 入場自由

Online 162.43.38.195:28015 checked 8m ago

moddedoxidepve
Connect
Players now 1/ 15 7% full
7-day average0peak 3
Rank#4,779top 21%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.511.5216:0001:0010:0019:0004:0013:00

Hourly average and peak, UTC.

Fig. 1Players on [JP] PVE テスト用サーバー 入場自由
Fig. 2

Server performance

05010015020016:0001:0010:0019:0004:0013: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap2.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 1 OctSun 27 SepSat 26 Sep
00.511.52+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 2, 21 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 17:58 UTC FW27d ago 2 – running 0
Sun 27 Sep, 16:13 UTC31d ago 1 held half 4.1 days 1
Sat 26 Sep, 13:54 UTC33d ago 1 – 1.1 days 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 58 on average
74 / 200
02
QS『鱼山路』pve|耐玩|升级|突袭EA · groups of 8+ · 37 on average
8 / 100
03
[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本EA · groups of 8+ · monthly · 35 on average
39 / 100
04
Japan Tokyo - Vanilla PvE|JP|BeginnerEA · groups of 16+ · 33 on average
62 / 100
05
Japan Tokyo - Chill PvE|JPEA · groups of 16+ · 21 on average
22 / 100
06
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average
19 / 88
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is [JP] PVE テスト用サーバー 入場自由 online, and what uptime has been recorded?

At this moment [JP] PVE テスト用サーバー 入場自由 is online. The uptime it reports puts the last restart at about 3 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.

Is [JP] PVE テスト用サーバー 入場自由 stable in the figures recorded?

110 server fps on average over the last 48 hours, and never under 67. Counted at its highest: 85,429 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 2,924 MB. Players feel low fps and a climbing entity count as lag.

In which location is [JP] PVE テスト用サーバー 入場自由 hosted?

Its name points to Asia, though [JP] PVE テスト用サーバー 入場自由 publishes no region tag. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 162.43.38.195:28015 is its address.

What Rust version is recorded for [JP] PVE テスト用サーバー 入場自由?

On Linux, [JP] PVE テスト用サーバー 入場自由 runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles the update.

Population

What does the population history show for [JP] PVE テスト用サーバー 入場自由?

1 of 15 slots on [JP] PVE テスト用サーバー 入場自由 are taken at the latest refresh. The seven-day mean is 0 players; the peak over the same period is 3. Averaged over the last 48 hours, the player count is highest at 08:00 UTC: 1 players.

Against other Rust servers, where is [JP] PVE テスト用サーバー 入場自由 placed?

Player hours over seven days place [JP] PVE テスト用サーバー 入場自由 at #4,779, within the top 21% of ranked servers.

Schedules

What is recorded on [JP] PVE テスト用サーバー 入場自由 on wipe day?

The recent wipes averaged a busiest count of 1 players. 21 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.

What wipe schedule has been recorded for [JP] PVE テスト用サーバー 入場自由?

No next wipe can be predicted for [JP] PVE テスト用サーバー 入場自由: its wipes fall at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 27 days 17 hours ago the current world was made.

Settings

Which rules and settings are recorded for [JP] PVE テスト用サーバー 入場自由?

No gather rate is stated in the name of [JP] PVE テスト用サーバー 入場自由. The group limit is 8 players, the game's default. pve, no fighting other players, is the game mode. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.

On which map is [JP] PVE テスト用サーバー 入場自由 played?

[JP] PVE テスト用サーバー 入場自由 runs a procedural map of size 3,500 with seed 1573025114, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The map is named as follows: Custom Map.

Tags

On Rust Graphs, which lists and filters contain [JP] PVE テスト用サーバー 入場自由?

The Rust Graphs lists that carry [JP] PVE テスト用サーバー 入場自由 are: Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

On [JP] PVE テスト用サーバー 入場自由, what is meant by each tag?

gmrust (Game mode): Survival in standard Rust style; mp15 (Max players): Slots: 15; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^p (PvE): Player fights are off; the world supplies the danger; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; modded (Modded): The game is changed by plugins or settings; the listing is Modded are the tags [JP] PVE テスト用サーバー 入場自由 publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Connect

What is the way to connect to [JP] PVE テスト用サーバー 入場自由?

Enter client.connect 162.43.38.195:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://note.com/7010_rust is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp15,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z,modded

Game

gmrust
Game mode Survival in standard Rust style.
mp15
Max players Slots: 15.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build 168909 is the game build.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

Gameplay

^p
PvE Player fights are off; the world supplies the danger.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.
modded
Modded The game is changed by plugins or settings; the listing is Modded.

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.

KeyTag string decoded