KimagureJP
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 8m ago · 160.251.205.9:28015
Abstract
We describe the public Rust server KimagureJP, reached at 160.251.205.9:28015 and hosted in EA. At the last check it held 0 of 30 places, against a seven-day mean of 1 and a peak of 71. It ranks #3,133 of all servers, the top 14%, and #284 in EA. It last wiped 1h ago on a published weekly schedule; the next wipe is expected Wednesday 4 November, 18:51 UTC, every 6 days 7 hours.
Keywordsweekly wipes vanilla pve
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 14% of all ranked servers, the top 52% in EA. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: a steady gap
The next wipe is expected Wednesday 4 November, 18:51 UTC, in 6d 5h. Every 6 days 7 hours (medium confidence).
| Measure | Value | Note |
|---|---|---|
| Usual gap | 6.8 days | between real wipes |
| On rhythm | 83% | of its recent wipes |
| Wipe-day peak | 8 | players, last three wipes |
| Crowd held | 0% | else halves by day 4 |
| When (UTC) | In | Kind |
|---|---|---|
| Wed 4 Nov, 18:51 | 6d 5h | its own schedule |
| Thu 5 Nov, 19:00 | 7d 5h | force wipefw |
| Wed 11 Nov, 02:07 | 12d 12h | its own schedule |
| Tue 17 Nov, 09:23 | 18d 19h | its own schedule |
| Mon 23 Nov, 16:40 | 25d 3h | its own schedule |
| Sun 29 Nov, 23:56 | 31d 10h | its own schedule |
| Thu 3 Dec, 19:00 | 35d 5h | force wipefw |
| Sun 6 Dec, 07:12 | 37d 17h | its own schedule |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Thu 29 Oct, 11:351h ago | – | – | running | 1 |
| Fri 23 Oct, 04:196d ago | 7 | – | – | 0 |
| Fri 16 Oct, 21:1012d ago | 8 | halved by day 4 | 6.3 d | 1 |
| Sat 10 Oct, 01:2919d ago | 8 | halved by day 5 | 6.8 d | 0 |
| Fri 2 Oct, 20:3026d ago | 6 | halved by day 3 | 7.2 d | 0 |
| Thu 24 Sep, 22:4734d ago | 11 | halved by day 4 | 7.9 d | 0 |
| Fri 18 Sep, 04:2641d ago | 10 | held half | 6.8 d | 2 |
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 160.251.205.9:28015 |
|---|---|
| Region | EA |
| Max players | 30 |
| Group limit | 8, the default |
| Wipe schedule | weekly |
| Last wipe | 29 Oct 2026, 11:35 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Procedural Map |
| Size | 3500 |
| Seed | 18922 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are community tab servers measured [2], pve wipes and settings [3], vanilla rust servers [4] and servers wiping soon [5].
| Server | Players |
|---|---|
| [SEA]Singapore PVEx20 10/23/26 SkillTree EventsEA · groups of 8+ · weekly · 6 on average | 7/50 |
| 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍EA · groups of 30+ · monthly · 22 on average | 43/200 |
| [SEA] RustEZ Pure PvE | Low Decay | No Killing | No RaidingEA · groups of 8+ · monthly · 17 on average | 24/200 |
| JP RustPvE kokuu Server No kill No raid beeginnerEA · groups of 8+ · monthly · 15 on average | 29/200 |
| Kiyo Server JP PVEEA · groups of 20+ · monthly · 5 on average | 10/30 |
| [SEA] tRust SG PvE Monthly VanillaEA · groups of 8+ · monthly · 5 on average | 5/50 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1How well does KimagureJP run?
Over the past 48 hours, it ran at an average of 44 server fps, with a low of 24. Its entity count reached a maximum of 73,459, including buildings, deployables and all other world objects. The peak memory usage was 3,315 MB. When fps is low and entity count climbs, players feel lag.
A.2In which location is KimagureJP based?
The EA tag places KimagureJP in Asia, as it lists itself. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 160.251.205.9:28015.
A.3What is the reliability of KimagureJP, and is it online?
KimagureJP is online at this time. The uptime it reports indicates a restart about 5 days 11 hours ago. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first observed on 13 September 2026 by Rust Statistics.
A.4What is the Rust version for KimagureJP?
Rust network protocol 2635 and build 168909 is the version that KimagureJP runs, on Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe timing
A.5When are wipes carried out on KimagureJP?
Over recent wipes, KimagureJP has averaged an interval of about 6.8 days. On Wednesday 4 November at 18:51 UTC the next wipe is expected. 1 hours have passed since the current world was generated. According to its tags, the server wipes on a weekly schedule.
A.6What characterises wipe day on KimagureJP?
Across its recent wipes, the average peak population was 8 players. The peak on the latest wipe came 8 hours after it began. The crowd stayed above half its peak until the next wipe in 0% of recent wipes. In the other cases, the population fell below half by day 4.
Population
A.7What position does KimagureJP occupy in the ranking of Rust servers?
On player hours over seven days KimagureJP is #3,133, within the top 14% of all ranked servers; within Asia it is #284.
A.8How would you characterise the player activity on KimagureJP?
The current population of KimagureJP is 0, drawn from 30 slots. The peak over seven days is 7, against an average of 1. Of the last 48 hours, the peak hour falls at 09:00 UTC, with an average of 3 players.
Tags, lists
A.9What do the tags associated with KimagureJP signify?
gmrust (Game mode): Rust survival, in its standard form; mp30 (Max players): 30 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^w (Weekly): Wipes happen every week; ^v (Vanilla): Nothing is changed from Facepunch's release: rates, kits and rules are as shipped; ^p (PvE): The threat is the world, not other players; EA (East Asia): In the server browser it is filed under East Asia: these are the tags KimagureJP publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.
A.10Where can KimagureJP be found among the Rust Statistics lists and filters?
These Rust Statistics lists include KimagureJP: Rust community servers, measured, Rust PvE servers: live list and Vanilla Rust servers. You will find it on the server list filtered by: Region: Asia; Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Weekly ^w, Vanilla ^v and PvE ^p; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours.
Rules, settings, map
A.11Which settings and rules are in force on KimagureJP?
Its name carries no gather rate for KimagureJP. The group cap is 8 players, which is the default in the game. pve is the game mode here; fighting other players is excluded. The server browser lists it under Community. It describes itself as vanilla, which is to say nothing is changed from Facepunch's release: rates, kits and rules are as shipped. VAC, Valve's anti-cheat, is enabled.
A.12What is the map for KimagureJP?
Size 3,500 and seed 18922 define the procedural, game-generated map on KimagureJP. Because size and seed determine the map, RustMaps can show it, linked from this page.
How to join
A.13How do you connect to KimagureJP?
Press F1 inside Rust to open the console and enter client.connect 160.251.205.9:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.
Appendix BServer tags
What each of the server's tags means. Published as mp30,ptrak,$r?,v2635,^p,^w,^v,EA,gmrust,cs168909,ts8.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Rust survival, in its standard form. |
mp30 | Max players. 30 slots are available. |
ts8 | Group limit. 8 per team, the value the game sets by default. |
v2635 | Protocol. Joining requires the same game version: protocol 2635. |
cs168909 | Build. Build 168909 is the one running. |
ptrak | Networking. Networking runs on RakNet, the game's standard layer. |
$r? | Region code. The region code is unset. |
| Wipe schedule | |
^w | Weekly. Wipes happen every week. |
| Difficulty | |
^v | Vanilla. Nothing is changed from Facepunch's release: rates, kits and rules are as shipped. |
| Gameplay | |
^p | PvE. The threat is the world, not other players. |
| Region | |
EA | East Asia. In the server browser it is filed under East Asia. |
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.
Appendix CAbout this server, in its own words
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Community tab servers measured. ruststatistics.org/top-rust-community-servers.
- [3]Rust Statistics. Pve wipes and settings. ruststatistics.org/top-rust-pve-servers.
- [4]Rust Statistics. Vanilla rust servers. ruststatistics.org/top-vanilla-rust-servers.
- [5]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.