Station XX-1331 · recording
OKAWAServer_JP_PvE
Online 160.251.175.229:28015 checked 11m ago
- Players now
- 9/ 100
- 9% full
- Motion · 24 h
- M0.1▲rising
- +1 players on the day
- 7-day average
- 5
- peak 17
- Rank
- #1,331
- top 6%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 9of 100 slots
- Motion · 24 h
- M0.1▲rising+1 players
- Sharpest hour
- −5into Wed 17:00 UTC
- Peak · 48 h
- 13most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 6% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 0.5 daysbetween real wipes
- wipe-day peak
- 45players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 46, 44 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 2 Oct, 11:17 UTC27d ago | M1.2▲rising | 46 | – | running | 30 | |
| Thu 1 Oct, 23:05 UTC FW27d ago | M1.6▲rising | 44 | – | 0.5 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on OKAWAServer_JP_PvE?
Generated by the game, the map on OKAWAServer_JP_PvE is procedural, size 4,500 with seed 4180011. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on OKAWAServer_JP_PvE?
The name of OKAWAServer_JP_PvE gives no gather rate. Up to 16 players can be in a group. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.
Live population
What is the current population on OKAWAServer_JP_PvE?
9 of the 100 slots on OKAWAServer_JP_PvE are filled right now. Averaged across the last seven days the population was 5 players, reaching a peak of 17. Averaged over the last 48 hours, the busiest hour was 14:00 UTC at 12 players.
How does OKAWAServer_JP_PvE rank against other Rust servers?
On player hours for the past week, OKAWAServer_JP_PvE sits at #1,331, which puts it inside the top 6% of every ranked server.
Server facts
How reliably does OKAWAServer_JP_PvE stay online?
OKAWAServer_JP_PvE is up at the moment. Going by the uptime figure it reports, it restarted about 5 days 15 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
How well does OKAWAServer_JP_PvE perform under load?
Its average server fps over the last 48 hours was 38, and it never dropped below 28. The world held up to 193,489 entities at its peak, buildings and deployables included. Its highest memory use was 6,839 MB. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is OKAWAServer_JP_PvE hosted?
No region is published by OKAWAServer_JP_PvE. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 160.251.175.229:28015.
What build of Rust does OKAWAServer_JP_PvE use?
On Linux, OKAWAServer_JP_PvE runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on OKAWAServer_JP_PvE?
The recent wipes averaged a busiest count of 45 players. 44 hours after the latest wipe, the crowd peaked.
On what timetable does OKAWAServer_JP_PvE run its wipes?
Too few wipes of OKAWAServer_JP_PvE are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 27 days 3 hours.
Lists and tags
What do the server tags on OKAWAServer_JP_PvE mean?
The game's server browser reads the tags OKAWAServer_JP_PvE publishes: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): Slots: 100; ts16 (Group limit): The team limit is 16; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does OKAWAServer_JP_PvE appear?
You will find OKAWAServer_JP_PvE on the following Rust Server Trends lists: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Connecting
What steps get you onto OKAWAServer_JP_PvE?
To join, enter client.connect 160.251.175.229:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. https://discord.com/invite/mRc2TvcSsA is where its website lives.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.