Online EA 153.197.161.35:28017 checked 8m ago

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

biweekly wipes vanillacarbonpremium

Connect

srv = rust.server("153.197.161.35:28015")
print(srv.connect_command)

Launch Rust and join

Right now

srv.summary()

players now 0/150 # 0% full

7-day average 1 # peak 7

rank #3,297 # top 15% · #309 in EA

last wipe 12d ago # biweekly schedule

next wipe 1d 7h # Fri 30 Oct, 04:32 UTC

Players

srv.players.plot(range="48h")

AveragePeak

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")

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

srv.rank.plot(invert=True)  # 1 is best

RankRank in region

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

srv.wipe_schedule()

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

	in	at	kind
0	1d 7h	Fri 30 Oct, 04:32 UTC	wipe
1	7d 21h	Thu 5 Nov, 19:00 UTC	FW force wipe
2	15d 7h	Fri 13 Nov, 04:32 UTC	wipe
3	29d 7h	Fri 27 Nov, 04:32 UTC	wipe
4	35d 21h	Thu 3 Dec, 19:00 UTC	FW force wipe
5	43d 7h	Fri 11 Dec, 04:32 UTC	wipe

The first 48 hours of its last wipes

Fri 16 OctThu 1 OctThu 17 Sep

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

Wipes · newest first

srv.wipes.head(20)

	wiped	peak	crowd	lasted	players_before
	datetime64[UTC]	int64	object	timedelta	int64
0	Fri 16 Oct, 04:32 UTC12d ago	5	NaN	running	0
1	Thu 1 Oct, 19:05 UTC FW27d ago	4	halved by day 9	14.4 days	0
2	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.

display(srv.map, srv.info())

Map

4500 · seed 930824030

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

map: Procedural Map
size: 4500
seed: 930824030

Open on RustMaps

Server

srv.info()

<class 'rust.Server'>
Index: 8 entries, address to first_seen

address: 153.197.161.35:28017
region: EA
max players: 150
group limit: 8, the default
wipe schedule: biweekly
last wipe: 16 Oct 2026, 04:32 UTC
hostname: inaka2.crypto-cheer.jp
first seen: 13 Sep 2026

Operator · crypto-cheer.jp

rust.servers(operator="crypto-cheer.jp").sort_values("players")

	server	players
0	[JP] まったりクマ鯖 x3 \| 10/02 BP Wipe	0/100
1	[JP]Rustテストサーバー	0/100

3 servers publish a crypto-cheer.jp hostname.

About this server · in its own words

print(srv.description)

JP Only!! ※新規アカウント及びプロフィールが非公開の場合はログインできません Full wipe on force wipe. Map wipe on the 3rd, and 5th Friday of the month.. This server will reboot every morning at 5:30 (JST). IP address changes irregularly to avoid DDOS. Please speak Japanese or English in Global Chat.(speaking other languages may result in being kicked or banned.) Banned acts: spamming, hate speech, abusive language, racist remarks, harassment, goosing, sniping. Have a good time! Do not cheat! Have a good time. Do not cheating!! rs01$8:aozJ^0rAi4001$Y

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)

	server	like_this	players
0	Rustoria.co - SEA Medium	EA · groups of 16+ · biweekly · 67 on average	9/200
1	Japan Tokyo - Mondays\|10/19\|JP/KR/SEA\|2週間\|JumpRust.com	EA · groups of 8+ · biweekly · 42 on average	14/215
2	Rustafied.com - SEA Medium	EA · groups of 16+ · biweekly · 27 on average	11/100
3	[SEA/KR/JP] Rusty Malaysia \| Biweekly \| Vanilla	EA · groups of 8+ · biweekly · 4 on average	1/200
4	JP ONLY 2WEEK SOLO/DUO/TORIO#84	EA · groups of 8+ · biweekly · 3 on average	1/60
5	[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.

Population

What position does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe take in the server rankings?

Player hours over the last seven days: #3,297 for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, #309 in Asia, within the top 15% of the ranked set.

What population does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe carry?

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe reports 0 players at this refresh, with 150 slots configured. Over the last seven days it averaged 1 players and peaked at 7. Peak hour in the last 48 hours: 10:00 UTC, mean 5 players.

About the server

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

Averaged over 48 hours: 98 server fps, never under 81. Buildings, deployables and all else in the world took the count as high as 122,965 entities. The memory field tops out at 4,550 MB. What players call lag is these two fields together: low fps and a rising entity count.

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

Version Rust network protocol 2635 and build 168909 on Linux is reported by [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. Steam updates your game for you, but the protocol must match to join.

Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe up, and what does its uptime show?

Online is the state at the latest refresh for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. A restart about 19 hours ago is what its reported uptime implies. 168 of 168 hours up over the last 7 full days, or 100%. The first row Rust Data holds for it is dated 13 September 2026.

In which location is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe hosted?

With its EA tag, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe lists itself in Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 153.197.161.35:28017.

Map and rules

Which rules apply on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, and what settings?

You will not find a gather rate in the string [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Community is its browser category. Plugins installed: Carbon. Its own label is vanilla: untouched settings: rates, kits and rules as shipped. Premium status is needed to join. Anti-cheat status: VAC on.

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

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

Wipes and dates

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

The tag sets the prediction: [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe has too few wipes on record to confirm its schedule. The schedule puts the next wipe on Friday 30 October at 04:32 UTC. This world was created 12 days 16 hours ago. The tags list a two-weekly wipe cycle.

On [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, what happens on wipe day?

Across recent wipes the busiest point averaged 5 players. 28 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 7.5.

Tags and filters

Where does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe appear among Rust Data lists and filters?

These Rust Data lists include [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: Rust community servers, unfiltered and Vanilla Rust servers. Under these filters on the server list, it is listed: 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 is behind [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, which suggests the same operator runs them.

Which meanings do the tags on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe hold?

The game's server browser reads these tags from [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: gmrust (Game mode): Rust survival in its standard form; mp150 (Max players): Slot count: 150; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): The cycle is fourteen days; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^y (Carbon): The plugin framework in use is Carbon; ^q (Premium): Premium status is needed to join; EA (East Asia): In the server browser it sits under East Asia. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

What is the way to join [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

Enter client.connect 153.197.161.35:28017 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. Premium status is needed to join.

Server tags · what each one means

srv.tags.decode()

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

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.