DZ Server JP PVE
Online EA 220.158.25.157:28015 checked 8m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 10% of all ranked servers, top 38% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence
- wipe-day peak
- 12players, last three wipes
Coming wipes
- in 7d 20hThu 5 Nov, 19:00 UTCFW
- in 35d 20hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 12, 40 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
1 OCT 2026Thu 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Rules and settings
What settings and rules does DZ Server JP PVE run?
No gather rate appears in the name DZ Server JP PVE. The default group limit of 8 players applies. Filed under pve, player combat is not allowed. Plugins or settings change the game; it is listed under Modded in the server browser. Filed under plugins: Oxide. VAC is on: Valve's anti-cheat is enabled.
What is the map on DZ Server JP PVE?
DZ Server JP PVE runs a procedural map of size 4,000 with seed 142534215, generated by the game. You can view the map on RustMaps from this page, as the same size and seed give the same map.
Lists and filters
Which lists and filters on Rust Server Index is DZ Server JP PVE filed under?
These lists on Rust Server Index take DZ Server JP PVE: Modded Rust servers, filed by play style and Rust PvE servers, filed A to Z. It appears under the following filters on the server list: 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.
How should you read the tags listed for DZ Server JP PVE?
The server's own tags are listed here, and the game's server browser reads them: DZ Server JP PVE gives gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): Build on file: 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty; ^m (Monthly): A monthly cycle: wipes fall with Facepunch's force wipe; ^p (PvE): No fighting between players: the danger comes from the world; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): This one is Modded, since plugins or settings change how it plays; EA (East Asia): The browser files it under East Asia. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipe dates
What happens on wipe day at DZ Server JP PVE?
Its recent wipes averaged 12 players at peak. The latest wipe peaked 40 hours in.
How often is DZ Server JP PVE wiped, and on what schedule?
One wipe a month is all DZ Server JP PVE runs, and it comes with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC, as the force wipe that reaches every Rust server. Its present world dates from 27 days 1 hours. A monthly wipe schedule is published in its tags.
Players and ranking
How is DZ Server JP PVE ranked compared with the rest?
On seven-day player hours, DZ Server JP PVE takes #2,182 overall and #211 in Asia, within the top 10% of ranked servers.
What does the player count on DZ Server JP PVE look like?
The live count for DZ Server JP PVE stands at 0 players, out of 50 slots. Averaged across seven days: 2 players, peaking at 7. Filed under busiest hour: 17:00 UTC in the last 48 hours, averaging 5 players.
Operator and status
What Rust version is DZ Server JP PVE on?
Rust network protocol 2635 and build 168909, on Linux, is what DZ Server JP PVE runs. To join you need the same protocol; Steam handles the update.
How reliable is DZ Server JP PVE, and is it online now?
You will find DZ Server JP PVE online as of now. The uptime it reports puts the last restart at about 23 hours ago. Of the last 7 full days, 168 of 168 hours were up, 100% of the time. On 13 September 2026 it was first seen by Rust Server Index.
How well does DZ Server JP PVE perform?
Averaged over the last 48 hours, server fps was 85, with a low of 52. Buildings, deployables and everything else in the world came to as many as 119,613 entities. Up to 3,573 MB of memory was in use. Lag, to players, is low fps and an entity count that climbs.
Where in the world is DZ Server JP PVE hosted?
Filed under Asia by its own listing, DZ Server JP PVE carries the EA tag. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. You will reach it at 220.158.25.157:28015.
Joining the server
What is the way onto DZ Server JP PVE?
Two ways in. Type client.connect 220.158.25.157:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you. The website can be found at https://discord.com/invite/pQKV9Qk5Ye.
Server tags
What each one means.
Published as mp50,ptrak,$r?,v2635,^m,EA,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp50
ts8
v2635
cs168909
ptrak
$r?
Wipe schedule
^m
Gameplay
^p
Mods and access
^o
^z
Region
EA
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.
