Rust Player Stats
Live UTC 54,200 playing

Online EA 153.197.161.35:28017 checked 11m ago

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

biweekly wipes vanillacarbonpremium
Players now0
Slots150
Full0%
7-day average1peak 7
Rank#3,306top 15% · #310 in EA
Last wipe12d agobiweekly schedule
Next wipe1d 5hFri 30 Oct, 04:32 UTC
Launch Rust and join

By the numbersMatch stats

against its 150 slots
Players now0
0% of the slots taken
7-day average1
players on an average hour this week
7-day peak7
the fullest it got this week
48-hour peak7
the busiest hour of the last two days
On the list46 of 48 hours
hours it answered in the last two days
Server fps98
average over 48 hours; 60 or more is smooth
Standingtop 15%
of all ranked servers, on player hours over seven days
Replay

The story of the match

Players, performance and rank, hour by hour and day by day.

CrowdPlayers

AveragePeak
0246800:0009:0018:0003:0012:0022:00

Hourly average and peak, UTC.

FitnessServer performance

05010015020000:0009:0018: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.

FormRank

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.

FixturesWipe schedule

from its schedule tag

Next wipeFriday 30 October, 04:32 UTCin 1d 5h Its biweekly schedule tag · low confidence

usual gap14.2 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak5players, last three wipes
crowd held0%else halves by day 7.5

Coming wipes

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

ResultsWipes

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.

Other matches on now

Similar servers

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

The pundits

Quick answers

From the figures on this page.

About the server

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

Online now, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is up. About 1 hours ago is when it restarted, judging by its reported uptime. 100% of the time over the last 7 full days, which is 168 of 168 hours up. Rust Player Stats logged it for the first time on 13 September 2026.

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

The last 48 hours average out at 98 server fps; it never dropped below 81. Up to 122,965 entities sat in the world, buildings and deployables included. Memory use reached 4,550 MB. A climbing entity count plus low fps: that is lag, as players experience it.

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

On Linux, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe runs Rust network protocol 2635 and build 168909. To get in, your game needs the same protocol; Steam handles the update.

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

Its EA tag places [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe in Asia. Rust Player Stats takes the server's word on where it is and does not look up the machine's real location. 153.197.161.35:28017 is the address.

Lists and filters

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

gmrust (Game mode): Survival, standard Rust style; mp150 (Max players): It holds 150 slots; ts8 (Group limit): Teams cap at 8, the game default; v2635 (Protocol): To join, your game has to run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, the standard one; $r? (Region code): No region code is set; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): The game as shipped by Facepunch, with rates, kits and rules untouched; ^y (Carbon): The plugin framework is Carbon; ^q (Premium): You need Rust's premium status to join; EA (East Asia): In the server browser it sits under East Asia are the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes, and the game's server browser reads them. The tags carry more besides: present players, queue length and when the world was made, all displayed at the top of this page.

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

One operator most likely runs [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe and the 2 other servers we track that share its crypto-cheer.jp hostname.

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

You will find [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe on the following Rust Player Stats lists: Community servers, ranked live and Vanilla Rust servers. 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.

Server rules

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

The procedural map on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is size 4,500, generated by the game from seed 930824030. The map repeats with that size and seed, and you can view it on RustMaps from here.

What are the rules and settings 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. Groups top out at 8 players, the default for the game. build, gather and raid in the standard game: that is the survival game mode. Fighting and raiding between players is allowed. The server browser lists it under Community. It runs plugins: Carbon. Vanilla is its own label: the game as shipped by Facepunch, with rates, kits and rules untouched. You need Rust's premium status to join. Anti-cheat is on: VAC.

Live counts

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

0 of 150 slots are filled on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe right now. Averaged across seven days: 1 players. The high point: 7. It drew its biggest crowd of the last 48 hours at 10:00 UTC: 5 players on average.

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

In Asia it is #310, and #3,306 on seven-day player hours, in the top 15% of all ranked servers: [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe.

Wipe schedule

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

The prediction follows its tag, because too few of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe's wipes are on record to confirm its schedule. Due on Friday 30 October at 04:32 UTC is its next wipe. 12 days 18 hours ago is when its current world was made. The wipe schedule in its tags is every two weeks.

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. 28 hours after the wipe, the crowd peaked on the latest wipe. Half that peak was held until the next wipe in 0% of its recent wipes. It fell below half by day 7.5 when it didn't hold.

Joining the server

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

In the Rust console (F1) type client.connect 153.197.161.35:28017. Alternatively, Launch Rust on this page opens Rust through Steam and drops you straight in. You need Rust's premium status to join.

GlossaryServer tags

what each one means

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

Game

gmrust
Game mode Survival, standard Rust style.
mp150
Max players It holds 150 slots.
ts8
Group limit Teams cap at 8, the game default.
v2635
Protocol To join, your game has to run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, the standard one.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^v
Vanilla The game as shipped by Facepunch, with rates, kits and rules untouched.

Mods and access

^y
Carbon The plugin framework is Carbon.
^q
Premium You need Rust's premium status to join.

Region

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