[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
Online EA 153.197.161.35:28017 checked 3h ago
Server instruments
last reading Wed 17:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 81 · below 20 is lag, below 10 is badEntities
48 h range 116,454–122,965 · memory 4,550 MBUptime
19 h 29 min since its last restart, at the last readingPlayers
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 55% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Friday 30 October, 04:32 UTC, in 1d 8h. Its biweekly schedule tag · low confidence
Coming wipes
- WPT 1Fri 30 Oct, 04:32 UTC1d 8h
- WPT 2Thu 5 Nov, 19:00 UTC7d 22hFW
- WPT 3Fri 13 Nov, 04:32 UTC15d 8h
- WPT 4Fri 27 Nov, 04:32 UTC29d 8h
- WPT 5Thu 3 Dec, 19:00 UTC35d 22hFW
- WPT 6Fri 11 Dec, 04:32 UTC43d 8h
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
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 04:32 UTC12d ago | 5 | – | running | 0 |
| Thu 1 Oct, 19:05 UTC FW27d ago | 4 | halved by day 9 | 14.4 days | 0 |
| Thu 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- 39/200
- 44/215
- 18/100
- 1/200
- 2/60
- 2/100
Quick answers
from the figures on this pageReset cycle
What happens on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe when wipe day comes?
An average of 5 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 28 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 7.5 it fell below half.
When does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe wipe?
Its tag guides the prediction: too few of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe's wipes are on record to confirm its schedule. Friday 30 October at 04:32 UTC is when its next wipe is due. 12 days 15 hours ago the current world was made. A wipe schedule of every two weeks is published in its tags.
Tags
Which tags does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe carry, and what do they mean?
These are the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp150 (Max players): Slots: 150; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^y (Carbon): Plugin framework in use: Carbon; ^q (Premium): Entry needs Rust's premium status; EA (East Asia): The server browser files it under East Asia. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Who is in charge of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Most likely the same operator runs them: [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes a crypto-cheer.jp hostname, and so do 2 other servers we track.
Which lists and filters on Rust Metrics show [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
On Rust Metrics, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe sits in these lists: Rust community servers: live readings and Vanilla Rust servers, live. 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.
Player count
Where does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe sit in the rankings?
Player hours over the last seven days put [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe at #3,296, #308 in Asia, in the top 15% of all ranked servers.
What is the population on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
0 of 150 slots are filled on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe right now. Check: players over seven days. Average 1, peak 7. Average at the busiest hour was 5 players, at 10:00 UTC over the last 48 hours.
Operator and location
What location is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe hosted in?
Its EA tag places [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe in Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 153.197.161.35:28017.
What Rust version is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe on?
Reading: [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.
Is performance on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe within range?
Check: fps. Average 99 server fps over the last 48 hours, low of 81. Within range. Reading: 122,965 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,550 MB. What players call lag comes from low fps and an entity count on the rise.
Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe up, and how often does it stay up?
[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe reports online. Status: normal. By its reported uptime, the last restart was roughly 19 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Settings and map
How is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe configured, and what rules are in force?
No gather rate appears in the name: [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Plugin count: Carbon. It describes itself as vanilla. The meaning given: rates, kits and rules are exactly as Facepunch ships them. Entry needs Rust's premium status. Anti-cheat reading: VAC on, Valve's system.
Which map is live on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
From seed 930824030, the game generates the procedural map on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. Its size is 4,500. View it on RustMaps from this page: matching size and seed give an identical map.
Join
How can you get onto [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
To join: start Rust, press F1 and type client.connect 153.197.161.35:28017. Or press Launch Rust here and Steam opens the game and connects you. Entry needs Rust's premium status.