OKAWAServer_JP_PvE
Online 160.251.175.229:28015 checked 7m ago
Server instruments
last reading Thu 18:00 UTCPlayers now
2% full 7-day avg7-day peakServer fps
48 h low 28 · below 20 is lag, below 10 is badEntities
48 h range 187,111–192,823 · memory 5,613 MBUptime
5 days 20 hours since its last restart, at the last readingPlayers
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.
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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 11:17 UTC27d ago | 46 | – | running | 30 |
| Thu 1 Oct, 23:05 UTC FW27d ago | 44 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 283/325
- 347/425
- 895/1000
- 49/100
- 942/1000
- 770/800
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on OKAWAServer_JP_PvE?
An average of 45 players came at the busiest on its recent wipes. 44 hours after the wipe, the crowd peaked on the latest wipe.
When does OKAWAServer_JP_PvE wipe?
To tell the rhythm of OKAWAServer_JP_PvE, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 27 days 8 hours ago the current world was made.
Lists and filters
How should you read the tags on OKAWAServer_JP_PvE?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts16 (Group limit): Team cap: 16; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from OKAWAServer_JP_PvE. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does OKAWAServer_JP_PvE appear in Rust Metrics lists and filters?
These Rust Metrics lists carry OKAWAServer_JP_PvE: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does OKAWAServer_JP_PvE sit in the rankings?
Player hours over seven days put OKAWAServer_JP_PvE at #1,330, in the top 6% of all ranked servers.
What is the population on OKAWAServer_JP_PvE?
Current headcount on OKAWAServer_JP_PvE: 2 players, 100 slots available. Seven-day check: 5 players on average. Peak reading: 17. Average at the busiest hour was 12 players, at 14:00 UTC over the last 48 hours.
Server details
Where does OKAWAServer_JP_PvE sit?
Reading: location. OKAWAServer_JP_PvE gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 160.251.175.229:28015.
What Rust version is OKAWAServer_JP_PvE on?
Rust network protocol 2635 and build 168909 on Linux is the build OKAWAServer_JP_PvE runs. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for OKAWAServer_JP_PvE?
Check: fps. Average 38 server fps over the last 48 hours, low of 28. Within range. Peak entity count: 192,823. Buildings, deployables and all else included. Memory peak: 6,964 MB. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on OKAWAServer_JP_PvE, and is it online?
Reading: online. OKAWAServer_JP_PvE answers right now. By its reported uptime, the last restart was roughly 5 days 20 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
How is OKAWAServer_JP_PvE configured, and what rules are in force?
Check: gather rate. The name OKAWAServer_JP_PvE does not state one. Group size, maximum: 16 players. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on OKAWAServer_JP_PvE?
Size 4,500 and seed 4180011: the game generates the procedural map on OKAWAServer_JP_PvE from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Connection
What do you do to join OKAWAServer_JP_PvE?
Check: join. Open Rust, press F1, then enter client.connect 160.251.175.229:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://discord.com/invite/mRc2TvcSsA.