On the class lists: C− (59), with population over 48 hours and no performance mark.
Players now2/ 1002% full
7-day average5peak 17
Rank#1,327top 6%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
5/ 100
F
A quiet classroom so far: 5 of 100 on average. Plenty of space to grow.
Standingrank on player hours
94/ 100
A
Well up the rankings: #1,327 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
63/ 100
C
Slows down under load at times: 38 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
42/ 100
F
Slipped a little: down 209 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 6% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···FW··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.
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
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 UTCFW27d 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
classmates: the same kind of game, then region, group limit, rate and wipes
OKAWAServer_JP_PvE leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 160.251.175.229:28015.
How reliable is OKAWAServer_JP_PvE, and is it up?
Right now, OKAWAServer_JP_PvE is online. According to its reported uptime, the last restart was about 5 days 20 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does OKAWAServer_JP_PvE perform well?
It never fell below 28 server fps in the last 48 hours, averaging 38. Up to 193,067 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 6,964 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does OKAWAServer_JP_PvE sit?
The server OKAWAServer_JP_PvE is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does OKAWAServer_JP_PvE wipe, and how often?
There are too few wipes on record for OKAWAServer_JP_PvE to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 27 days 8 hours.
What should you expect from wipe day on OKAWAServer_JP_PvE?
Recent wipes have peaked at 45 players on average. The crowd on the latest wipe was largest 44 hours after it began.
Population
Where does OKAWAServer_JP_PvE sit among Rust servers?
In the top 6% of all ranked servers, OKAWAServer_JP_PvE sits at #1,327 for player hours over the last seven days.
What does the population on OKAWAServer_JP_PvE look like?
OKAWAServer_JP_PvE is showing 2 players right now, with 100 slots in total. It peaked at 17 and averaged 5 players over the last seven days. The highest average in the last 48 hours came at 14:00 UTC, with 12 players.
Tags
How should you read the tags on OKAWAServer_JP_PvE?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; ts16 (Group limit): No team may go above 16; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server are the tags OKAWAServer_JP_PvE publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does OKAWAServer_JP_PvE appear in the Rust Server Score lists and filters?
Rust Server Score lists that include OKAWAServer_JP_PvE: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does OKAWAServer_JP_PvE enforce, and what are its settings?
The name of OKAWAServer_JP_PvE gives no gather rate. The limit for a group is 16 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on OKAWAServer_JP_PvE?
OKAWAServer_JP_PvE runs a game-generated procedural map at size 4,500, seed 4180011. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to OKAWAServer_JP_PvE?
Enter client.connect 160.251.175.229:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/mRc2TvcSsA.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts16
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
ts16
Group limitNo team may go above 16.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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.
A fair term, with more to come. Strongest in uptime (A+); population is the one to work on (F).