Rust Data

rustdata.spaceservers162.43.38.195:29015.ipynb

Run all rust-data · live

‹ All servers

Online 162.43.38.195:28015 checked 10m ago

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

moddedoxidepve

Connect

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

Right now

srv.summary()
players now 0/15 # 0% full
7-day average 0 # peak 3
rank #4,736 # top 21%
last wipe 27d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5220:0005:0014:0000:0009:0018:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020020:0005:0014:0000:0009:0018: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

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 17:58 UTC FW28d ago 2 NaN running 0
1 Sun 27 Sep, 16:13 UTC32d ago 1 held half 4.1 days 1
2 Sat 26 Sep, 13:54 UTC33d ago 1 NaN 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.

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

Map

3500 · seed 1573025114
Map of [JP] PVE テスト用サーバー 入場自由
map
Custom Map
size
3500
seed
1573025114

Server

srv.info()
address
162.43.38.195:28015
region
–
max players
15
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 22:03 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
By participating, you will be deemed to have agreed to the contents of the website.This server is a private test server for Japanese users only.(サーバーに接続)ボタンを押し場合は、当WEBサイトの内容に同意したものとみなします。パスワードはHPに書いてます。

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 16+ · biweekly · 59 on average36/200
1QS『鱼山路』pve|耐玩|升级|突袭EA · groups of 8+ · 37 on average33/100
2[坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱EA · groups of 8+ · monthly · 34 on average23/100
3Japan Tokyo - Vanilla PvE|JP|BeginnerEA · groups of 16+ · 33 on average15/100
4Japan Tokyo - Chill PvE|JPEA · groups of 16+ · 21 on average8/100
5爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average18/88

Quick answers

From the figures on this page.

Population data

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

Player hours over seven days put [JP] PVE テスト用サーバー 入場自由 at #4,736, in the top 21% of the ranked set.

How many players does [JP] PVE テスト用サーバー 入場自由 hold at once?

Current row: 0 players on [JP] PVE テスト用サーバー 入場自由, against 15 slots. Over the last seven days it averaged 0 players and peaked at 3. Peak hour in the last 48 hours: 08:00 UTC, mean 1 players.

Server data

What does performance look like on [JP] PVE テスト用サーバー 入場自由?

The 48-hour average is 112 server fps, with a low of 67. The entity count peaked at 85,429, covering buildings, deployables and the rest of the world. Memory peaked at 2,924 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

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

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

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

Online is the state at the latest refresh for [JP] PVE テスト用サーバー 入場自由. The uptime it reports puts the last restart about 1 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

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

Its name points to Asia, but [JP] PVE テスト用サーバー 入場自由 publishes no region tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 162.43.38.195:28015.

Map and rules

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

No gather rate appears in the name: [JP] PVE テスト用サーバー 入場自由. No custom cap; the default of 8 players per group stands. Game mode pve, with this note: player combat is not allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

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

[JP] PVE テスト用サーバー 入場自由 runs a procedural map of size 3,500 with seed 1573025114, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.

Wipe data

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

No next wipe can be predicted for [JP] PVE テスト用サーバー 入場自由, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 27 days 21 hours ago.

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

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 21 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Lists and tags

Where does [JP] PVE テスト用サーバー 入場自由 appear among Rust Data lists and filters?

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

Which meanings do the tags on [JP] PVE テスト用サーバー 入場自由 hold?

Read by the game's server browser, the tags [JP] PVE テスト用サーバー 入場自由 publishes are: gmrust (Game mode): Rust survival in its standard form; mp15 (Max players): Slot count: 15; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; modded (Modded): Modded listing: the game is changed by plugins or settings. 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

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

The manual route: launch Rust, F1, then client.connect 162.43.38.195:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://note.com/7010_rust is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp15
Max players Slot count: 15.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

Mods and access

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

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 104,335 players 11,883 servers online