Rust Dashboard48,587 playing

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe

Online EA 153.197.161.35:28017 checked 6m ago

biweekly wipes vanillacarbonpremium

Players now

Live
0of 150
Full
0%
In queue
0
Peak, 48 hours
7
Peak, 7 days
7

0% full

Tue 01:00Wed 22:00players each hour · 48 hours · UTC

Rank

#3,311

top 15% · #310 in EA

7-day average

1

peak 7

Last wipe

12d ago

biweekly schedule

Next wipe

1d 4h

Fri 30 Oct, 04:32 UTC

Players

AveragePeak
0246801:0010:0019:0003:0012:0022:00

Hourly average and peak, UTC.

Server performance

05010015020001:0010:0019:0003:0012:0022: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.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 04:32 UTC, in 1d 4h. Its biweekly schedule tag · low confidence

14.2 daysusual gapbetween real wipes
100%on rhythmof its recent wipes
5wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 7.5

Coming wipes

  • 1d 4hFri 30 Oct, 04:32 UTC
  • 7d 18hThu 5 Nov, 19:00 UTCFW
  • 15d 4hFri 13 Nov, 04:32 UTC
  • 29d 4hFri 27 Nov, 04:32 UTC
  • 35d 18hThu 3 Dec, 19:00 UTCFW
  • 43d 4hFri 11 Dec, 04:32 UTC

The first 48 hours of its last wipes

Fri 16 OctThu 1 OctThu 17 Sep
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 28 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 04:32 UTC12d ago 5 – running 0
Thu 1 Oct, 19:05 UTC FW27d ago 4 halved by day 9 14.4 days 0
Thu 17 Sep, 19:00 UTC41d ago 7 halved by day 6 14 days 0

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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1
    Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 66 on average
    5/ 200
  2. 2
    Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.comEA · groups of 8+ · biweekly · 42 on average
    15/ 215
  3. 3
    Rustafied.com - SEA MediumEA · groups of 16+ · biweekly · 27 on average
    4/ 100
  4. 4
    [SEA/KR/JP] Rusty Malaysia | Biweekly | VanillaEA · groups of 8+ · biweekly · 4 on average
    0/ 200
  5. 5
    JP ONLY 2WEEK SOLO/DUO/TORIO#84EA · groups of 8+ · biweekly · 3 on average
    1/ 60
  6. 6
    [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 2 on average
    1/ 100

Quick answers

from the figures on this page

Server details

Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe online, and how reliable is it?

Right now [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is running. The uptime it reports puts its last restart about 1 hours ago. It was online 86% of the last 7 full days, which is 144 of 168 hours. Our records for it start on 13 September 2026, when Rust Dashboard first saw it.

Which version of Rust does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe run?

Rust network protocol 2635 and build 168909 is running on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, which sits on Linux. You need the same protocol as the server to join. Steam updates your game for you.

Where is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe located?

In Asia, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe lists itself with the EA tag. A server's stated location is what Rust Dashboard displays; it does not check where the machine stands. Connect to it at 153.197.161.35:28017.

Does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe run smoothly?

The last 48 hours gave an average of 98 server fps, and it never went under 81. The world held as many as 122,965 entities, counting buildings, deployables and all the rest. Memory use peaked at 4,550 MB. When fps is low and entities keep piling up, players notice it as lag.

Tags, lists

Which Rust Dashboard lists and filters include [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

The Rust Dashboard lists that carry [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe are: Best Rust community servers and Vanilla Rust servers. You'll find it under these filters on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: Premium; Server tag: Biweekly ^b, Vanilla ^v, Premium ^q and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Who runs [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

A crypto-cheer.jp hostname is published by [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, and by 2 other servers we track, so one operator most likely runs them all.

What do the server tags on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe mean?

The browser in the game reads gmrust (Game mode): This is Rust as it comes, with survival rules unchanged; mp150 (Max players): It holds 150 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Your game needs to be on the same version, protocol 2635, to get in; cs168909 (Build): Build 168909 is what it runs; ptrak (Networking): RakNet is the standard network layer for the game, and it is what runs here; $r? (Region code): No region code is set; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): No changed rates, kits or rules: the game exactly as Facepunch ships it; ^y (Carbon): Carbon handles the plugins on this server; ^q (Premium): You need Rust's premium status to get in; EA (East Asia): East Asia is where the server browser puts it from [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe as its tags. The tags also carry the current player count, the queue and when the world was made, all shown at the top of this page.

Population

How busy is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe has 0 of its 150 slots filled at the moment. Averaged across the last seven days: 1 players, peaking at 7. Across the last 48 hours, the peak came at 10:00 UTC with an average of 5 players.

How does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe rank against other Rust servers?

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe holds #3,311 for player hours across seven days, #310 in Asia, in the top 15% of all ranked servers.

Reset times

What does wipe day look like on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

At their busiest, its recent wipes drew 5 players on average. On the latest wipe, 28 hours passed before the crowd peaked. Above half that peak until the next wipe: that held in 0% of recent wipes. In the other cases it dropped below half by day 7.5.

What is the wipe schedule on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

Its schedule cannot be confirmed from the record, which holds too few of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe's wipes, so the prediction follows the tag. On Friday 30 October at 04:32 UTC the next wipe is due. 12 days 19 hours ago the current world was made. Its tags publish a wipe schedule of every two weeks.

Map and rules

What are the rules and settings on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

No gather rate appears in the name of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. The group limit is 8 players, which is the game's default. It runs survival, the usual game, where you gather, build and raid. Raids and player fights are part of the game here. It appears in the Community section of the server browser. The plugin count is Carbon. Vanilla is the label it uses: no changed rates, kits or rules: the game exactly as Facepunch ships it. You need Rust's premium status to get in. VAC is on: that is Valve's anti-cheat.

Which map does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe run?

The game generates the procedural map on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, size 4,500 with seed 930824030. Because size and seed fix the map, a RustMaps view is available from this page.

How to join

How do I join [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

Type client.connect 153.197.161.35:28017 in the Rust console, which F1 opens. Launch Rust on this page also works: Steam opens Rust and connects you. You need Rust's premium status to get in.

Server tags

what each one means

Published as mp150,ptrak,$r?,v2635,^y,^b,^v,EA,gmrust,cs168909,^q,ts8

Game

gmrust
Game mode This is Rust as it comes, with survival rules unchanged.
mp150
Max players It holds 150 slots.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol Your game needs to be on the same version, protocol 2635, to get in.
cs168909
Build Build 168909 is what it runs.
ptrak
Networking RakNet is the standard network layer for the game, and it is what runs here.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game exactly as Facepunch ships it.

Mods and access

^y
Carbon Carbon handles the plugins on this server.
^q
Premium You need Rust's premium status to get in.

Region

EA
East Asia East Asia is where the server browser puts 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.