Rust Server Analytics 95,829 players11,876 servers
All servers
Drill-through Server detail

[EA]Japan-Server |PvP|

Online EA 133.117.73.110:28015 checked 9m ago

Drill-through
FilterServeris [EA]Japan-Server |PvP|
Attributes
biweekly wipes moddedoxide
Last refreshed
Players now 1/ 100
7-day average 0 peak 3
Rank #5,889 top 27% · #393 in EA
Last wipe 11d ago biweekly schedule
Next wipe 2d 14h Fri 30 Oct, 09:00 UTC
Capacity 1% full

Players

average and peak, with its wipes marked
AveragePeak
0123419:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
05010015020019:0004:0013:0023:0008:0017: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
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 09:00 UTC, in 2d 14h. Its biweekly schedule tag · low confidence

usual gap14.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

Coming wipes

InWhen, UTCKind
2d 14hFri 30 Oct, 09:00 UTCits own
9d 0hThu 5 Nov, 19:00 UTCFW force wipe
16d 14hFri 13 Nov, 09:00 UTCits own
30d 14hFri 27 Nov, 09:00 UTCits own
37d 0hThu 3 Dec, 19:00 UTCFW force wipe
44d 14hFri 11 Dec, 09:00 UTCits own

The first 48 hours of its last wipes

Fri 16 OctThu 1 OctWed 16 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 24 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 09:00 UTC11d ago 2 – running 0
Thu 1 Oct, 18:55 UTC FW25d ago 4 halved by day 1 14.6 days 0
Wed 16 Sep, 13:05 UTC41d ago 0 – 15.2 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
[JP]初心者PVPサーバー|RaidTime・ Events EA · groups of 10+ · biweekly · 19 on average 3 / 100
[JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 EA · no group limit · biweekly · 5 on average 0 / 20
瞌睡熊『5倍10废|10.27|萌新首选|无权限』 EA · groups of 8+ · biweekly · 4 on average 2 / 100
[JP/PvE][BPリサーチ]MatoyServer初しん者〇 EA · groups of 8+ · biweekly · 2 on average 1 / 50
[JPN] Apple Server | PvP | Vanilla | 2Weekly EA · groups of 8+ · biweekly · 2 on average 2 / 50
cczsbwd/solo/独狼/原倍半月清/月图/公益服 EA · no group limit · biweekly · 1 on average 1 / 50

Quick answers

from the figures on this page

Wipe cycle

On what cycle does [EA]Japan-Server |PvP| wipe?

Its tag guides the prediction, since [EA]Japan-Server |PvP| has too few wipes on record to confirm the schedule. Friday 30 October at 09:00 UTC is when its next wipe is due. 11 days 9 hours ago the current world was made. The tags carry an every-two-weeks wipe schedule.

On [EA]Japan-Server |PvP|, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. The highest player count on the latest wipe arrived 24 hours in. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. The fall below half arrived by day 1 when it didn't hold.

Server details

What is the hosting location of [EA]Japan-Server |PvP|?

In Asia, according to its EA tag, sits [EA]Japan-Server |PvP|. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. You will find it at 133.117.73.110:28015.

Which Rust version is [EA]Japan-Server |PvP| on?

Rust network protocol 2635 and build 168909 on Linux is the setup for [EA]Japan-Server |PvP|. Your game must match the protocol to join, and Steam applies that update.

Is [EA]Japan-Server |PvP| up, and how steady is its uptime?

As of the latest refresh, [EA]Japan-Server |PvP| is online. The uptime it reports puts the last restart at about 8 hours ago. Of 168 hours in the last 7 full days, 168 were up: 100%. The first sighting of it by Rust Server Analytics was on 13 September 2026.

What performance does [EA]Japan-Server |PvP| show?

Server fps averaged 116 over the last 48 hours, with a floor of 81. Buildings, deployables and all other world objects brought the entity total to 100,693. Peak memory was 2,954 MB. A climbing entity count and low fps are the lag players perceive.

Tags

How should the tags on [EA]Japan-Server |PvP| be read?

gmrust (Game mode): Rust survival, standard ruleset; mp100 (Max players): Player slots: 100; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): A region code is not set; ^b (Biweekly): Every two weeks the server wipes; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): The Modded section, because plugins or settings modify play; EA (East Asia): Its browser listing sits in East Asia are the tags [EA]Japan-Server |PvP| publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

On Rust Server Analytics, which lists and filters feature [EA]Japan-Server |PvP|?

The following Rust Server Analytics lists count [EA]Japan-Server |PvP| among their servers: Modded Rust servers: live data. It appears on the server list under the following filters: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Population

Where does [EA]Japan-Server |PvP| sit among Rust servers?

For player hours over the last seven days, [EA]Japan-Server |PvP| places #5,889 globally and #393 in Asia, in the top 27% of all ranked servers.

How many players does [EA]Japan-Server |PvP| carry?

Population at the current refresh: 1 players on [EA]Japan-Server |PvP|, against 100 slots. Averaging 0 players across seven days, the server reached a peak of 3. Averaged over 48 hours, activity is highest at 07:00 UTC with 3 players.

Map and rules

How is [EA]Japan-Server |PvP| configured, and what rules apply?

No gather rate is given in the name of [EA]Japan-Server |PvP|. The default group cap of 8 players applies. survival is the game mode, the standard game: gather, build, raid. Raiding and PvP combat are available. Plugins or settings modify the game, and it is listed as Modded. Plugins from Oxide are in use. VAC, Valve's anti-cheat, is enabled.

The map on [EA]Japan-Server |PvP|: which one is it?

[EA]Japan-Server |PvP| uses a procedural map of size 4,096 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. The name of the map is Custom Map.

How to join

What is the way onto [EA]Japan-Server |PvP|?

In the Rust console (F1), enter client.connect 133.117.73.110:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://discord.com/invite/473S8yCnC7 is its website.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,EA,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival, standard ruleset.
mp100
Max players Player slots: 100.
ts8
Group limit Team cap of 8, the stock game setting.
v2635
Protocol To join, your game version must match protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code A region code is not set.

Wipe schedule

^b
Biweekly Every two weeks the server wipes.

Mods and access

^o
Oxide It runs Oxide (uMod) for plugins.
^z
Modded The Modded section, because plugins or settings modify play.

Region

EA
East Asia Its browser listing sits in East Asia.

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.