[JP] OServer
162.43.74.201:28025 checked 13m ago
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
Top 42% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 22.9 days between real wipes
- wipe-day peak
- 2 players, last three wipes
- crowd held
- 0% else halves by day 7
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 7 Oct, 02:50 UTC 6d ago | 1 | – | running | 0 |
| Mon 14 Sep, 06:04 UTC 29d ago | 2 | halved by day 7 | 22.9 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
Quick answers
Population
How busy is [JP] OServer?
The current population of [JP] OServer is 1 out of 20 slots. A seven-day average of 0 players, with a peak of 1. The busiest time in the last 48 hours was 11:00 UTC, when the average was 1 players.
How does [JP] OServer rank against other Rust servers?
Over the last seven days, [JP] OServer is #9,353 for player hours, placing it in the top 42% of ranked servers globally.
Wipe schedule
What does wipe day look like on [JP] OServer?
The busiest points of its recent wipes drew 2 players on average. On the latest wipe, 0 hours passed before the crowd peaked. Half that peak or more was held until the next wipe in 0% of its recent wipes. If it did not hold, that half mark was passed by day 7.
What is the wipe schedule on [JP] OServer?
The rhythm of [JP] OServer cannot yet be told: too few of its wipes are on record. The monthly force wipe, next on Thursday 5 November at 19:00 UTC, wipes every Rust server. 6 days 19 hours is how long the present world has lasted.
Server details
Is [JP] OServer online, and how reliable is it?
Right now [JP] OServer is up and online. It reports an uptime that puts the last restart at about 3 hours ago. 168 of 168 hours were online in the last 7 full days, 100% uptime. When Is Wipe has tracked it since 13 September 2026.
Performance of [JP] OServer: does it run smoothly?
Over the past 48 hours, it averaged 228 server fps, with a minimum of 143. Buildings, deployables and other world objects pushed the entity count as high as 4,929. The peak memory usage was 1,389 MB. Low fps together with an increasing entity count is what players call lag.
Which version of Rust does [JP] OServer run?
On [JP] OServer, the Rust version is network protocol 2634 and build 166652 and the OS is Linux. Steam updates your game, so the protocol matches when you join.
Where is [JP] OServer located?
Its name points to Asia, though [JP] OServer publishes no region tag. What When Is Wipe shows is where a server says it is, not where the machine stands, which it does not look up. You can reach it at 162.43.74.201:28025.
Lists and tags
Which When Is Wipe lists include [JP] OServer? And filters?
The When Is Wipe lists [JP] OServer fits are: Best modded Rust servers. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
What do the server tags on [JP] OServer mean?
The game's server browser reads the tags [JP] OServer publishes: gmrust (Game mode): Standard survival is the game mode; mp20 (Max players): Slot count: 20; ts8 (Group limit): Default team size applies: 8 maximum; v2634 (Protocol): Your game version has to be on protocol 2634 to connect; cs166652 (Build): This server runs build 166652; ptrak (Networking): RakNet is the network layer in use here, as standard for the game; $r? (Region code): A region code is not set for this server; ^z (Modded): Listed under Modded, with plugins or changed settings; ^y (Carbon): The plugin framework is Carbon. At the top of this page you can see its current players, queue and world creation time, which are in the tags too.
Rules, map
What rules does [JP] OServer enforce? And settings?
[JP] OServer's name makes no mention of a gather rate. With the default limit, groups are limited to 8 players. On this server, the mode is survival, standard survival: gathering, building, raiding. You can fight and raid other players. It is in the Modded section: plugins or settings alter the game. Plugins: Carbon. VAC is on.
Which map does [JP] OServer run?
A procedural map, size 1,500 with seed 1337, is used by [JP] OServer; the game generates it. The map is fixed by size and seed; view it on RustMaps from this page. On the map name: Custom Map.
How to join
How do I join [JP] OServer?
Open Rust, press F1, and type client.connect 162.43.74.201:28025 in the console. Alternatively, use Launch Rust on this page to open the game via Steam and connect.
Server tags
Published as mp20,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y
Game
gmrust- Game mode Standard survival is the game mode.
mp20- Max players Slot count: 20.
ts8- Group limit Default team size applies: 8 maximum.
v2634- Protocol Your game version has to be on protocol 2634 to connect.
cs166652- Build This server runs build 166652.
ptrak- Networking RakNet is the network layer in use here, as standard for the game.
$r?- Region code A region code is not set for this server.
Mods and access
^z- Modded Listed under Modded, with plugins or changed settings.
^y- Carbon The plugin framework is Carbon.
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.