RUST METRICSFlight deck · live data
Data live Servers11,686 Players34,939 Populated2,865 Fresh wipes 3 h97 Scan5 min
‹ All servers220.158.25.157:28015
Online Full Queue Fresh wipe Wipe due No query

DZ Server JP PVE

Online EA 220.158.25.157:28015 checked 10m ago

monthly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 01:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

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

Server fps

48 h low 52 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 117,139 ×1000

Entities

48 h range 100,674–119,613 · memory 2,767 MB
1239 ET SINCE RESTART 04:01

Uptime

4 h 1 min since its last restart, at the last reading
7-day average2peak 7
Rank#2,196top 10% · #212 in EA
Last wipe27d agomonthly schedule
Next wipe7d 15hThu 5 Nov, 19:00 UTC FW
Memory2,767MB48 h peak 5 players
REC 1

Players

AveragePeak
0246804:0013:0022:0006:0015:0001:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020004:0013:0022:0006:0015:0001: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
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 10% of all ranked servers, top 38% in EA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h. The force wipe · high confidence

wipe-day peak12players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 15hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 15hFW

The first 48 hours of its last wipes

05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 12, 40 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 21:01 UTC FW27d ago 12 – running 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 DZ Server JP PVE when wipe day comes?

The busiest point of its recent wipes drew 12 players on average. 40 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does DZ Server JP PVE follow?

The only wipe for DZ Server JP PVE is the force wipe, once a month. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 27 days 6 hours ago. Its tags carry a monthly wipe schedule.

Tag meanings

Which tags does DZ Server JP PVE carry, and what do they mean?

Tags published by DZ Server JP PVE, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server; EA (East Asia): East Asia is the browser category it sits in. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show DZ Server JP PVE?

Rust Metrics lists featuring DZ Server 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: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Player count

Where does DZ Server JP PVE sit in the rankings?

Top 10% of all ranked servers: DZ Server JP PVE takes #2,196 on seven-day player hours and #212 in Asia.

How full does DZ Server JP PVE get?

Current headcount on DZ Server JP PVE: 0 players, 50 slots available. Seven-day check: 2 players on average. Peak reading: 7. The last 48 hours peaked at 17:00 UTC, averaging 5 players at that hour.

Operator and location

What location is DZ Server JP PVE hosted in?

Its EA tag places DZ Server JP PVE in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 220.158.25.157:28015.

What Rust version is DZ Server JP PVE on?

Rust network protocol 2635 and build 168909 on Linux is the build DZ Server JP PVE runs. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for DZ Server JP PVE?

Over the last 48 hours the average was 85 server fps; the floor was 52. Reading: 119,613 entities at the highest. That covers buildings, deployables and everything else. Reading: 3,573 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on DZ Server JP PVE, and is it online?

Check: connection. DZ Server JP PVE is online at this moment. Reading: uptime. About 4 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

What rules does DZ Server JP PVE enforce, and what are its settings?

Reading the name gives no gather rate for DZ Server JP PVE. 8 players per group, the default value. The mode is pve. Note the following: no combat against other players. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is DZ Server JP PVE on?

From seed 142534215, the game generates the procedural map on DZ Server JP PVE. Its size is 4,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

What do you do to join DZ Server JP PVE?

Check: join. Open Rust, press F1, then enter client.connect 220.158.25.157:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://discord.com/invite/pQKV9Qk5Ye.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^m,EA,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

Region

EA
East Asia East Asia is the browser category it sits in.

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.