Skip to the coverage
Live Rust server stats, updated every five minutes.
Rust Live Stats
Live
34,284 players on Rust servers right now 11,672 servers online 2,842 with players on 85 fresh wipes in the last three hours [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: 0 players on now Updated every five minutes

LiveLive coverage · EA

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

Key points

  • 0 of 150 players are on now, 0% full.
  • Over the last seven days it averages 1 players, with a peak of 7.
  • It ranks #3,316, the top 15% of all ranked servers, and #309 in EA.
  • The current map has been up 12d 22h, since Friday 16 October, 04:32 UTC, on a biweekly schedule.
  • The next wipe is expected Friday 30 October at 04:32 UTC, in 1d 1h.
Join
biweekly wipes vanillacarbonpremium

Live coverage

newest first · every post is a reading of this server

Now: 0 of 150 players

0/ 150players now 0% full
17-day averagepeak 7
#3,316ranktop 15% · #309 in EA
12d agolast wipebiweekly schedule
1d 1hnext wipeFri 30 Oct, 04:32 UTC

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

Players

AveragePeak
0246804:0013:0022:0007:0016:0002:00

Hourly average and peak, UTC.

How the server is running

Server performance

05010015020004:0013:0022:0007:0016:0002: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 #3,316 today

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Next wipe in 1d 1h

from its schedule tag

Next wipe Friday 30 October, 04:32 UTC, in 1d 1h. 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

  1. 1d 1h
    Fri 30 Oct, 04:32 UTC
  2. 7d 15h
    Thu 5 Nov, 19:00 UTC
    FW
  3. 15d 1h
    Fri 13 Nov, 04:32 UTC
  4. 29d 1h
    Fri 27 Nov, 04:32 UTC
  5. 35d 15h
    Thu 3 Dec, 19:00 UTC
    FW
  6. 43d 1h
    Fri 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

Wipe peaks at 5 players

Peak
5
Crowd
–
Lasted
running
Players before
0

Force wipe peaks at 4 players

Peak
4
Crowd
halved by day 9
Lasted
14.4 days
Players before
0

Wipe peaks at 7 players

Peak
7
Crowd
halved by day 6
Lasted
14 days
Players before
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
Rustoria.co - SEA Medium
EA · groups of 16+ · biweekly · 65 on average
8 / 200
Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com
EA · groups of 8+ · biweekly · 41 on average
7 / 215
Rustafied.com - SEA Medium
EA · groups of 16+ · biweekly · 27 on average
5 / 100
[SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla
EA · groups of 8+ · biweekly · 4 on average
2 / 200
JP ONLY 2WEEK SOLO/DUO/TORIO#84
EA · groups of 8+ · biweekly · 3 on average
1 / 60
[SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly
EA · groups of 8+ · biweekly · 2 on average
0 / 100

Quick answers

from the figures on this page

Wipe days

What should you expect from wipe day on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

Recent wipes on this server averaged a peak of 5 players at their busiest. Peak population on the latest wipe came 28 hours after it. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. On those occasions it fell below half by day 7.5.

When does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe wipe?

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe's schedule cannot be confirmed from the wipes recorded, so its tag drives the prediction. Friday 30 October at 04:32 UTC is the date of its next wipe. 12 days 22 hours have passed since this world was generated. Wipes every two weeks: that is the schedule its tags publish.

Tags and categories

Who is in charge of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

The crypto-cheer.jp hostname [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes is shared with 2 other tracked servers, which points to one operator.

Which Rust Live Stats filters and lists does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe show up in?

The Rust Live Stats lists that include [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe are Live Rust community servers and Vanilla Rust servers, live. These filters on the server list bring it up: 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.

How should you read the tags on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

These are the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe makes public: gmrust (Game mode): The game mode is standard Rust survival; mp150 (Max players): The slot count is 150; ts8 (Group limit): Team cap: 8, which is the game default; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here; ^b (Biweekly): The cycle is two weeks per wipe; ^v (Vanilla): It runs the game as Facepunch ships it: rates, kits and rules unchanged; ^y (Carbon): Plugin framework: Carbon; ^q (Premium): You need Rust's premium status to join this server; EA (East Asia): East Asia is the browser listing for this server. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.

Population

How full is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe at the moment?

Live now: 0 players on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, out of 150 slots. Peak over the past week: 7. Average: 1 players. Between now and 48 hours back, 10:00 UTC drew the most players, 5 on average.

What position does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe hold among Rust servers?

Asia places [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe at #309; overall it is #3,316, inside the top 15% of ranked servers, by seven-day player hours.

Map and rules

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

Nothing in the name of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe states a gather rate. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. Fighting and raiding between players are allowed. You find it under Community in the server browser. The plugin load is Carbon. Its self-description is vanilla: it runs the game as Facepunch ships it: rates, kits and rules unchanged. You need Rust's premium status to join this server. VAC is enabled: Valve's anti-cheat.

Which map is in use on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

A procedural map of 4,500 with seed 930824030, generated by the game, runs on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. Size and seed repeat the same map, so RustMaps can show it from this page.

Server details

Where does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe sit geographically?

Its EA tag places [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe in Asia. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. Connect to 153.197.161.35:28017.

What is performance like on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

The average server fps was 98 over the last 48 hours; the lowest was 81. It supported up to 122,965 entities, covering buildings, deployables and all other objects. The highest memory usage was 4,550 MB. A climbing entity count and low fps are felt as lag by players.

What version of Rust is running on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

The setup on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is Rust network protocol 2635 and build 168909 with Linux. To join, your game must use the same protocol; Steam handles the update for you.

Does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe stay online, and is it up right now?

At the time of this update, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is live. About 5 hours ago is when it last restarted, according to its uptime. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. Rust Live Stats has tracked it since 13 September 2026.

Getting on

What steps connect you to [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 153.197.161.35:28017. You need Rust's premium status to join this server.

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp150
Max players The slot count is 150.
ts8
Group limit Team cap: 8, which is the game default.
v2635
Protocol The server runs protocol 2635, so match that version to join.
cs168909
Build Build: 168909.
ptrak
Networking The network layer is RakNet, the standard the game uses.
$r?
Region code No region code is set here.

Wipe schedule

^b
Biweekly The cycle is two weeks per wipe.

Difficulty

^v
Vanilla It runs the game as Facepunch ships it: rates, kits and rules unchanged.

Mods and access

^y
Carbon Plugin framework: Carbon.
^q
Premium You need Rust's premium status to join this server.

Region

EA
East Asia East Asia is the browser listing for this server.

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.