[JP] Rust Classic|PVE
Online 160.251.212.246:28015 checked 12m 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
daily · 1 is bestTop 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 21d 19h. The force wipe · high confidence
Coming wipes
- 21d 19hThu 5 Nov, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 17 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 20:43 UTC FW13d ago | 2 | – | running | 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.
Quick answers
From the figures on this page.
Server tags
What is the meaning of the tags on [JP] Rust Classic|PVE?
The server browser reads these tags that [JP] Rust Classic|PVE publishes: gmrust (Game mode): Survival as standard Rust plays; mp30 (Max players): The cap is 30; ts8 (Group limit): The default cap is 8 per team; v2634 (Protocol): To join, your game version must line up with protocol 2634; cs167058 (Build): Game build: 167058; ptrak (Networking): The game's usual network layer, RakNet, is used; $r? (Region code): No region code is set; ^p (PvE): The world supplies the danger, not other players; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): It sits in Modded: plugins or settings make the difference. You will find its live player count, queue and world creation time in the tags too, displayed at the top here.
On Rust Vending Machine, which lists and filters can you find [JP] Rust Classic|PVE in?
The Rust Vending Machine lists that feature [JP] Rust Classic|PVE are: Modded Rust servers and PvE Rust servers in stock. These filters bring it up on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
Which map is currently on [JP] Rust Classic|PVE?
[JP] Rust Classic|PVE runs a procedural map of size 3,750 with seed 712011, generated by the game. You can view it on RustMaps from this page, since the same size and seed give the same map.
What rules does [JP] Rust Classic|PVE enforce, and what settings does it run?
The name of [JP] Rust Classic|PVE gives no gather rate. 8 players is the default group size, and that is the cap here. pve is the game mode, no player-versus-player fighting. The server browser lists it as Modded: plugins or settings alter the game. Oxide plugins are running on it. VAC is on.
Server info
What is the location of [JP] Rust Classic|PVE?
Without a region tag, [JP] Rust Classic|PVE'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: 160.251.212.246:28015.
How stable is [JP] Rust Classic|PVE, and is it currently online?
Open for trade right now: [JP] Rust Classic|PVE is online. By its own uptime report, the last restart was about 1 hours ago. 168 of 168 hours online over the last 7 full days, or 100% uptime. It came to Rust Vending Machine's notice on 13 September 2026.
Is [JP] Rust Classic|PVE lag-free?
The 48-hour average for server fps is 59, and the floor was 42. Up to 74,337 entities were in play, buildings, deployables and the rest of the world combined. Memory use peaked at 2,411 MB. What players call lag comes from low fps and an entity count on the rise.
What Rust version does [JP] Rust Classic|PVE run?
On Linux, [JP] Rust Classic|PVE is running Rust network protocol 2634 and build 167058. Joining needs the same protocol on your game; Steam handles the update for you.
Live players
How does [JP] Rust Classic|PVE compare to other Rust servers in the rankings?
The last seven days of player hours place [JP] Rust Classic|PVE at #4,377, in the top 20% of all ranked servers.
How many players are on [JP] Rust Classic|PVE right now?
[JP] Rust Classic|PVE is carrying 1 players on 30 slots at the moment. The seven-day average is 0, and the busiest point reached 4. Its busiest point in the last 48 hours was 14:00 UTC, averaging 3 players.
Wipe schedule
How often does [JP] Rust Classic|PVE wipe?
The force wipe is the only wipe at [JP] Rust Classic|PVE, once a month. Every Rust server wipes at the force wipe, which is its next wipe on Thursday 5 November at 19:00 UTC. The world it has now started 13 days 2 hours ago.
What happens on [JP] Rust Classic|PVE on wipe day?
The average busiest point of its recent wipes was 2 players. The crowd on the latest wipe was at its largest 17 hours after the wipe.
Getting in
What is the way to join [JP] Rust Classic|PVE?
Press F1 in Rust to bring up the console and enter client.connect 160.251.212.246:28015. Alternatively, the Launch Rust option on this page opens Rust via Steam and joins for you. You can find its website at https://discord.com/invite/kxV4cxZmKa.
Server tags
what each one meansPublished as mp30,ptrak,$r?,v2634,^p,gmrust,cs167058,ts8,^o^z
Game
gmrust
mp30
ts8
v2634
cs167058
ptrak
$r?
Gameplay
^p
Mods and access
^o
^z
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.