Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO F SRV11,898online PAX102,237playing OCC3,978with players WIPED 3H333
MODModded traffic
Callsign

JPN5483=

[EA]Japan-Server |PvP|

Online EA 133.117.73.110:28015 checked 9m ago

biweekly wipes moddedoxide
Clearance · join
Players now 0/ 100 0% full
7-day average0peak 3
Rank#5,483top 25% · #362 in EA
Last wipe13d agobiweekly schedule
Next wipe15hFri 30 Oct, 09:00 UTC
Track history

Players

AveragePeak
00.250.50.75118:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

Server performance

05010015020018:0003:0012:0022:0007:0016: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 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Friday 30 October, 09:00 UTC, in 15h.

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

  1. 15hFri 30 Oct, 09:00 UTC
  2. 7d 1hThu 5 Nov, 19:00 UTCFW
  3. 14d 15hFri 13 Nov, 09:00 UTC
  4. 28d 15hFri 27 Nov, 09:00 UTC
  5. 35d 1hThu 3 Dec, 19:00 UTCFW
  6. 42d 15hFri 11 Dec, 09:00 UTC

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 UTC13d ago 2 – running 0
Thu 1 Oct, 18:55 UTC FW27d ago 4 halved by day 1 14.6 days 0
Wed 16 Sep, 13:05 UTC43d 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.

Nearby traffic

Similar servers

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

  1. 01MOD
    Callsign EVN020EA · groups of 10+ · biweekly · 15 on average [JP]初心者PVPサーバー|RaidTime・ Events
    Players 3/100
  2. 02MOD
    Callsign ONL015EA · no group limit · biweekly · 4 on average [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29
    Players 1/20
  3. 03MOD
    Callsign SRV016EA · groups of 8+ · biweekly · 4 on average 瞌睡熊『5倍10废|10.29|萌新首选|无权限』
    Players 2/100
  4. 04MOD
    Callsign JPP015EA · groups of 8+ · biweekly · 2 on average [JP/PvE][BPリサーチ]MatoyServer初しん者〇
    Players 0/50
  5. 05MOD
    Callsign JPN016EA · groups of 8+ · biweekly · 2 on average [JPN] Apple Server | PvP | Vanilla | 2Weekly
    Players 1/50
  6. 06MOD
    Callsign CCZ012EA · no group limit · biweekly · 2 on average cczsbwd/solo/独狼/原倍半月清/月图/公益服
    Players 1/50
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which lists and filters on Rust Tracker show [EA]Japan-Server |PvP|?

On Rust Tracker, [EA]Japan-Server |PvP| sits in these lists: Modded servers, tracked live. These filters surface it on the server list: 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.

Which tags does [EA]Japan-Server |PvP| carry, and what do they mean?

The game's server browser reads these tags from [EA]Japan-Server |PvP|: gmrust (Game mode): Standard survival mode for Rust; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; listed under Modded; EA (East Asia): In the server browser it is listed under East Asia. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Schedule

What should you expect on [EA]Japan-Server |PvP| when wipe day lands?

Recent wipes averaged a peak of 2 players. 24 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 0% of recent wipes. In the other cases, half the peak was lost by day 1.

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

[EA]Japan-Server |PvP|'s schedule is unconfirmed, too few wipes being on record, so the prediction follows its tag. Due on Friday 30 October at 09:00 UTC: its next wipe. This world has been running 13 days 8 hours. Tags list a wipe schedule of every two weeks.

Server Details

What is the uptime on [EA]Japan-Server |PvP|, and is it online?

Right now [EA]Japan-Server |PvP| is online. About 7 hours ago it restarted last, based on reported uptime. 167 of 168 hours up over the last 7 full days: 99% uptime. Rust Tracker logged it first on 13 September 2026.

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

Rust network protocol 2635 and build 168909 on Linux is what [EA]Japan-Server |PvP| runs. The same protocol is required to join, and Steam updates it for you.

Is [EA]Japan-Server |PvP| holding performance?

Average server fps over the last 48 hours: 109, with a low of 52. Peak entity count: 101,145, covering buildings, deployables and all else in the world. Peak memory use: 3,186 MB. A climbing entity count and low fps are what register as lag for players.

Which location is [EA]Japan-Server |PvP| in?

In Asia, under its EA tag, is where [EA]Japan-Server |PvP| lists itself. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 133.117.73.110:28015.

Player Count

Is [EA]Japan-Server |PvP| busy?

Slots 100; players on board 0: that is [EA]Japan-Server |PvP| now. Seven-day average 0 players; peak 3. Peak traffic in the last 48 hours came at 18:00 UTC, averaging 1 players.

How does [EA]Japan-Server |PvP| compare in the rankings?

Top 25% of all ranked servers and #362 in Asia: [EA]Japan-Server |PvP| ranks #5,483 on player hours over the last seven days.

Settings

Which settings and rules are confirmed on [EA]Japan-Server |PvP|?

No gather rate appears in [EA]Japan-Server |PvP|'s name. Up to 8 players per group, the game's default. survival is the game mode, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. Plugins or settings change the game, and the server browser lists it under Modded. Plugins on it: Oxide. On: VAC, Valve's anti-cheat.

Which map is loaded on [EA]Japan-Server |PvP|?

The map on [EA]Japan-Server |PvP| is procedural, size 4,096, seed 1337, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map. Its map goes by the name Custom Map.

Connect

How do you get onto [EA]Japan-Server |PvP|?

Open the console in Rust with F1 after starting the game, then type client.connect 133.117.73.110:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you. For the website, go to https://discord.com/invite/473S8yCnC7.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp100
Max players 100 slots on this server.
ts8
Group limit Team limit is 8, the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; listed under Modded.

Region

EA
East Asia In the server browser it is listed under 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.