Rust Server TrendsSeismic network · station log
Recording Stations11,741 Players62,626 Active3,351 Wipes · 3 h195 48 h

Station XX-4845 · recording

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

Online 162.43.38.195:28015 checked 9m ago

moddedoxidepve
Connect
Players now
0/ 15
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 3
Rank
#4,845
top 22%
Last wipe
27d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-4845 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 15 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+1into Wed 08:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5212:0021:0006:0015:0001:0010:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020012:0021:0006: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.

Channel 3 · rank movement

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.

Expected events

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 gap
2.6 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
100%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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 17:58 UTC FW27d ago M0.3rising 2 – running 0
Sun 27 Sep, 16:13 UTC31d ago M0.0steady 1 held half 4.1 days 1
Sat 26 Sep, 13:54 UTC32d ago M0.0rising 1 – 1.1 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 58 on average
83/ 200
QS『鱼山路』pve|耐玩|升级|突袭 EA · groups of 8+ · 37 on average
44/ 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
53/ 100
Japan Tokyo - Chill PvE|JP EA · groups of 16+ · 21 on average
32/ 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 20 on average
18/ 88
Readings, in words

Quick answers

from the figures on this page

Server rules

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

Generated by the game, the map on [JP] PVE テスト用サーバー 入場自由 is procedural, size 3,500 with seed 1573025114. Size and seed produce the same map, so RustMaps can show it from this page. Its map carries the name Custom Map.

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

You will find no gather rate in the name of [JP] PVE テスト用サーバー 入場自由. At the game's default, groups can have up to 8 players. pve is the game mode, no player-versus-player fighting. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Player counts

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

At this moment, [JP] PVE テスト用サーバー 入場自由 records 0 players across 15 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 3. The busiest point in the last 48 hours came at 08:00 UTC, averaging 1 players.

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

On player hours for the past week, [JP] PVE テスト用サーバー 入場自由 sits at #4,845, which puts it inside the top 22% of every ranked server.

Server details

How reliably does [JP] PVE テスト用サーバー 入場自由 stay online?

Right now, you can reach [JP] PVE テスト用サーバー 入場自由. Going by the uptime figure it reports, it restarted about 28 minutes ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does [JP] PVE テスト用サーバー 入場自由 perform under load?

Its average server fps over the last 48 hours was 109, and it never dropped below 67. The world held up to 84,593 entities at its peak, buildings and deployables included. It reached a ceiling of 2,924 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Where in the world is [JP] PVE テスト用サーバー 入場自由 hosted?

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

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

Rust network protocol 2635 and build 168909 on Linux is what [JP] PVE テスト用サーバー 入場自由 runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

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

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.

How often does [JP] PVE テスト用サーバー 入場自由 wipe, and on which days?

No next wipe can be predicted for [JP] PVE テスト用サーバー 入場自由, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 27 days 13 hours is how long the current world has been running.

Lists and tags

What do the server tags on [JP] PVE テスト用サーバー 入場自由 mean?

These are the tags [JP] PVE テスト用サーバー 入場自由 publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp15 (Max players): Slots: 15; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; modded (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does [JP] PVE テスト用サーバー 入場自由 appear?

These Rust Server Trends lists include [JP] PVE テスト用サーバー 入場自由: Modded Rust servers, tracked live and Rust PvE servers. You will find it 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.

Connecting

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

To join, enter client.connect 162.43.38.195:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. https://note.com/7010_rust is where its website lives.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp15
Max players Slots: 15.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.
modded
Modded The game is changed by plugins or settings, placing it 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.