RUST ZERG LIFEClan war room · live
No limit8 · game default
Deployment dossierOnline

[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe

EA 153.197.161.35:28017 checked 14m ago

biweekly wipes vanillacarbonpremium
Deploy
Zerg meter0%empty
0/150 troops
7-day average1
peak 5
Rank#4,237
top 19% · #333 in EA
Last wipe12d ago
biweekly schedule
Next wipe · H-hour1d 18h
Thu 15 Oct, 19:05 UTC

Players

AveragePeak
00.250.50.75102:0011:0020:0005:0014:0023:00

Hourly average and peak, UTC.

Server performance

05010015020002:0011:0020:0005:0014:0023: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 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Wipe schedule

from its schedule tag

Next wipe Thursday 15 October, 19:05 UTC, in 1d 18h. Its biweekly schedule tag · low confidence

usual gap14 days
between real wipes
wipe-day peak6
players, last three wipes
crowd held0%
else halves by day 6

Coming wipes

1d 18hThu 15 Oct, 19:05 UTC
15d 18hThu 29 Oct, 19:05 UTC
22d 17hThu 5 Nov, 19:00 UTCFW
29d 18hThu 12 Nov, 19:05 UTC
43d 18hThu 26 Nov, 19:05 UTC

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 4, 16 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 19:05 UTC FW12d ago 4 – running 0
Thu 17 Sep, 19:00 UTC26d 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
Zergmax 16
Rustoria.co - SEA Medium EA · groups of 16+ · biweekly · 53 on average
14/200
No limit8 · game default
Japan Tokyo - Mondays|10/05|JP/KR/SEA|2週間|JumpRust.com EA · groups of 8+ · biweekly · 38 on average
8/215
Zergmax 16
Rustafied.com - SEA Medium EA · groups of 16+ · biweekly · 28 on average
2/100
No limit8 · game default
JP ONLY 2WEEK SOLO/DUO/TORIO#83 EA · groups of 8+ · biweekly · 10 on average
0/60
No limit8 · game default
[SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla EA · groups of 8+ · biweekly · 9 on average
2/200
No limit8 · game default
[SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 3 on average
0/100

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?

You will not find a gather rate in the name [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe. Up to 8 players can group, which is the game's default. It runs survival, gather, build, raid: the regular game. Raiding and fighting other players are allowed. You will find it under Community in the server browser. The plugins it runs number Carbon. Its own label is vanilla: vanilla: the standard game, with no changes to rates, kits or rules. You need premium status to get in. VAC is on, Valve's anti-cheat.

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

A procedural map, size 4,500 with seed 452968691, generated by the game, is what [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe runs. From this page, RustMaps can show it: size and seed produce the same map each time.

Server population

How many players are on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?

[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe has 0 of its 150 slots filled right now. Averaging 1 players over seven days, it peaked at 5. The highest average over the last 48 hours came at 11:00 UTC, with 1 players.

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

For player hours in the last week, [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe ranks #4,237 overall and #333 in Asia, placing it in the top 19% of ranked servers.

Tags and filters

Who operates [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?

The same operator most likely runs [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe and 2 other servers we track, as they all publish a crypto-cheer.jp hostname.

What is the meaning of the tags on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?

What the game's server browser gets from [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe is this tag list: gmrust (Game mode): Standard survival gameplay; mp150 (Max players): It holds 150 players; ts8 (Group limit): Teams max out at 8—the default setting for Rust; v2634 (Protocol): Protocol 2634—only players on that version can get in; cs167781 (Build): Build number: 167781; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): Region code left unset; ^b (Biweekly): Every two weeks the server wipes; ^v (Vanilla): Vanilla: the standard game, with no changes to rates, kits or rules; ^y (Carbon): This server uses Carbon for plugins; ^q (Premium): You need premium status to get in; EA (East Asia): East Asia is the category it falls under in the server browser. The tags carry its players now, its queue and the time its world was made as well, and the top of this page displays them.

Which Rust Zerg Life filters and lists cover [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?

Rust community servers for clans and Vanilla servers for clans and zergs: that is where you will find [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe among the Rust Zerg Life rankings. These filters bring it up 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.

Server details

Is [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe currently online and stable?

[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe is up and running as you read this. Based on the uptime it reports, the last restart was about 2 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. Rust Zerg Life has been tracking it since 13 September 2026.

Is [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe smooth to play on?

Over the past 48 hours, server fps averaged 100 and never dropped below 82. It reached a maximum of 115,884 entities, covering buildings, deployables and the rest of the world. At its highest, memory usage hit 4,365 MB. Lag, as players feel it, is caused by low fps and an increasing number of entities.

What Rust version is [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe on?

The server [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe runs Rust network protocol 2634 and build 167781 with Linux as its operating system. You can only join if your game uses the same protocol, and Steam takes care of updating it.

What is the location of [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?

The EA tag is what [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe uses to list itself in Asia. Rust Zerg Life displays the location a server claims, not where the machine actually stands. Connect to it at 153.197.161.35:28017.

Wipe cycle

What can you expect on wipe day on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?

Across its recent wipes, the busiest times averaged 6 players. The crowd on the latest wipe peaked 16 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. If not, the crowd fell below half by day 6.

What schedule does [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe follow for wipes?

The prediction follows its tag because not enough of [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe's wipes are on record to confirm the schedule. Thursday 15 October at 19:05 UTC is when its next wipe is due. 12 days 5 hours ago is when its present world was created. The tags hold a fortnightly wipe schedule.

How to join

What is the process to join [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?

Join by entering client.connect 153.197.161.35:28017 in the console (press F1 first). Or use Launch Rust on this page, which opens Rust through Steam and connects you. You need premium status to get in.

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival gameplay.
mp150
Max players It holds 150 players.
ts8
Group limit Teams max out at 8—the default setting for Rust.
v2634
Protocol Protocol 2634—only players on that version can get in.
cs167781
Build Build number: 167781.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code Region code left unset.

Wipe schedule

^b
Biweekly Every two weeks the server wipes.

Difficulty

^v
Vanilla Vanilla: the standard game, with no changes to rates, kits or rules.

Mods and access

^y
Carbon This server uses Carbon for plugins.
^q
Premium You need premium status to get in.

Region

EA
East Asia East Asia is the category it falls under in the server browser.

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.