Skip to the page
Network live 11,894 servers online 101,584 players aboard 404 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

OKAWAServer_JP_PvE

Online 160.251.175.229:28015 checked 10m ago

Tracking number · connect
Wipe progress · wiped 27d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –too few wipes seen yet
9/ 100 players now 9% full
57-day averagepeak 17
#1,336ranktop 6%
27d agolast wipeno schedule published
–next wipetoo few wipes seen yet
Delivery history

Players, performance and rank

Players

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

Hourly average and peak, UTC.

Server performance

02040608018: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
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 6% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

0.5 daysusual gapbetween real wipes
45wipe-day peakplayers, last three wipes

The first 48 hours of its last wipes

Fri 2 OctThu 1 Oct
020406080+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 46, 44 hours in.

Wipes

every wipe as a delivery, newest first
  1. Fri 2 Oct, 11:17 UTC 12:17 UK · 27d ago
    Wipe delivered
    Peak
    46
    Crowd
    –
    Lasted
    running
    Players before
    30
  2. Thu 1 Oct, 23:05 UTC FW 00:05 UK · 27d ago
    Force wipe delivered
    Peak
    44
    Crowd
    –
    Lasted
    0.5 days
    Players before
    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 parcels

Similar servers

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

  1. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 514 on average 373 / 425
  2. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average 442 / 500
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 280 on average 981 / 1000
  4. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average 58 / 100
  5. Rustoria.co - EU MainEU · groups of 16+ · weekly · 265 on average 986 / 1000
  6. Rustoria.co - US MainNA · groups of 16+ · weekly · 235 on average 31 / 250
Help desk

Quick answers

From the figures on this page.

Player activity

Where does OKAWAServer_JP_PvE place among Rust servers?

A seven-day player-hours count places OKAWAServer_JP_PvE at #1,336: the top 6% of every ranked server.

How many players are on OKAWAServer_JP_PvE right now?

Checking now: 9 players on 100 slots at OKAWAServer_JP_PvE. Averaged over the past week: 5 players, peaking at 17. Over the last 48 hours, the peak hour came at 14:00 UTC with an average of 12 players.

Rules and settings

On what map does OKAWAServer_JP_PvE take place?

Generated by the game with seed 4180011, the procedural map on OKAWAServer_JP_PvE is size 4,500. Size and seed match means the map matches, so you can view it on RustMaps from this page.

Which settings and rules apply on OKAWAServer_JP_PvE?

The name of OKAWAServer_JP_PvE gives no gather rate. The group limit is 16 players. survival is the mode, gather, build and raid, as the standard game goes. Raiding and PvP are both on. It appears in the server browser under Community, being a community server. VAC, the anti-cheat from Valve, is active.

About the server

What location does OKAWAServer_JP_PvE run from?

No region is published by OKAWAServer_JP_PvE. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. The address to connect to is 160.251.175.229:28015.

Does OKAWAServer_JP_PvE perform well?

The 48-hour average for server fps stands at 38, never dipping below 28. Buildings, deployables and all the rest of the world pushed its entity count as high as 193,067. Memory use peaked at 6,839 MB. Players feel a rising entity count and low fps as lag.

Is OKAWAServer_JP_PvE up, and how good is its uptime?

OKAWAServer_JP_PvE is up and online at the moment. About 5 days 18 hours ago is when it last restarted, judged by the uptime it gives. 99% is the uptime for the last 7 full days, up for 167 of 168 hours. 13 September 2026 is when Rust Wipe Tracker first recorded it.

What Rust version is OKAWAServer_JP_PvE using?

Rust network protocol 2635 and build 168909 on Linux is what OKAWAServer_JP_PvE runs. To join, your game must be on the same protocol; Steam handles that update for you.

Wipe schedule

What should you expect from wipe day on OKAWAServer_JP_PvE?

At their busiest, its recent wipes drew an average of 45 players. 44 hours after the latest wipe, the crowd reached its peak.

On what schedule does OKAWAServer_JP_PvE reset its map?

To tell its rhythm we would need more of OKAWAServer_JP_PvE's wipes on record; there are too few yet. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. The world it is running was made 27 days 6 hours.

Tags and filters

On Rust Wipe Tracker, which lists and filters is OKAWAServer_JP_PvE part of?

These Rust Wipe Tracker lists take OKAWAServer_JP_PvE: Rust community servers, unmodded. These are the filters that bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the tags on OKAWAServer_JP_PvE?

The game's server browser picks up these OKAWAServer_JP_PvE tags: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): Slot count: 100; ts16 (Group limit): Team size caps at 16; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): A region code isn't set. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.

Connecting

How do you connect to OKAWAServer_JP_PvE?

Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 160.251.175.229:28015. You will find its website at https://discord.com/invite/mRc2TvcSsA.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts16

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players Slot count: 100.
ts16
Group limit Team size caps at 16.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet handles networking, as standard for the game.
$r?
Region code A region code isn't set.

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.