JP-APOLLO-RUST-PVE-SERVER
Online 219.164.228.12:28015 checked 7m ago
Server instruments
last reading Thu 13:00 UTCPlayers now
4% full 7-day avg7-day peakServer fps
48 h low 30 · below 20 is lag, below 10 is badEntities
48 h range 180,996–203,019 · memory 7,101 MBUptime
16 h 0 min since its last restart, at the last readingPlayers
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 7% 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 7d 3h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 3hFW
- WPT 2Thu 3 Dec, 19:00 UTC35d 3hFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 30, 31 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 23:08 UTC FW27d ago | 30 | – | running | 1 |
| Fri 4 Sep, 08:06 UTC55d ago | 23 | halved by day 13 | 27.6 days | 4 |
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- 38/100
- 19/88
- 15/100
- 16/100
- 13/200
- 12/100
Quick answers
from the figures on this pageReset cycle
What happens on JP-APOLLO-RUST-PVE-SERVER when wipe day comes?
The busiest point of its recent wipes drew 26 players on average. Peak crowd on the latest wipe: 31 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 13 when it didn't.
How often does JP-APOLLO-RUST-PVE-SERVER wipe, and when?
Once a month JP-APOLLO-RUST-PVE-SERVER wipes, with the force wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 27 days 15 hours ago. The tags state a wipe schedule of one wipe a month.
Lists and filters
Which tags does JP-APOLLO-RUST-PVE-SERVER carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts16 (Group limit): Teams are capped at 16; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon from JP-APOLLO-RUST-PVE-SERVER. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does JP-APOLLO-RUST-PVE-SERVER appear in Rust Metrics lists and filters?
Rust Metrics lists featuring JP-APOLLO-RUST-PVE-SERVER: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Occupancy
Where does JP-APOLLO-RUST-PVE-SERVER sit in the rankings?
Ranking for JP-APOLLO-RUST-PVE-SERVER: #1,644 on seven-day player hours, top 7% of all ranked servers.
What player count does JP-APOLLO-RUST-PVE-SERVER carry?
4 of 100 slots are filled on JP-APOLLO-RUST-PVE-SERVER right now. Check: players over seven days. Average 3, peak 14. Average at the busiest hour was 9 players, at 10:00 UTC over the last 48 hours.
Server details
Where does JP-APOLLO-RUST-PVE-SERVER sit?
The name of JP-APOLLO-RUST-PVE-SERVER points to Asia, though it publishes no region tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 219.164.228.12:28015.
What Rust version is JP-APOLLO-RUST-PVE-SERVER on?
Reading: JP-APOLLO-RUST-PVE-SERVER, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for JP-APOLLO-RUST-PVE-SERVER?
Check: fps. Average 48 server fps over the last 48 hours, low of 30. Within range. Peak entity count: 203,019. Buildings, deployables and all else included. Memory peak: 8,526 MB. What players call lag comes from low fps and an entity count on the rise.
What is the uptime on JP-APOLLO-RUST-PVE-SERVER, and is it online?
Check: connection. JP-APOLLO-RUST-PVE-SERVER is online at this moment. By its reported uptime, the last restart was roughly 16 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
How is JP-APOLLO-RUST-PVE-SERVER configured, and what rules are in force?
Reading the name gives no gather rate for JP-APOLLO-RUST-PVE-SERVER. The cap on groups is 16 players. pve, other players are not fought — that is the game mode. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on JP-APOLLO-RUST-PVE-SERVER?
From seed 1739184776, the game generates the procedural map on JP-APOLLO-RUST-PVE-SERVER. Its size is 4,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Join
How can you get onto JP-APOLLO-RUST-PVE-SERVER?
Check: join. Open Rust, press F1, then enter client.connect 219.164.228.12:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://discord.com/invite/9AcbMCKcvd.