A129/ 100 players
Modded#9,353
[JP] OServer
Online 162.43.74.201:28025 checked 12m ago
moddedcarbon
players now1of 20 slots
7-day average0peak 1
rank#9,353top 42%
last wipe · restocked6d agono schedule published
next wipe · restock–too few wipes seen yet
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 bestRankRank in region
Top 42% 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.
22.9 daysusual gapbetween real wipes
2wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 7
The first 48 hours of its last wipes
Wed 7 OctMon 14 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 7 Oct, 02:50 UTC6d ago | 1 | – | running | 0 |
| Mon 14 Sep, 06:04 UTC29d 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.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A231/ 200 players
A329/ 100 players
B125/ 100 players
B220/ 100 players
B323/ 100 players
On the back of the pack
Quick answers
From the figures on this page.
Server tags
Can you explain the tags on [JP] OServer?
The server browser reads these tags that [JP] OServer publishes: gmrust (Game mode): The standard survival game mode; mp20 (Max players): The cap is 20; ts8 (Group limit): The default cap is 8 per team; v2634 (Protocol): Protocol 2634: your game must match to get in; cs166652 (Build): Game build: 166652; ptrak (Networking): This is the standard RakNet layer the game uses; $r? (Region code): No region code is set; ^z (Modded): It sits in Modded: plugins or settings make the difference; ^y (Carbon): The plugin framework here is Carbon. Player numbers, queue length and world age are tagged as well, and they sit at the top of this page.
Where does [JP] OServer appear in the lists and filters on Rust Vending Machine?
These Rust Vending Machine lists include [JP] OServer: Modded Rust servers. It shows under these filters 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.
Rules & map
Which map is currently on [JP] OServer?
[JP] OServer runs a procedural map of size 1,500 with seed 1337, generated by the game. From this page you can look at it on RustMaps: the same size and seed give the same map. The map goes by: Custom Map.
Which settings and rules apply on [JP] OServer?
No gather rate is given in the name of [JP] OServer. The group limit is 8 players, the game's default. survival is the game mode, gather, build, raid: the standard game. Player versus player combat and raiding are on. Plugins or settings change the game, so it is listed under Modded. Carbon plugins are running on it. VAC is on.
Server details
What is the location of [JP] OServer?
Without a region tag, [JP] OServer's name still points to Asia. A server's stated location is what Rust Vending Machine shows; the actual machine location is not looked up. Find it at this address: 162.43.74.201:28025.
How stable is [JP] OServer, and is it currently online?
You can grab [JP] OServer: it is online as we speak. The uptime counter points to a restart about 2 hours ago. Over 7 full days, the shelves were stocked for 168 of 168 hours (100%). Its first record on Rust Vending Machine is dated 13 September 2026.
What is the performance like on [JP] OServer?
The 48-hour average for server fps is 228, and the floor was 143. The entity count reached 4,929: that includes buildings, deployables and everything else. The highest memory reading was 1,389 MB. What players call lag comes from low fps and an entity count on the rise.
What version does [JP] OServer use?
The setup: [JP] OServer on Linux, Rust network protocol 2634 and build 166652. The protocol has to line up on your side to join, and Steam does the updating.
Player count
Where does [JP] OServer sit in the rankings?
The last seven days of player hours place [JP] OServer at #9,353, in the top 42% of all ranked servers.
Is [JP] OServer busy at the moment?
You will find 1 players filling 20 slots in [JP] OServer as things stand. The seven-day average stands at 0 players, peaking at 1. Its busiest point in the last 48 hours was 11:00 UTC, averaging 1 players.
Wipe schedule
How often does [JP] OServer wipe?
Too few wipes of [JP] OServer are recorded to tell what its rhythm is. On Thursday 5 November at 19:00 UTC the monthly force wipe comes, and every Rust server wipes. 6 days 19 hours ago it made the world it is using now.
How does [JP] OServer handle wipe day?
The average busiest point of its recent wipes was 2 players. Peak crowd on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 7 the crowd had dropped below half in the wipes that failed to hold.
Getting in
What steps do you take to join [JP] OServer?
Open Rust and press F1 for the console, then type client.connect 162.43.74.201:28025. Or use the Launch Rust button here to open the game through Steam and connect.
Server tags
what each one meansPublished as mp20,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y
Game
gmrust
Game mode The standard survival game mode.
mp20
Max players The cap is 20.
ts8
Group limit The default cap is 8 per team.
v2634
Protocol Protocol 2634: your game must match to get in.
cs166652
Build Game build: 166652.
ptrak
Networking This is the standard RakNet layer the game uses.
$r?
Region code No region code is set.
Mods and access
^z
Modded It sits in Modded: plugins or settings make the difference.
^y
Carbon The plugin framework here 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.