Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO E SRV11,863online PAX104,004playing OCC3,955with players WIPED 3H547
PVEPvE traffic
Callsign

KMG3132=

KimagureJP

Online EA 160.251.205.9:28015 checked 10m ago

weekly wipes vanillapve
Clearance · join
Players now 2/ 30 7% full
7-day average1peak 7
Rank#3,132top 14% · #279 in EA
Last wipe7h agoweekly schedule
Next wipe5d 23hWed 4 Nov, 18:51 UTC
Track history

Players

AveragePeakWipe
0123420:0005:0014:0023:0008:0018:00Wiped Thu 29 Oct, 11:35 UTCWIPE

Hourly average and peak, UTC.

Server performance

Server fpsWipe
05010015020020:0005:0014:0023:0008:0018:00Wiped Thu 29 Oct, 11:35 UTCWIPE

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
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.

Flight plan

Wipe schedule

a steady gap
ETD · next wipe

Next wipe Wednesday 4 November, 18:51 UTC, in 5d 23h.

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. 5d 23hWed 4 Nov, 18:51 UTC
  2. 6d 23hThu 5 Nov, 19:00 UTCFW
  3. 12d 6hWed 11 Nov, 02:07 UTC
  4. 18d 13hTue 17 Nov, 09:23 UTC
  5. 24d 21hMon 23 Nov, 16:40 UTC
  6. 31d 4hSun 29 Nov, 23:56 UTC
  7. 34d 23hThu 3 Dec, 19:00 UTCFW
  8. 37d 11hSun 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

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

Wipes

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

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign SEA015EA · groups of 8+ · weekly · 6 on average [SEA]Singapore PVEx20 10/23/26 SkillTree Events
    Players 2/50
  2. 02PVE
    Callsign PVE051EA · groups of 30+ · monthly · 22 on average 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍
    Players 9/200
  3. 03PVE
    Callsign SEA015EA · groups of 8+ · monthly · 17 on average [SEA] RustEZ Pure PvE | Low Decay | No Killing | No Raiding
    Players 9/200
  4. 04PVE
    Callsign RST015EA · groups of 8+ · monthly · 15 on average JP RustPvE kokuu Server No kill No raid beeginner
    Players 4/200
  5. 05PVE
    Callsign KIY015EA · groups of 20+ · monthly · 5 on average Kiyo Server JP PVE
    Players 2/30
  6. 06PVE
    Callsign SEA016EA · groups of 8+ · monthly · 5 on average [SEA] tRust SG PvE Monthly Vanilla
    Players 2/50
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which lists and filters on Rust Tracker show KimagureJP?

On Rust Tracker, KimagureJP sits in these lists: PvE servers, tracked live, Community servers, no tags and Vanilla Rust servers, tracked live. On the server list, these filters bring it up: 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.

What do the tags mean that KimagureJP is listed under?

Listed for the server browser to read, KimagureJP publishes these tags: gmrust (Game mode): Survival as standard Rust plays; mp30 (Max players): Capacity: 30 slots; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set; ^w (Weekly): A weekly wipe; ^v (Vanilla): Facepunch's game unaltered: rates, kits and rules unchanged; ^p (PvE): No player fights — the world is the danger; EA (East Asia): In the server browser it is listed under East Asia. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Times

What happens on KimagureJP on wipe day?

At their busiest, recent wipes averaged 8 players. 8 hours after the latest wipe, the crowd peaked. Half the peak was held until the next wipe in 0% of its recent wipes. The fall below half came by day 4 where it did not hold.

When does KimagureJP wipe?

The recent gap between wipes at KimagureJP is about 6.8 days. Due on Wednesday 4 November at 18:51 UTC: its next wipe. Its world went live 7 hours. Tags list a weekly wipe schedule.

Server Details

How reliable is KimagureJP, and is it online now?

Tracking shows KimagureJP online as of now. The uptime it reports puts the last restart about 6 hours ago. Uptime stood at 99% for the last 7 full days, 167 of 168 hours online. First contact for Rust Tracker: 13 September 2026.

Which Rust build is KimagureJP running?

Rust network protocol 2635 and build 168909 is the build on KimagureJP; the platform is Linux. Steam updates it for you; your game must share the protocol to join.

Is KimagureJP holding performance?

For the last 48 hours it averaged 53 server fps; the floor was 24. Maximum entities carried: 73,459, from buildings and deployables to everything else. Memory peaked at 3,315 MB. A climbing entity count and low fps are what register as lag for players.

Which location is KimagureJP in?

Listed in Asia under EA: that is KimagureJP by its own tags. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 160.251.205.9:28015.

Player Count

How many players are on KimagureJP right now?

Slots 30; players on board 2: that is KimagureJP now. Peak of 7 in the last seven days, average 1 players. Peak traffic in the last 48 hours came at 09:00 UTC, averaging 3 players.

What rank does KimagureJP carry among Rust servers?

Seven-day player hours: #3,132 overall for KimagureJP, top 14% of ranked servers, #279 in Asia.

Settings

Which settings and rules are confirmed on KimagureJP?

No gather rate appears in KimagureJP's name. Up to 8 players per group, the game's default. It runs pve, fighting between players is off. A community server: the server browser lists it under Community. Its label is vanilla: facepunch's game unaltered: rates, kits and rules unchanged. VAC is on, Valve's anti-cheat.

Which map is confirmed for KimagureJP?

Generated by the game from seed 18922, the procedural map on KimagureJP measures 3,500. Same size, same seed, same map. RustMaps shows it, linked from this page.

How to Join

How do you get onto KimagureJP?

To connect: start Rust, press F1, enter client.connect 160.251.205.9:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp30
Max players Capacity: 30 slots.
ts8
Group limit Team limit is 8, the game default.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code Region code: not set.

Wipe schedule

^w
Weekly A weekly wipe.

Difficulty

^v
Vanilla Facepunch's game unaltered: rates, kits and rules unchanged.

Gameplay

^p
PvE No player fights — the world is the danger.

Region

EA
East Asia In the server browser it is listed 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.