Online EA 160.251.205.9:28015 checked 10m ago
KimagureJP
Connect
srv = rust.server("160.251.205.9: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 bestTop 14% of all ranked servers, top 51% in EA. Ranked on player hours over the last seven days.
Wipe schedule · a steady gap
srv.wipe_schedule()Next wipe Wednesday 4 November, 18:51 UTC, in 5d 19h. # Every 6 days 7 hours · medium confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 5d 19h | Wed 4 Nov, 18:51 UTC | wipe |
| 1 | 6d 19h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 12d 2h | Wed 11 Nov, 02:07 UTC | wipe |
| 3 | 18d 9h | Tue 17 Nov, 09:23 UTC | wipe |
| 4 | 24d 17h | Mon 23 Nov, 16:40 UTC | wipe |
| 5 | 31d 0h | Sun 29 Nov, 23:56 UTC | wipe |
| 6 | 34d 19h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 37d 7h | Sun 6 Dec, 07:12 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 7, 8 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 29 Oct, 11:35 UTC11h ago | NaN | NaN | running | 1 |
| 1 | Fri 23 Oct, 04:19 UTC6d ago | 7 | NaN | NaN | 0 |
| 2 | Fri 16 Oct, 21:10 UTC13d ago | 8 | halved by day 4 | 6.3 days | 1 |
| 3 | Sat 10 Oct, 01:29 UTC19d ago | 8 | halved by day 5 | 6.8 days | 0 |
| 4 | Fri 2 Oct, 20:30 UTC27d ago | 6 | halved by day 3 | 7.2 days | 0 |
| 5 | Thu 24 Sep, 22:47 UTC35d ago | 11 | halved by day 4 | 7.9 days | 0 |
| 6 | Fri 18 Sep, 04:26 UTC41d ago | 10 | held half | 6.8 days | 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. 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
3500 · seed 18922
- map
- Procedural Map
- size
- 3500
- seed
- 18922
Server
srv.info()- 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
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [SEA]Singapore PVEx20 10/23/26 SkillTree Events | EA · groups of 8+ · weekly · 6 on average | 0/50 |
| 1 | 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 | EA · groups of 30+ · monthly · 22 on average | 2/200 |
| 2 | [SEA] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | EA · groups of 8+ · monthly · 17 on average | 2/200 |
| 3 | JP RustPvE kokuu Server No kill No raid beeginner | EA · groups of 8+ · monthly · 15 on average | 4/200 |
| 4 | Kiyo Server JP PVE | EA · groups of 20+ · monthly · 5 on average | 3/30 |
| 5 | [SEA] tRust SG PvE Monthly Vanilla | EA · groups of 8+ · monthly · 5 on average | 0/50 |
Quick answers
From the figures on this page.
Player counts
How does KimagureJP compare in the rankings?
Player hours over the last seven days: #3,116 for KimagureJP, #275 in Asia, within the top 14% of the ranked set.
What population does KimagureJP carry?
Current row: 1 players on KimagureJP, against 30 slots. Over the last seven days it averaged 1 players and peaked at 7. Averaged by hour over 48 hours, 09:00 UTC is the busiest, at 3 players.
Server data
What does performance look like on KimagureJP?
Averaged over 48 hours: 57 server fps, never under 24. Entity numbers reached 73,459, and that includes buildings, deployables and the rest. A high of 3,315 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does KimagureJP run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by KimagureJP. The protocol has to match before you can join, and Steam does the updating.
Is KimagureJP up, and what does its uptime show?
KimagureJP reports itself online at the current refresh. The uptime it reports puts the last restart about 10 hours ago. 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.
Which location does KimagureJP run from?
With its EA tag, KimagureJP lists itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 160.251.205.9:28015 is its address.
Settings and map
What rules and settings are recorded for KimagureJP?
The name KimagureJP carries no gather rate. No custom cap; the default of 8 players per group stands. pve is the game mode here, and no combat between players. It is a community server, and the browser files it under Community. The description says vanilla, which here means untouched settings: rates, kits and rules as shipped. VAC is running: Valve's anti-cheat is on.
Which map has KimagureJP loaded?
Size 3,500, seed 18922: the procedural map on KimagureJP, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does KimagureJP wipe?
The gap between wipes on KimagureJP has lately averaged about 6.8 days. The schedule puts the next wipe on Wednesday 4 November at 18:51 UTC. The world it runs now was generated 11 hours ago. Its tags carry a weekly wipe schedule.
What is wipe day on KimagureJP like?
Across recent wipes the busiest point averaged 8 players. The crowd on the latest wipe topped out 8 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 4.
Tags and filters
Where does KimagureJP appear among Rust Data lists and filters?
These Rust Data lists include KimagureJP: Rust community servers, unfiltered, Rust PvE servers and Vanilla Rust servers. Under these filters on the server list, it is listed: 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.
How should you read the server tags on KimagureJP?
These tags are published by KimagureJP and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): Slot count: 30; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^w (Weekly): The interval is one week; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^p (PvE): PvE: the world is the threat, not other players; EA (East Asia): In the server browser it sits under East Asia. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into KimagureJP?
Enter client.connect 160.251.205.9:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.