StatusLive Servers online11,792 Players68,594 Populated3,568 Wiped · 3 h191 Interval5 min Date29 OCT 2026

DWG RG-S3145Server sheetchecked 13m ago

KimagureJP

Online EA 160.251.205.9:28015 checked 13m ago

weekly wipes vanillapve
Connect
Players now 0/ 30 0% full
7-day average1peak 7
Rank#3,145top 14% · #284 in EA
Last wipe1h agoweekly schedule
Next wipe6d 5hWed 4 Nov, 18:51 UTC
Fig. 1

Players

AveragePeak
0123413:0022:0007:0015:0001:0011:00

Hourly average and peak, UTC.

Fig. 1Players on KimagureJP
Fig. 2

Server performance

02040608013:0022:0007:0015:0001:0011:00

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 14% of all ranked servers, top 52% in EA. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

a steady gap

Next wipe Wednesday 4 November, 18:51 UTC, in 6d 5h. Every 6 days 7 hours · medium confidence

usual gap6.8 daysbetween real wipes
on rhythm83%of its recent wipes
wipe-day peak8players, last three wipes
crowd held0%else halves by day 4

Coming wipes

  1. 6d 5hWed 4 Nov, 18:51 UTC
  2. 7d 6hThu 5 Nov, 19:00 UTCFW
  3. 12d 13hWed 11 Nov, 02:07 UTC
  4. 18d 20hTue 17 Nov, 09:23 UTC
  5. 25d 3hMon 23 Nov, 16:40 UTC
  6. 31d 11hSun 29 Nov, 23:56 UTC
  7. 35d 6hThu 3 Dec, 19:00 UTCFW
  8. 37d 18hSun 6 Dec, 07:12 UTC

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctSat 10 Oct
02468+0h+9h+19h+28h+38h+47h
Fig. 4Players 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.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 11:35 UTC1h 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

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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
[SEA]Singapore PVEx20 10/23/26 SkillTree EventsEA · groups of 8+ · weekly · 6 on average
6 / 50
02
【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍EA · groups of 30+ · monthly · 22 on average
41 / 200
03
[SEA] RustEZ Pure PvE | Low Decay | No Killing | No RaidingEA · groups of 8+ · monthly · 17 on average
24 / 200
04
JP RustPvE kokuu Server No kill No raid beeginnerEA · groups of 8+ · monthly · 15 on average
26 / 200
05
Kiyo Server JP PVEEA · groups of 20+ · monthly · 5 on average
12 / 30
06
[SEA] tRust SG PvE Monthly VanillaEA · groups of 8+ · monthly · 5 on average
4 / 50
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is KimagureJP online, and what uptime has been recorded?

KimagureJP is up at this moment. About 5 days 11 hours ago is when it last restarted, measured from the uptime it reports. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.

How does KimagureJP perform, as measured?

The last 48 hours give an average of 44 server fps and a floor of 24. Counted at its highest: 73,459 entities, buildings, deployables and the rest of the world included. 3,315 MB is the memory peak. A climbing entity count and low fps are the source of what players feel as lag.

In which location is KimagureJP hosted?

With its EA tag, KimagureJP lists itself in Asia. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 160.251.205.9:28015.

On which Rust version is KimagureJP running?

Rust network protocol 2635 and build 168909 on Linux: that is what KimagureJP runs. To join, your game must be on the same protocol; Steam handles the update.

Player data

What player count is recorded on KimagureJP?

At the last refresh, KimagureJP recorded 0 players across 30 slots. Averaged across seven days, the player count is 1, with a peak of 7. The 48-hour peak falls at 09:00 UTC, averaging 3 players.

Against other Rust servers, where is KimagureJP placed?

The same seven-day player-hour count places KimagureJP at #284 within Asia, #3,145 across all ranked servers and in the top 14% of them.

Wipe data

On KimagureJP, what does the data show for wipe day?

The recent wipes averaged a busiest count of 8 players. At 8 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 4.

On KimagureJP, when do wipes occur?

About every 6.8 days is how often KimagureJP has wiped lately. Wednesday 4 November at 18:51 UTC is the date its next wipe is due. 1 hours ago the current world was made. A wipe every week is the schedule its tags set out.

Rules and settings

Which settings does KimagureJP run, and what rules?

The name of KimagureJP records no gather rate. No limit is published beyond the default: 8 players per group. It runs the pve game mode, no fighting other players. The server browser lists it under Community. It describes itself as vanilla, by which it means rates, kits and rules are unchanged from Facepunch's release. Anti-cheat: VAC, from Valve, is on.

What is the map for KimagureJP?

Seed 18922 and size 3,500 define the procedural map KimagureJP generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

Where does KimagureJP appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry KimagureJP are: Rust community servers, plotted, PvE Rust servers, plotted and Vanilla Rust servers. These filters on the server list return it: 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.

On KimagureJP, what is meant by each tag?

gmrust (Game mode): Standard survival, as Rust plays; mp30 (Max players): The slot count is 30; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^w (Weekly): Every week it wipes; ^v (Vanilla): Rates, kits and rules are unchanged from Facepunch's release; ^p (PvE): The world is the danger; players do not fight each other; EA (East Asia): The server browser lists it under East Asia are the tags KimagureJP publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Connect

What is the way to connect to KimagureJP?

Enter client.connect 160.251.205.9:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp30,ptrak,$r?,v2635,^p,^w,^v,EA,gmrust,cs168909,ts8

Game

gmrust
Game mode Standard survival, as Rust plays.
mp30
Max players The slot count is 30.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code Region code not set.

Wipe schedule

^w
Weekly Every week it wipes.

Difficulty

^v
Vanilla Rates, kits and rules are unchanged from Facepunch's release.

Gameplay

^p
PvE The world is the danger; players do not fight each other.

Region

EA
East Asia The server browser lists it 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.

KeyTag string decoded