Rust Data

rustdata.spaceservers160.251.175.229:28017.ipynb

Run all rust-data · live

‹ All servers

Online 160.251.175.229:28015 checked 12m ago

OKAWAServer_JP_PvE

Connect

srv = rust.server("160.251.175.229:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 9/100 # 9% full
7-day average 5 # peak 17
rank #1,336 # top 6%
last wipe 27d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0510152018:0003:0012:0021:0006:0015:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608018:0003:0012:0021:0006:0015: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

srv.rank.plot(invert=True)  # 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

srv.wipe_schedule()

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

usual gap0.5 daysbetween real wipes
wipe-day peak45players, 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 · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 11:17 UTC27d ago 46 NaN running 30
1 Thu 1 Oct, 23:05 UTC FW27d ago 44 NaN 0.5 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.

display(srv.map, srv.info())

Map

4500 · seed 4180011
Map of OKAWAServer_JP_PvE
map
Procedural Map
size
4500
seed
4180011
Open on RustMaps

Server

srv.info()
address
160.251.175.229:28015
region
–
max players
100
group limit
16 max
wipe schedule
–
last wipe
2 Oct 2026, 11:17 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
ようこそ大川サーバへ! 本サーバはPVEサーバです。 サーバのルールは左下のリンクからDiscordへ参加して確認してください。 ルール違反者は処罰の対象となります。 Discord内は現在、日本語のみです。 Welcome to OKAWAServer!! Click the [WEBPAGE] button to check the Server Rules. Language: Japanese only

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 514 on average385/425
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average458/500
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 280 on average988/1000
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average56/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 265 on average979/1000
5Rustoria.co - US MainNA · groups of 16+ · weekly · 235 on average28/250

Quick answers

From the figures on this page.

Population

How does OKAWAServer_JP_PvE compare in the rankings?

Player hours over seven days put OKAWAServer_JP_PvE at #1,336, in the top 6% of the ranked set.

How many players does OKAWAServer_JP_PvE hold at once?

Current row: 9 players on OKAWAServer_JP_PvE, against 100 slots. Over the last seven days it averaged 5 players and peaked at 17. Peak hour in the last 48 hours: 14:00 UTC, mean 12 players.

Server data

How smoothly does OKAWAServer_JP_PvE run?

Server fps over the last 48 hours averages 38; the floor is 28. The entity count peaked at 193,067, covering buildings, deployables and the rest of the world. Memory peaked at 6,839 MB. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is OKAWAServer_JP_PvE on?

Version Rust network protocol 2635 and build 168909 on Linux is reported by OKAWAServer_JP_PvE. Joining needs the same protocol on your game; Steam handles the update.

How reliable is OKAWAServer_JP_PvE, and is it up?

The current sample puts OKAWAServer_JP_PvE online. Count back 5 days 17 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.

Which location does OKAWAServer_JP_PvE run from?

No region is published by OKAWAServer_JP_PvE. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 160.251.175.229:28015 is its address.

Settings and map

Which rules apply on OKAWAServer_JP_PvE, and what settings?

You will not find a gather rate in the string OKAWAServer_JP_PvE. 16 players is the maximum per group. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. VAC is running: Valve's anti-cheat is on.

Which map has OKAWAServer_JP_PvE loaded?

Size 4,500, seed 4180011: the procedural map on OKAWAServer_JP_PvE, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

When does OKAWAServer_JP_PvE wipe, and how often?

Too few wipes are on record for OKAWAServer_JP_PvE to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 5 hours ago.

What is wipe day on OKAWAServer_JP_PvE like?

Across recent wipes the busiest point averaged 45 players. The crowd on the latest wipe topped out 44 hours after it began.

Tags, lists

Which lists on Rust Data hold OKAWAServer_JP_PvE, and which filters?

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

Which meanings do the tags on OKAWAServer_JP_PvE hold?

The game's server browser reads these tags from OKAWAServer_JP_PvE: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts16 (Group limit): Team size tops out at 16; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way to join OKAWAServer_JP_PvE?

The manual route: launch Rust, F1, then client.connect 160.251.175.229:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://discord.com/invite/mRc2TvcSsA is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players The server lists 100 slots.
ts16
Group limit Team size tops out at 16.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is 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.

Rust Data 99,159 players 11,894 servers online