[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe
Key statistics
the figures behind the quote- Players now
- 0/ 150 0% full
- Change · 24h
- ▪+0 no reading a day ago
- 7-day average
- 1 peak 5
- Rank
- #4,233 top 19% · #334 in EA
- Rank · 7d ago
- #4,048 ▼185 places down
- Last wipe
- 12d ago biweekly schedule
- Next wipe
- 1d 22h Thu 15 Oct, 19:05 UTC
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 85 player hours, last seven days
- Map
- 4500 Procedural Map · seed 452968691
- First seen
- 13 Sep 2026 inaka2.crypto-cheer.jp
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 1 players.
Daily average and peak, UTC.
Server performance
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 bestTop 19% of all ranked servers, top 64% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tag- usual gap
- 14 days between real wipes
- wipe-day peak
- 6 players, last three wipes
- crowd held
- 0% else halves by day 6
Coming wipes
- 1d 22hThu 15 Oct, 19:05 UTC
- 15d 22hThu 29 Oct, 19:05 UTC
- 22d 22hThu 5 Nov, 19:00 UTCFW
- 29d 22hThu 12 Nov, 19:05 UTC
- 43d 22hThu 26 Nov, 19:05 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 16 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 54 on average | 29/200 | ▲+6+28.4% | |
| 2 | Japan Tokyo - Mondays|10/05|JP/KR/SEA|2週間|JumpRust.comEA · groups of 8+ · biweekly · 39 on average | 10/215 | ▲+2+21.2% | |
| 3 | Rustafied.com - SEA MediumEA · groups of 16+ · biweekly · 28 on average | 10/100 | ▲+5+106.9% | |
| 4 | JP ONLY 2WEEK SOLO/DUO/TORIO#83EA · groups of 8+ · biweekly · 10 on average | 2/60 | ▲+1+60.0% | |
| 5 | [SEA/KR/JP] Rusty Malaysia | Biweekly | VanillaEA · groups of 8+ · biweekly · 9 on average | 0/200 | ▪+0 | |
| 6 | [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 3 on average | 1/100 | ▪+0 |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
No gather rate appears in the name of [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe. Groups can contain a maximum of 8 players, the default for the game. survival is the mode, gather, build and raid in the standard game. You can fight and raid other players. The server browser lists it under Community, as a community server. Carbon plugins are running. Its self-description is vanilla: facepunch's build, untouched: no rate changes, no kits, no rule changes. Entry requires Rust's premium status. VAC is active.
Which map is played on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe uses a procedural map of size 4,500 with seed 452968691, generated by the game. You can see the map on RustMaps from this page, as the same size and seed give the same map.
Player Count
Where does [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe sit in the rankings?
In the top 19% of all ranked servers, [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe is #4,233 on player hours over the last seven days and #334 in Asia.
How many players does [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe have?
On [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe, 0 players are in now, out of 150 slots. Average players over seven days: 1; peak: 5. Over the last 48 hours, the peak hour was 11:00 UTC, averaging 1 players.
Wipe Schedule
How does [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe handle wipe day?
The average peak across its recent wipes is 6 players. 16 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The crowd fell below half by day 6 when it did not hold.
When does [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe schedule its wipes?
The prediction follows the tag because too few of [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe's wipes are on record to confirm its schedule. On Thursday 15 October at 19:05 UTC the next wipe is due. Its world now is 12 days 1 hours old. Its tags carry a wipe schedule of every two weeks.
Server Overview
What is the server location for [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
The EA tag and Asia are what [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe lists for itself. Rust Analytics reports the location a server claims, not the machine's actual location. 153.197.161.35:28017 is its address.
What is the performance like on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
Server fps over the last 48 hours: 100 on average, 82 at the lowest. At its peak it held 115,884 entities: buildings, deployables and the rest of the world. Up to 4,365 MB of memory was used. What players feel as lag is low fps together with a rising entity count.
What Rust version is [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe running?
The version in use at [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe: Rust network protocol 2634 and build 167781, on Linux. Joining requires the same protocol on your game, which Steam updates.
How reliable is [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe and is it currently online?
[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe is up. It is taking players now. Its own uptime figure dates the last restart to roughly 22 hours ago. 100% is its uptime for the last 7 full days, 168 of 168 hours. First sighting by Rust Analytics: 13 September 2026.
Tags and Rankings
What is the meaning of the tags on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
Published by [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe for the game's server browser to read: gmrust (Game mode): Rust's standard survival mode; mp150 (Max players): Slot count: 150; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): To join, your game needs protocol 2634; cs167781 (Build): It runs build 167781; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^b (Biweekly): One wipe every fortnight; ^v (Vanilla): Facepunch's build, untouched: no rate changes, no kits, no rule changes; ^y (Carbon): The plugin framework here is Carbon; ^q (Premium): Entry requires Rust's premium status; EA (East Asia): East Asia is its browser listing. The top of this page and the tags both show its players now, its queue and when its world was made.
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 the 2 other servers we track that publish a crypto-cheer.jp hostname.
[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe appears in which of the lists and filters on Rust Analytics?
On Rust Analytics, [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe matches these lists: Rust community servers and Vanilla Rust servers. 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.
Connection
What steps do I take to join [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
The console route: start Rust, press F1, enter client.connect 153.197.161.35:28017. The page's Launch Rust button opens Rust through Steam and connects you instead. Entry requires Rust's premium status.
Server tags
what each one meansPublished as mp150,ptrak,$r?,v2634,^y,^b,^v,EA,gmrust,cs167781,^q,ts8
Game
gmrust
mp150
ts8
v2634
cs167781
ptrak
$r?
Wipe schedule
^b
Difficulty
^v
Mods and access
^y
^q
Region
EA
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.