RUST METRICSFlight deck · live data
Data live Servers11,808 Players82,963 Populated3,624 Fresh wipes 3 h313 Scan5 min
‹ All servers133.117.73.110:28015
Online Full Queue Fresh wipe Wipe due No query

[EA]Japan-Server |PvP|

Online EA 133.117.73.110:28015 checked 11m ago

biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 20:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

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

Entities

48 h range 81,114–101,145 · memory 2,725 MB
1239 ET SINCE RESTART 11:01

Uptime

11 h 1 min since its last restart, at the last reading
7-day average0peak 3
Rank#5,492top 25% · #362 in EA
Last wipe13d agobiweekly schedule
Next wipe10hFri 30 Oct, 09:00 UTC
Memory2,725MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75123:0008:0017:0002:0011:0020:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020023:0008:0017:0002:0011:0020: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
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.

PLAN

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 09:00 UTC, in 10h. 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. WPT 1Fri 30 Oct, 09:00 UTC10h
  2. WPT 2Thu 5 Nov, 19:00 UTC6d 20hFW
  3. WPT 3Fri 13 Nov, 09:00 UTC14d 10h
  4. WPT 4Fri 27 Nov, 09:00 UTC28d 10h
  5. WPT 5Thu 3 Dec, 19:00 UTC34d 20hFW
  6. WPT 6Fri 11 Dec, 09:00 UTC42d 10h

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 09:00 UTC13d ago 2 – running 0
Thu 1 Oct, 18:55 UTC FW28d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on [EA]Japan-Server |PvP| when wipe day comes?

At their busiest, its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 24 hours. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell below half by day 1 when it didn't.

When does [EA]Japan-Server |PvP| wipe?

The prediction follows its tag, because too few of [EA]Japan-Server |PvP|'s wipes are on record to confirm its schedule. On Friday 30 October at 09:00 UTC its next wipe is due. 13 days 13 hours ago the current world was made. A wipe schedule of every two weeks is published in its tags.

Tag meanings

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

These are the tags [EA]Japan-Server |PvP| publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Two-week wipe schedule; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EA (East Asia): East Asia is the browser category it sits in. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does [EA]Japan-Server |PvP| appear in Rust Metrics lists and filters?

On Rust Metrics, [EA]Japan-Server |PvP| sits in these lists: Modded Rust servers, checked live. These filters bring it up 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.

Population

What position does [EA]Japan-Server |PvP| hold among Rust servers?

Top 25% of all ranked servers: [EA]Japan-Server |PvP| takes #5,492 on seven-day player hours and #362 in Asia.

What player count does [EA]Japan-Server |PvP| carry?

0 of 100 slots are filled on [EA]Japan-Server |PvP| right now. Check: players over seven days. Average 0, peak 3. Check: 48-hour peak. 05:00 UTC, 1 players on average.

Operator and location

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

[EA]Japan-Server |PvP| gives Asia as its location, with the EA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 133.117.73.110:28015.

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

Reading: [EA]Japan-Server |PvP|, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

How does [EA]Japan-Server |PvP| perform?

Over the last 48 hours the average was 105 server fps; the floor was 52. Check: entities. The peak was 101,145, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,186 MB. Lag, as players feel it, is low fps plus a climbing entity count.

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

Check: connection. [EA]Japan-Server |PvP| is online at this moment. Reading: uptime. About 11 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does [EA]Japan-Server |PvP| enforce, and what are its settings?

No gather rate appears in the name: [EA]Japan-Server |PvP|. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

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

Size 4,096 and seed 1337: the game generates the procedural map on [EA]Japan-Server |PvP| from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Read the map name: Custom Map.

How to join

What do you do to join [EA]Japan-Server |PvP|?

To join: start Rust, press F1 and type client.connect 133.117.73.110:28015. Or press Launch Rust here and Steam opens the game and connects you. https://discord.com/invite/473S8yCnC7 is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.