Rust Server Analytics 66,169 players11,766 servers
All servers
Drill-through Server detail

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

Online 162.43.38.195:28015 checked 9m ago

Drill-through
FilterServeris [JP] PVE テスト用サーバー 入場自由
Attributes
moddedoxidepve
Last refreshed
Players now 0/ 15
7-day average 0 peak 3
Rank #4,827 top 22%
Last wipe 27d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
00.511.5213:0022:0007:0015:0001:0010:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
05010015020013:0022:0007:0015:0001:0010: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.

Rank

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

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

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

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

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 UTC32d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 58 on average 101 / 200
QS『鱼山路』pve|耐玩|升级|突袭 EA · groups of 8+ · 37 on average 46 / 100
[坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖 EA · groups of 8+ · monthly · 35 on average 40 / 100
Japan Tokyo - Vanilla PvE|JP|Beginner EA · groups of 16+ · 33 on average 56 / 100
Japan Tokyo - Chill PvE|JP EA · groups of 16+ · 21 on average 34 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 20 on average 22 / 88

Quick answers

from the figures on this page

Wipe cycle

On what cycle does [JP] PVE テスト用サーバー 入場自由 wipe?

The next wipe on [JP] PVE テスト用サーバー 入場自由 cannot be predicted, because it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. The current world dates from 27 days 14 hours.

On [JP] PVE テスト用サーバー 入場自由, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. 21 hours after the latest wipe the crowd peaked. Above half that peak until the next wipe held in 100% of recent wipes.

Server

Which location hosts [JP] PVE テスト用サーバー 入場自由?

No region tag is published by [JP] PVE テスト用サーバー 入場自由, but the name points to Asia. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 162.43.38.195:28015.

What Rust build does [JP] PVE テスト用サーバー 入場自由 run?

Rust network protocol 2635 and build 168909 on Linux is the setup for [JP] PVE テスト用サーバー 入場自由. Joining requires the same protocol on your game; Steam handles the update.

How reliable is [JP] PVE テスト用サーバー 入場自由, and is it online now?

[JP] PVE テスト用サーバー 入場自由 reports online at the current check. The uptime it reports puts the last restart at about 28 minutes ago. Of 168 hours in the last 7 full days, 167 were up: 99%. 13 September 2026 is when Rust Server Analytics first recorded it.

Is performance on [JP] PVE テスト用サーバー 入場自由 stable?

Over 48 hours the average held at 109 server fps, and the minimum was 67. At its highest the entity count was 84,593, including buildings, deployables and all else. At its highest, memory use was 2,924 MB. A climbing entity count and low fps are the lag players perceive.

Lists and tags

What do [JP] PVE テスト用サーバー 入場自由's tags stand for?

Tags from [JP] PVE テスト用サーバー 入場自由, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp15 (Max players): Player slots: 15; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Game build: 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^p (PvE): No fighting between players, with the world as the threat; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): Plugins or settings change the game, so it sits under Modded; modded (Modded): Plugins or settings change the game, so it sits under Modded. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

Where does [JP] PVE テスト用サーバー 入場自由 appear across Rust Server Analytics's lists and filters?

Among the Rust Server Analytics lists [JP] PVE テスト用サーバー 入場自由 fits are: Modded Rust servers: live data and PvE Rust servers by live population. On the server list, the filters that return it are: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Player numbers

Against other Rust servers, how does [JP] PVE テスト用サーバー 入場自由 compare?

Player hours for the last seven days place [JP] PVE テスト用サーバー 入場自由 at #4,827, in the top 22% of the ranked field.

At what level does [JP] PVE テスト用サーバー 入場自由 run its population?

Population at the current refresh: 0 players on [JP] PVE テスト用サーバー 入場自由, against 15 slots. The seven-day mean is 0 players, against a peak of 3. The 48-hour peak window is 08:00 UTC, at an average of 1 players.

Map and rules

What are the settings on [JP] PVE テスト用サーバー 入場自由, and its rules?

Gather rate is not mentioned in the name of [JP] PVE テスト用サーバー 入場自由. No custom group limit: 8 players is the standard. pve is the game mode, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. VAC, Valve's anti-cheat, is enabled.

What is the map for [JP] PVE テスト用サーバー 入場自由?

The game generates a procedural map of size 3,500 with seed 1573025114 for [JP] PVE テスト用サーバー 入場自由. Because size and seed determine the map, it can be viewed on RustMaps via this page. The map is called Custom Map.

Connection

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

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 162.43.38.195:28015. https://note.com/7010_rust is its website.

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 the standard Rust format.
mp15
Max players Player slots: 15.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build Game build: 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code A region code is not set.

Gameplay

^p
PvE No fighting between players, with the world as the threat.

Mods and access

^o
Oxide It runs Oxide (uMod) for plugins.
^z
Modded Plugins or settings change the game, so it sits under Modded.
modded
Modded Plugins or settings change the game, so it sits under 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.