[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
Online EA 153.197.161.35:28017 checked 6m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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
daily · 1 is bestTop 15% of all ranked servers, top 52% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Friday 30 October, 04:32 UTC · 04:32 UK, in 22h.
Its biweekly schedule tag · low confidenceComing wipes
- 22hFri 30 Oct, 04:32 UTC04:32 UK
- 7d 12hThu 5 Nov, 19:00 UTC19:00 UKFW
- 14d 22hFri 13 Nov, 04:32 UTC04:32 UK
- 28d 22hFri 27 Nov, 04:32 UTC04:32 UK
- 35d 12hThu 3 Dec, 19:00 UTC19:00 UKFW
- 42d 22hFri 11 Dec, 04:32 UTC04:32 UK
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
every wipe as a delivery, newest first-
Fri 30 Oct, 04:32 UTC04:32 UK · in 22hNext wipe expected · its biweekly schedule tag
-
Fri 16 Oct, 04:32 UTC 05:32 UK · 13d agoWipe delivered
- Peak
- 5
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Thu 1 Oct, 19:05 UTC FW 20:05 UK · 27d agoForce wipe delivered
- Peak
- 4
- Crowd
- halved by day 9
- Lasted
- 14.4 days
- Players before
- 0
-
Thu 17 Sep, 19:00 UTC 20:00 UK · 41d agoWipe delivered
- Peak
- 7
- Crowd
- halved by day 6
- Lasted
- 14 days
- Players before
- 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.
Player activity
Where does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe place among Rust servers?
Ranked #3,286 on player hours over the last seven days, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is #294 in Asia and in the top 15% of all ranked servers.
Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe busy at the moment?
The current count is 1 players on 150 slots for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. The seven-day figures show an average of 1 players and a peak of 7. Over the last 48 hours, the peak hour came at 10:00 UTC with an average of 5 players.
Map and rules
What is the current map on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
The game generates the procedural map on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe at size 4,500 with seed 930824030. You can see the map on RustMaps from this page, since one size and seed give one map.
What settings and rules should you know for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
No gather rate appears in the name of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. Up to 8 players can join a group, the default for the game. survival is the mode, gather and build and raid: the standard game. Raiding and PvP are both on. You will find it listed under Community in the server browser: it is a community server. The plugins run on Carbon. The vanilla label is one it applies to itself: unchanged rates, kits and rules: Facepunch's standard game. Rust premium status is required to join. The VAC anti-cheat from Valve is enabled.
About the server
What is the location of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
With its EA tag, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe places itself in Asia. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. You will find it at 153.197.161.35:28017.
How smoothly does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe run?
The 48-hour average for server fps stands at 98, never dipping below 81. Buildings, deployables and all the rest of the world pushed its entity count as high as 122,965. 4,550 MB of memory was its top figure. What players call lag is the mix of low fps and an entity count that keeps climbing.
Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe up, and how good is its uptime?
Right now, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is online. Its reported uptime suggests a restart roughly 7 hours ago. 99% is the uptime for the last 7 full days, up for 167 of 168 hours. 13 September 2026 is when Rust Wipe Tracker first recorded it.
What Rust version is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe using?
The version on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is Rust network protocol 2635 and build 168909, running on Linux. The same protocol is required to join, and Steam takes care of updating it.
Wipe times
How does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe handle its wipe days?
5 players is the average peak across its recent wipes. 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. In the other cases it sank under half by day 7.5.
When does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe wipe? What schedule does it follow?
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. You can expect its next wipe on Friday 30 October at 04:32 UTC. The world it is running was made 13 days 1 hours. In its tags it posts a wipe every two weeks.
Server tags
On Rust Wipe Tracker, which lists and filters is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe part of?
You will find [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe on the following Rust Wipe Tracker lists: Rust community servers, unmodded and Vanilla Rust servers. You will find it 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 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, so one operator most likely runs them all.
What is the meaning of the server tags on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
gmrust (Game mode): Survival in standard Rust; mp150 (Max players): It holds 150 slots; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): A region code isn't set; ^b (Biweekly): A wipe comes every fortnight; ^v (Vanilla): Unchanged rates, kits and rules: Facepunch's standard game; ^y (Carbon): Carbon, a plugin framework, is installed here; ^q (Premium): Rust premium status is required to join; EA (East Asia): Server browser category: East Asia are the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes, and the server browser takes them as read. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.
Getting started
What steps do you take to join [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Enter client.connect 153.197.161.35:28017 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you. Rust premium status is required to join.