[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
Online EA 153.197.161.35:28017 checked 3h ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
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
Top 15% of all ranked servers, top 55% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 30 October, 04:32 UTC, in 1d 8h. Its biweekly schedule tag · low confidence
- usual gap
- 14.2 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 5players, last three wipes
- crowd held
- 0%else halves by day 7.5
Coming wipes
- in 1d 8hFri 30 Oct, 04:32 UTC
- in 7d 22hThu 5 Nov, 19:00 UTCFW
- in 15d 8hFri 13 Nov, 04:32 UTC
- in 29d 8hFri 27 Nov, 04:32 UTC
- in 35d 22hThu 3 Dec, 19:00 UTCFW
- in 43d 8hFri 11 Dec, 04:32 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 28 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
16 OCT 2026Fri 16 Oct, 04:32 UTC12d ago |
5 | – | running | 0 |
1 OCT 2026Thu 1 Oct, 19:05 UTC FW27d ago |
4 | halved by day 9 | 14.4 days | 0 |
17 SEP 2026Thu 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Settings and map
On [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, which rules and settings apply?
The name of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe does not state a gather rate. The group limit is 8 players, the game's default. The server runs survival, gather, build and raid: the standard game. PvP and raiding are allowed. It is listed under Community in the server browser and is a community server. Filed under plugins: Carbon. The server describes itself as vanilla: no changed rates, kits or rules: this is the game Facepunch ships. Rust premium status is required to join. VAC is on: Valve's anti-cheat is enabled.
Which map is in use on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Generated by the game, the procedural map of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe has size 4,500 and seed 930824030. You can view the map on RustMaps from this page, as the same size and seed give the same map.
Lists and filters
Which lists and filters on Rust Server Index is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe filed under?
Filed under these Rust Server Index lists is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: Community Rust servers, indexed and Vanilla Rust servers. Filed under these filters 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.
Who operates [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; the same operator most likely runs them.
Which tags are attached to [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, and what do they stand for?
These are the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp150 (Max players): Player cap: 150; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): The game build here is 168909; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): A region code is absent; ^b (Biweekly): Every second week brings a wipe; ^v (Vanilla): No changed rates, kits or rules: this is the game Facepunch ships; ^y (Carbon): Plugins run through Carbon; ^q (Premium): Rust premium status is required to join; EA (East Asia): The browser files it under East Asia. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipes and resets
How does a wipe day run on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
The average peak across its recent wipes is 5 players. The latest wipe peaked 28 hours in. The crowd held above half the peak until the next wipe in 0% of its recent wipes. By day 7.5 the crowd had fallen below half when it didn't hold.
How often is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe wiped, and on what schedule?
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 the schedule. On Friday 30 October at 04:32 UTC the next wipe is due. The world it runs now was made 12 days 15 hours. Filed in its tags: a wipe schedule of every two weeks.
Players and ranking
How is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe ranked compared with the rest?
The seven-day player-hours ranking places [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe at #3,296 and #308 in Asia, among the top 15% of ranked servers.
How many players are on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe at the moment?
[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is currently showing 0 players on 150 slots. The seven-day average is 1 players; the peak reached 7. The busiest point in the last 48 hours was 10:00 UTC, averaging 5 players.
Operator and status
Which Rust build is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe running?
Rust network protocol 2635 and build 168909, on Linux, is what [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe runs. To join you need the same protocol; Steam handles the update.
How reliable is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, and is it online now?
Right now [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is up and running. The uptime it reports puts the last restart at about 19 hours ago. Of the last 7 full days, 168 of 168 hours were up, 100% of the time. The earliest sighting at Rust Server Index is 13 September 2026.
How well does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe perform?
Server fps held at 99 on average across the last 48 hours, never dropping below 81. The entity count reached 122,965, covering buildings, deployables and all else in the world. The peak memory figure stood at 4,550 MB. A climbing entity count and low fps are felt by players as lag.
Which region is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe in?
The EA tag places [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, by its own listing, in Asia. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 153.197.161.35:28017.
Connecting
What steps lead onto [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
If you would rather use the console, press F1 in Rust and enter client.connect 153.197.161.35:28017. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you. Rust premium status is required to join.
Server tags
What each one means.
Published as mp150,ptrak,$r?,v2635,^y,^b,^v,EA,gmrust,cs168909,^q,ts8
Game
gmrust
mp150
ts8
v2635
cs168909
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.