Statistical profileOnline
KimagureJP
EA 160.251.205.9:28015 checked 10m ago
Connect to this server
1. Main points
Players now
0/ 30
0% full
7-day average
1
peak 7
Rank
#3,128
top 14% · #281 in EA
Last wipe
2h ago
weekly schedule
Next wipe
6d 4h
Wed 4 Nov, 18:51 UTC
Main points
- There were 0 players on it, 0% of its 30 slots.
- Over the last seven days it averaged 1 players, with a peak of 7.
- It ranks #3,128 of all ranked servers, the top 14%, and #281 in EA, on player hours over the last seven days.
- Its current map went up 2h ago; the next wipe is expected Wednesday 4 November, 18:51 UTC, every 6 days 7 hours.
2. Players
Figure 1: Players on KimagureJP
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 14% of all ranked servers, top 52% in EA. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterna steady gap
Next wipe Wednesday 4 November, 18:51 UTC, in 6d 4h. Every 6 days 7 hours · medium confidence
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
Table 1: Coming wipes
Expected from its own rhythm and the force wipe
| In | Date and time | Kind |
|---|---|---|
| 6d 4h | Wed 4 Nov, 18:51 UTC | Own schedule |
| 7d 4h | Thu 5 Nov, 19:00 UTC | Force wipe FW |
| 12d 12h | Wed 11 Nov, 02:07 UTC | Own schedule |
| 18d 19h | Tue 17 Nov, 09:23 UTC | Own schedule |
| 25d 2h | Mon 23 Nov, 16:40 UTC | Own schedule |
| 31d 9h | Sun 29 Nov, 23:56 UTC | Own schedule |
| 35d 4h | Thu 3 Dec, 19:00 UTC | Force wipe FW |
| 37d 17h | Sun 6 Dec, 07:12 UTC | Own schedule |
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 7, 8 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 2: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 29 Oct, 11:35 UTC2h ago | – | – | running | 1 |
| Fri 23 Oct, 04:19 UTC6d ago | 7 | – | – | 0 |
| Fri 16 Oct, 21:10 UTC12d ago | 8 | halved by day 4 | 6.3 days | 1 |
| Sat 10 Oct, 01:29 UTC19d ago | 8 | halved by day 5 | 6.8 days | 0 |
| Fri 2 Oct, 20:30 UTC26d ago | 6 | halved by day 3 | 7.2 days | 0 |
| Thu 24 Sep, 22:47 UTC34d ago | 11 | halved by day 4 | 7.9 days | 0 |
| Fri 18 Sep, 04:26 UTC41d ago | 10 | held half | 6.8 days | 2 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of KimagureJP
3500 · seed 18922
8. Server characteristics
Table 4: Characteristics of KimagureJP
What the server publishes and what was recorded
| 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 |
9. About this server
In its own words: the description the server publishes, unedited.
・一部管理人は建築サーバとして利用しています。飛んでても気にしないでください ・概ねWeeklyですが、気まぐれで前後したりbiweeklyになったりします ・基本的にレイド禁止ですが、最低限の自衛もしていない場合はレイド可能です レイド可能な拠点・設置物 - ほぼ藁のまま1日以上経過している拠点(木強化すらされていない拠点) - 木ドアのまま1日以上経過している拠点 - 風化が始まっている拠点 - 未施錠・ドアなし等、何も破壊せず侵入可能な拠点 - 拠点外に放置されているチェスト、かまど等の設置物 ・ロックドクレートはハッキングをスタートした人がその場に留まっている 場合に限り、その人優先としてください ・サプライシグナルを使った場合のエアドロップは、使った人がその場に 留まっている場合に限り、その人優先としてください ・タレットは設置可能ですが、内向きに設置する等 通行人を無差別に 攻撃しないようにしてください ・施錠されていない車が放置されている場合は乗って行っても構いませんが ミニコプや馬等の仕様上施錠できない乗り物は勝手に持ち去らないように してください ・違反を確認した場合、管理人やその代理が予告なくBANすることがあります ・上記ルールは前提としつつも、最低限の自衛は徹底してください
10. Similar servers
Table 5: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| [SEA]Singapore PVEx20 10/23/26 SkillTree Events | EA · groups of 8+ · weekly · 6 on average | 6 / 50 |
| 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 | EA · groups of 30+ · monthly · 22 on average | 42 / 200 |
| [SEA] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | EA · groups of 8+ · monthly · 17 on average | 30 / 200 |
| JP RustPvE kokuu Server No kill No raid beeginner | EA · groups of 8+ · monthly · 15 on average | 34 / 200 |
| Kiyo Server JP PVE | EA · groups of 20+ · monthly · 5 on average | 9 / 30 |
| [SEA] tRust SG PvE Monthly Vanilla | EA · groups of 8+ · monthly · 5 on average | 3 / 50 |
11. Quick answers
From the figures on this page.
Wipe details
When does KimagureJP wipe, and how often?
Recent wipes of KimagureJP have fallen at intervals of about 6.8 days. Wednesday 4 November at 18:51 UTC is the date of its next wipe. 2 hours have passed since this world was made. The tags list a wipe schedule of one week.
How is wipe day run on KimagureJP?
Recent wipes drew an average peak of 8 players. 8 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the other cases, half the peak was lost by day 4.
About the server
What does the record show for the uptime and current status of KimagureJP?
KimagureJP is online at the time of this release. The uptime it reports puts the last restart at about 35 minutes ago. 167 of 168 hours on across the last 7 full days gives an uptime of 99%. First recorded by Rust Census on 13 September 2026.
What does the performance record of KimagureJP show?
Over the last 48 hours, server fps averaged 46; the lowest reading was 24. The world carried up to 73,459 entities, including buildings, deployables and all else. Memory use reached 3,315 MB at its peak. What players experience as lag is low fps combined with a climbing entity count.
Which location does KimagureJP run from?
Its EA tag is how KimagureJP lists itself in Asia. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. 160.251.205.9:28015 is its address.
Which Rust version is KimagureJP running?
The version in use on KimagureJP is Rust network protocol 2635 and build 168909 on Linux. Steam updates your game for you, but it has to be on the same protocol to join.
Player figures
What population has been recorded on KimagureJP?
At counting time KimagureJP recorded 0 players across 30 slots. This release records a seven-day average of 1 players and a peak of 7. An average of 3 players was recorded at 09:00 UTC, the busiest hour of the last 48.
In the rankings of Rust servers, where is KimagureJP placed?
For seven-day player hours KimagureJP is ranked #3,128 and #281 in Asia, placing it in the top 14% of all ranked servers.
Lists and tags
Which Rust Census filters and lists cover KimagureJP?
The Rust Census lists that KimagureJP fits are: Community servers, Rust PvE servers, listed and Vanilla Rust servers. These filters bring it up on the server list: 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.
Which meanings do the tags on KimagureJP carry?
Read by the game's server browser, KimagureJP publishes these tags: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp30 (Max players): Slots: 30; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): To connect, your game version must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): This server carries no region code; ^w (Weekly): The wipe cycle is weekly; ^v (Vanilla): This is the unmodified game: rates, kits and rules as Facepunch ships them; ^p (PvE): Player-versus-player fighting is off; the world provides the danger; EA (East Asia): East Asia is the region under which the browser lists it. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Rules, map
Which map has been recorded for KimagureJP?
KimagureJP runs a procedural map of size 3,500 with seed 18922, generated by the game. The same size and seed produce the same map; RustMaps shows it from this page.
On KimagureJP, what rules and settings are in force?
No gather rate is given in the name of KimagureJP. 8 players is the group limit, the game's default. pve is the game mode recorded, no fighting other players. It appears under Community in the server browser. Vanilla is its own description: this is the unmodified game: rates, kits and rules as Facepunch ships them. The server runs VAC, Valve's anti-cheat.
Connecting
How can you connect to KimagureJP?
You can open the console in Rust with F1 and enter client.connect 160.251.205.9:28015; or press Launch Rust and join on this page, and you are connected through Steam.
12. Server tags
What each tag this server publishes means: a glossary.
Published asmp30,ptrak,$r?,v2635,^p,^w,^v,EA,gmrust,cs168909,ts8
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp30 | Max players Slots: 30. |
ts8 | Group limit Teams are capped at 8, the default the game ships with. |
v2635 | Protocol To connect, your game version must match protocol 2635. |
cs168909 | Build Game build: 168909. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code This server carries no region code. |
Wipe schedule
^w | Weekly The wipe cycle is weekly. |
|---|
Difficulty
^v | Vanilla This is the unmodified game: rates, kits and rules as Facepunch ships them. |
|---|
Gameplay
^p | PvE Player-versus-player fighting is off; the world provides the danger. |
|---|
Region
EA | East Asia East Asia is the region under which the browser lists it. |
|---|
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.