Rust PopulationField survey · Rust servers
Observing 34,720 players 11,597 servers 2,891 with someone on 65 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 3,545EAfirst seen 13 Sep 2026

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

Online EA 153.197.161.35:28017 checked 10m ago

biweekly wipes vanillacarbonpremium

Measurements

Players now
1/ 150
= 1 player
1% full
7-day average
1
peak 7
Rank
#3,545
top 16% · #336 in EA
Last wipe
12d ago
biweekly schedule
Next wipe
1d 22h
Fri 30 Oct, 04:32 UTC
Obs. 1 · sightings

Players

AveragePeak
0246807:0016:0001:0010:0019:0004:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

05010015020007:0016:0001:0010:0019:0004: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.

Obs. 3 · standing

Rank

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

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

Obs. 4 · the wipe cycle

Wipe schedule

from its schedule tag

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

14.2 days
usual gap
between real wipes
100%
on rhythm
of its recent wipes
5
wipe-day peak
players, last three wipes
0%
crowd held
else halves by day 7.5

Coming wipes

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

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 04:32 UTC12d ago 5 – running 0
Thu 1 Oct, 19:05 UTC FW26d ago 4 halved by day 9 14.4 days 0
Thu 17 Sep, 19:00 UTC40d 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.

Field questions

Quick answers

from the figures on this page

Population

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

On player hours over the last seven days [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is #3,545, #336 in Asia, placing it in the top 16% of ranked servers.

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

Of its 150 slots, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is using 1 right now. We counted an average of 1 players in the past week, with 7 at the busiest. The busiest hour in the last 48 was 10:00 UTC, when an average of 5 players were on.

Lists and tags

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

These are the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes, as read by the game's server browser: gmrust (Game mode): Survival in the standard Rust style; mp150 (Max players): 150 slots are available; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): This server has no region code; ^b (Biweekly): A wipe happens once a fortnight; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^y (Carbon): Carbon provides the plugin framework here; ^q (Premium): You need Rust's premium status to join; EA (East Asia): The server browser lists it under East Asia. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

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

The crypto-cheer.jp hostname that [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes is shared with 2 other servers we track; one operator most likely runs them.

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

These Rust Population lists include [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: Community servers, field-listed and Vanilla Rust servers, counted. Filter the server list by 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 and it will show up.

Wipe schedule

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

Averaged over recent wipes, 5 players were counted at the busiest point. The crowd on the latest wipe peaked 28 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 7.5 when it did not hold.

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

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

Map and rules

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

The map on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is procedural, made by the game at size 4,500 from seed 930824030. The map follows from its size and seed, and RustMaps shows it from this page.

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

The name tells you nothing about gather rates: [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe states none. The group limit is 8 players, which is the default. survival is what it runs, raid, build and gather: the standard game. Fighting and raiding between players is allowed. You will find it under Community: it is a community server. Carbon plugins are in use here. By its own description it is vanilla: no changed rates, kits or rules: this is the game as Facepunch ships it. You need Rust's premium status to join. You play with Valve's anti-cheat on: VAC.

About the server

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

The setup is Rust network protocol 2635 and build 168909 on Linux for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. Steam updates your game automatically, but you need the same protocol to join.

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

In the last 48 hours, it averaged 97 server fps, with a low of 80. The entity count reached 122,965: buildings, deployables and all other objects. Memory use peaked at 4,466 MB. Lag, as players feel it, is low fps combined with a climbing entity count.

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

You will find [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe online now. Judging by the uptime it reports, the last restart was about 7 hours ago. Over the last 7 full days, 168 of 168 hours were online, or 100%. It was first seen by Rust Population on 13 September 2026.

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

The EA tag is how [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe places itself in Asia. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. You will find it at 153.197.161.35:28017.

Getting in

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

Either enter client.connect 153.197.161.35:28017 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected. You need Rust's premium status to join.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp150
Max players 150 slots are available.
ts8
Group limit This is the game default: at most 8 per team.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Game build: 168909.
ptrak
Networking The standard network layer, RakNet, is in use.
$r?
Region code This server has no region code.

Wipe schedule

^b
Biweekly A wipe happens once a fortnight.

Difficulty

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

Mods and access

^y
Carbon Carbon provides the plugin framework here.
^q
Premium You need Rust's premium status to join.

Region

EA
East Asia The server browser lists it 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.