Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO G SRV11,765online PAX73,690playing OCC3,473with players WIPED 3H229
MODModded traffic
Callsign

JPP4749=

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

Online 162.43.38.195:28015 checked 8m ago

moddedoxidepve
Clearance · join
Players now 0/ 15 0% full
7-day average0peak 3
Rank#4,749top 21%
Last wipe28d agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

AveragePeak
00.511.5223:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

05010015020023:0008:0017:0003:0012:0021: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 21% of all ranked servers. Ranked on player hours over the last seven days.

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

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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign PVE016EA · groups of 16+ · biweekly · 59 on average 【炮炮PVE启蒙】纯净|特色|突袭|技能
    Players 18/200
  2. 02MOD
    Callsign QSP016EA · groups of 8+ · 37 on average QS『鱼山路』pve|耐玩|升级|突袭
    Players 32/100
  3. 03MOD
    Callsign PVE015EA · groups of 8+ · monthly · 34 on average [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本
    Players 22/100
  4. 04MOD
    Callsign JPN100EA · groups of 16+ · 33 on average Japan Tokyo - Vanilla PvE|JP|Beginner
    Players 9/100
  5. 05MOD
    Callsign JPN110EA · groups of 16+ · 21 on average Japan Tokyo - Chill PvE|JP
    Players 8/100
  6. 06MOD
    Callsign PVE002EA · groups of 8+ · monthly · 20 on average 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地
    Players 15/88
ATIS · this server

Quick answers

From the figures on this page.

Tags

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

These Rust Tracker lists carry [JP] PVE テスト用サーバー 入場自由: PvE servers, tracked live and Modded servers, tracked live. It comes up 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 tags does [JP] PVE テスト用サーバー 入場自由 carry, and what do they mean?

These tags are published by [JP] PVE テスト用サーバー 入場自由 for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp15 (Max players): 15 slots on this server; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): Build: 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^p (PvE): The world is the danger; players do not fight each other; ^o (Oxide): Plugin framework confirmed: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; modded (Modded): Plugins or settings alter the game, so it is listed under Modded. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

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

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

Which wipe times are confirmed for [JP] PVE テスト用サーバー 入場自由?

No next wipe to predict for [JP] PVE テスト用サーバー 入場自由, which wipes at irregular times. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. 28 days since this world was made.

Location and Status

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

Right now [JP] PVE テスト用サーバー 入場自由 is online. The uptime it reports puts the last restart about 4 hours ago. 167 of 168 hours up over the last 7 full days: 99% uptime. First contact for Rust Tracker: 13 September 2026.

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

Rust network protocol 2635 and build 168909 on Linux is what [JP] PVE テスト用サーバー 入場自由 runs. The same protocol is required to join, and Steam updates it for you.

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

Server fps held an average of 113 across the last 48 hours, never below 67. Buildings, deployables and the rest of the world took it to a maximum of 85,429 entities. Peak memory use: 2,924 MB. Players feel lag when fps drops and the entity count climbs.

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

The name of [JP] PVE テスト用サーバー 入場自由 points to Asia, though no region tag is published. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 162.43.38.195:28015.

Player Count

How many players are on [JP] PVE テスト用サーバー 入場自由 right now?

Tracking [JP] PVE テスト用サーバー 入場自由: 0 of 15 slots filled. Over seven days: average 0, peak 3 players. Peak traffic in the last 48 hours came at 08:00 UTC, averaging 1 players.

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

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

Settings

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

The name of [JP] PVE テスト用サーバー 入場自由 carries no gather rate. Up to 8 players per group, the game's default. It runs pve, fighting between players is off. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins run on it. On: VAC, Valve's anti-cheat.

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

Generated by the game from seed 1573025114, the procedural map on [JP] PVE テスト用サーバー 入場自由 measures 3,500. Same size, same seed, same map. RustMaps shows it, linked from this page. Its map goes by the name Custom Map.

How to Join

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

To connect: start Rust, press F1, enter client.connect 162.43.38.195:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join. For the website, go to https://note.com/7010_rust.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, standard mode.
mp15
Max players 15 slots on this server.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build Build: 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Gameplay

^p
PvE The world is the danger; players do not fight each other.

Mods and access

^o
Oxide Plugin framework confirmed: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is listed under Modded.
modded
Modded Plugins or settings alter the game, so it is listed 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.