Offline 162.43.50.87:28015 checked 27d ago
PVE Rust Server JP
Connect
srv = rust.server("162.43.50.87:29015")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 24 Sep, 15:54 UTC33d ago | 1 | NaN | running | 1 |
# 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.
display(srv.map, srv.info())Map
3500 · seed 50000
- map
- Procedural Map
- size
- 3500
- seed
- 50000
Server
srv.info()- address
- 162.43.50.87:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 15:54 UTC
- hostname
- –
- first seen
- 24 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rustoria.co - SEA Main | EA · groups of 16+ · weekly · 181 on average | 53/200 |
| 1 | Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com | EA · groups of 16+ · weekly · 118 on average | 31/550 |
| 2 | Rustoria.co - SEA Long | EA · groups of 12+ · monthly · 108 on average | 111/200 |
| 3 | Rustafied.com - SEA Main | EA · groups of 16+ · weekly · 87 on average | 22/100 |
| 4 | Rustoria.co - SEA Medium | JUST WIPED 28.10 | EA · no group limit · 65 on average | 50/100 |
| 5 | Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] | EA · groups of 8+ · weekly · 51 on average | 17/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does PVE Rust Server JP rank?
Over the last seven days PVE Rust Server JP sits at #16,728 on player hours, in the top 70% of ranked servers.
What population does PVE Rust Server JP carry?
The current row shows PVE Rust Server JP offline; the last response was 27 days 12 hours ago.
Server data
What is the Rust version on PVE Rust Server JP?
Rust network protocol 2633 and build 165217 on Linux is what PVE Rust Server JP runs. Steam updates your game for you, but the protocol must match to join.
How reliable is PVE Rust Server JP, and is it up?
The latest sample has PVE Rust Server JP offline, with a last sighting 27 days 12 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 24 September 2026.
Which location does PVE Rust Server JP run from?
No region tag is published by PVE Rust Server JP, though its name points to Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 162.43.50.87:28015.
Map and rules
What rules and settings are recorded for PVE Rust Server JP?
No gather rate appears in the name: PVE Rust Server JP. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Community is its browser category. Anti-cheat status: VAC on.
Which map has PVE Rust Server JP selected?
Size 3,500, seed 50000: the procedural map on PVE Rust Server JP, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does PVE Rust Server JP wipe, and on what schedule?
A rhythm cannot be read from the wipes of PVE Rust Server JP on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 33 days 17 hours ago, and that is the one in play.
On PVE Rust Server JP, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which lists on Rust Data hold PVE Rust Server JP, and which filters?
These Rust Data lists include PVE Rust Server JP: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on PVE Rust Server JP?
The game's server browser reads these tags from PVE Rust Server JP: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): The server runs build 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to PVE Rust Server JP?
In Rust, F1 opens the console: type client.connect 162.43.50.87:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.