RUST METRICSFlight deck · live data
Data live Servers11,644 Players43,541 Populated3,049 Fresh wipes 3 h97 Scan5 min
‹ All servers160.251.205.9:28015
Online Full Queue Fresh wipe Wipe due No query

KimagureJP

Online EA 160.251.205.9:28015 checked 12m ago

quad weekly wipes softcore
COM 1 · connect

Server instruments

last reading Thu 07:00 UTC
0 8 15 22 30 PAX 0 /30

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 52 SERVER FPS

Server fps

48 h low 24 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 71,323 ×1000

Entities

48 h range 71,009–73,459 · memory 2,665 MB
1239 ET SINCE RESTART 5D 09H

Uptime

5 days 9 hours since its last restart, at the last reading
7-day average1peak 7
Rank#3,148top 14% · #285 in EA
Last wipe6d agoweekly schedule
Next wipe15hThu 29 Oct, 23:59 UTC
Memory2,665MB48 h peak 4 players
REC 1

Players

AveragePeak
0123409:0018:0003:0012:0022:0007:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608009:0018:0003:0012:0022:0007: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.

REC 3

Rank

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

Top 14% of all ranked servers, top 51% in EA, and #199 of the quad servers (top 24%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

a steady gap

Next wipe Thursday 29 October, 23:59 UTC, in 15h. Every 6 days 20 hours · medium confidence

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

Coming wipes

  1. WPT 1Thu 29 Oct, 23:59 UTC15h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 10hFW
  3. WPT 3Thu 12 Nov, 15:21 UTC14d 6h
  4. WPT 4Thu 19 Nov, 11:01 UTC21d 2h
  5. WPT 5Thu 26 Nov, 06:42 UTC27d 22h
  6. WPT 6Thu 3 Dec, 19:00 UTC35d 10hFW
  7. WPT 7Wed 9 Dec, 22:03 UTC41d 13h

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctSat 10 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 7, 8 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 04:19 UTC6d ago 7 – running 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on KimagureJP?

An average of 8 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 8 hours in. The crowd stayed above half that peak until the next wipe in 20% of its recent wipes. When it didn't hold, by day 4 it fell below half.

How often does KimagureJP wipe, and when?

The recent wipe interval on KimagureJP is about 6.8 days. Thursday 29 October at 23:59 UTC is when its next wipe is due. The world in play was created 6 days 4 hours ago. The tags state a wipe schedule of one wipe a week.

Tags

How should you read the tags on KimagureJP?

Check: tags. The game's server browser reads gmsoftcore (Game mode): Check: ruleset. Softcore, the easier option; mp30 (Max players): The server holds 30 slots; ts4 (Group limit): Teams are capped at 4; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^w (Weekly): It wipes each week; EA (East Asia): East Asia is the browser category it sits in from KimagureJP. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show KimagureJP?

These Rust Metrics lists carry KimagureJP: Rust community servers: live readings. Reading: server list filters. It comes up under Region: Asia; Type: Community (not modded, not official) and No plugins at all; Game mode: Softcore; Server tag: Weekly ^w; Group limit: Quad; Wipe schedule: Weekly; Last wipe: In the last week.

Occupancy

Where does KimagureJP sit in the rankings?

Ranked by seven-day player hours, KimagureJP sits at #3,148 and #285 in Asia, inside the top 14%. The quad group places it at #199.

How full does KimagureJP get?

Current headcount on KimagureJP: 0 players, 30 slots available. Check: players over seven days. Average 1, peak 7. The last 48 hours peaked at 09:00 UTC, averaging 3 players at that hour.

Server details

Which location does KimagureJP run from?

KimagureJP gives Asia as its location, with the EA tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 160.251.205.9:28015.

What Rust version is KimagureJP on?

Reading: KimagureJP, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for KimagureJP?

Reading: 45 server fps on average across the last 48 hours. It never dropped below 24. Check: entities. The peak was 73,459, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,315 MB. Expect lag when fps falls and entities climb.

What is the uptime on KimagureJP, and is it online?

KimagureJP reports online. Status: normal. By its reported uptime, the last restart was roughly 5 days 9 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does KimagureJP enforce, and what are its settings?

No gather rate appears in the name: KimagureJP. Groups stop at 4 players. The label given is quad. The mode is softcore. Note the following: Facepunch's lighter mode: some loot is kept. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on KimagureJP?

From seed 1862081922, the game generates the procedural map on KimagureJP. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join KimagureJP?

To join: start Rust, press F1 and type client.connect 160.251.205.9:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp30,ptrak,$r?,v2635,^w,EA,gmsoftcore,cs168909,ts4

Game

gmsoftcore
Game mode Check: ruleset. Softcore, the easier option.
mp30
Max players The server holds 30 slots.
ts4
Group limit Teams are capped at 4.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly It wipes each week.

Region

EA
East Asia East Asia is the browser category it sits in.

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.