Online 219.164.228.12:28015 checked 10m ago
JP-APOLLO-RUST-PVE-SERVER
Connect
srv = rust.server("219.164.228.12:28017")
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 17 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 best
Top 7% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 23h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 23:08 UTC FW27d ago | 30 | NaN | running | 1 |
| 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.
display(srv.map, srv.info())
Map
4500 · seed 1739184776
- map
- Procedural Map
- size
- 4500
- seed
- 1739184776
Server
srv.info()- address
- 219.164.228.12:28015
- region
- –
- max players
- 100
- group limit
- 16 max
- wipe schedule
- monthly
- last wipe
- 1 Oct 2026, 23:08 UTC
- hostname
- –
- first seen
- 13 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 | [坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱 | EA · groups of 8+ · monthly · 34 on average | 26/100 |
| 1 | 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 18/88 |
| 2 | [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 | EA · groups of 8+ · monthly · 12 on average | 13/100 |
| 3 | [JP]ちょっぴりHard-PvE RiSu Server | EA · groups of 8+ · monthly · 11 on average | 6/100 |
| 4 | 【青岩-PVE服】原倍/萌新/突袭据点 | EA · groups of 8+ · monthly · 11 on average | 2/200 |
| 5 | 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 | EA · groups of 16+ · monthly · 10 on average | 8/100 |
Quick answers
From the figures on this page.
Population data
What position does JP-APOLLO-RUST-PVE-SERVER take in the server rankings?
Over the last seven days JP-APOLLO-RUST-PVE-SERVER sits at #1,627 on player hours, in the top 7% of ranked servers.
What population does JP-APOLLO-RUST-PVE-SERVER carry?
Current row: 3 players on JP-APOLLO-RUST-PVE-SERVER, against 100 slots. Over the last seven days it averaged 3 players and peaked at 14. Averaged by hour over 48 hours, 10:00 UTC is the busiest, at 9 players.
Server data
How smoothly does JP-APOLLO-RUST-PVE-SERVER run?
Averaged over 48 hours: 48 server fps, never under 26. The entity count peaked at 203,019, covering buildings, deployables and the rest of the world. A high of 8,526 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does JP-APOLLO-RUST-PVE-SERVER run?
Rust network protocol 2635 and build 168909 on Windows is what JP-APOLLO-RUST-PVE-SERVER runs. The protocol has to match before you can join, and Steam does the updating.
Is JP-APOLLO-RUST-PVE-SERVER up, and what does its uptime show?
The current sample puts JP-APOLLO-RUST-PVE-SERVER online. Count back 21 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is JP-APOLLO-RUST-PVE-SERVER hosted?
Its name points to Asia, but JP-APOLLO-RUST-PVE-SERVER publishes no region tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 219.164.228.12:28015 is its address.
Map and rules
Which rules apply on JP-APOLLO-RUST-PVE-SERVER, and what settings?
You will not find a gather rate in the string JP-APOLLO-RUST-PVE-SERVER. 16 players is the maximum per group. Recorded as pve, no combat between players. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.
Which map has JP-APOLLO-RUST-PVE-SERVER loaded?
Size 4,500, seed 1739184776: the procedural map on JP-APOLLO-RUST-PVE-SERVER, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does JP-APOLLO-RUST-PVE-SERVER wipe, and on what schedule?
A single wipe each month, the force wipe, is all JP-APOLLO-RUST-PVE-SERVER does. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 27 days 20 hours ago, and that is the one in play. The tags list wipes as monthly.
On JP-APOLLO-RUST-PVE-SERVER, what happens on wipe day?
Across recent wipes the busiest point averaged 26 players. 31 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 13.
Tags, lists
Where does JP-APOLLO-RUST-PVE-SERVER appear among Rust Data lists and filters?
On Rust Data, JP-APOLLO-RUST-PVE-SERVER appears in these lists: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: 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.
How should you read the server tags on JP-APOLLO-RUST-PVE-SERVER?
Read by the game's server browser, the tags JP-APOLLO-RUST-PVE-SERVER publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts16 (Group limit): No team may exceed 16; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): PvE: the world is the threat, not other players; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into JP-APOLLO-RUST-PVE-SERVER?
Enter client.connect 219.164.228.12:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://discord.com/invite/9AcbMCKcvd.