RUST METRICSFlight deck · live data
Data live Servers11,899 Players104,128 Populated4,035 Fresh wipes 3 h421 Scan5 min
‹ All servers162.43.38.195:28015
Online Full Queue Fresh wipe Wipe due No query

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

Online 162.43.38.195:28015 checked 12m ago

moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 17:00 UTC
0 4 8 11 15 PAX 0 /15

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 107 SERVER FPS

Server fps

48 h low 67 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 84,383 ×1000

Entities

48 h range 81,579–85,429 · memory 1,900 MB
1239 ET SINCE RESTART 06:01

Uptime

6 h 1 min since its last restart, at the last reading
7-day average0peak 3
Rank#4,737top 21%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
Memory1,900MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5219:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020019:0004:0013:0023:0008:0017: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.

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

PLAN

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 17:58 UTC FW28d ago 2 – running 0
Sun 27 Sep, 16:13 UTC32d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

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

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 21 hours in. Until the next wipe, the crowd stayed above half that peak in 100% of its recent wipes.

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

No next wipe can be predicted for [JP] PVE テスト用サーバー 入場自由, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 27 days 20 hours ago.

Tags

How should you read the tags on [JP] PVE テスト用サーバー 入場自由?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp15 (Max players): Slots: 15; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; modded (Modded): Check: category. Modded, because plugins or settings alter the game from [JP] PVE テスト用サーバー 入場自由. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show [JP] PVE テスト用サーバー 入場自由?

These Rust Metrics lists carry [JP] PVE テスト用サーバー 入場自由: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does [JP] PVE テスト用サーバー 入場自由 sit in the rankings?

Ranking for [JP] PVE テスト用サーバー 入場自由: #4,737 on seven-day player hours, top 21% of all ranked servers.

How full does [JP] PVE テスト用サーバー 入場自由 get?

Current headcount on [JP] PVE テスト用サーバー 入場自由: 0 players, 15 slots available. Seven-day check: 0 players on average. Peak reading: 3. Average at the busiest hour was 1 players, at 08:00 UTC over the last 48 hours.

Operator and location

Where does [JP] PVE テスト用サーバー 入場自由 sit?

Reading: location. Nothing in the tags, but the name of [JP] PVE テスト用サーバー 入場自由 points to Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 162.43.38.195:28015.

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

Rust network protocol 2635 and build 168909 on Linux is the build [JP] PVE テスト用サーバー 入場自由 runs. Matching protocol is required to join. Let Steam update your game.

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

Over the last 48 hours the average was 110 server fps; the floor was 67. Reading: 85,429 entities at the highest. That covers buildings, deployables and everything else. Reading: 2,924 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on [JP] PVE テスト用サーバー 入場自由, and is it online?

Check: connection. [JP] PVE テスト用サーバー 入場自由 is online at this moment. By its reported uptime, the last restart was roughly 6 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

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

No gather rate appears in the name: [JP] PVE テスト用サーバー 入場自由. The group cap is 8 players, which is the default in the game. The mode is pve. Note the following: fighting between players is off. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

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

From seed 1573025114, the game generates the procedural map on [JP] PVE テスト用サーバー 入場自由. Its size is 3,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Its map carries the name Custom Map.

Join

How can you get onto [JP] PVE テスト用サーバー 入場自由?

Press F1 in Rust and enter client.connect 162.43.38.195:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://note.com/7010_rust is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp15
Max players Slots: 15.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Gameplay

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

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.
modded
Modded Check: category. Modded, because plugins or settings alter the game.

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.