Station EA-3296 · recording
[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
Online EA 153.197.161.35:28017 checked 9m ago
- Players now
- 0/ 150
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 7
- Rank
- #3,296
- top 15% · #308 in EA
- Last wipe
- 12d ago
- biweekly schedule
- Next wipe
- 1d 7h
- Fri 30 Oct, 04:32 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 150 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +4into Tue 10:00 UTC
- Peak · 48 h
- 7most players in any hour
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 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 7h. 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
- 1d 7hFri 30 Oct, 04:32 UTC
- 7d 22hThu 5 Nov, 19:00 UTCFW
- 15d 7hFri 13 Nov, 04:32 UTC
- 29d 7hFri 27 Nov, 04:32 UTC
- 35d 22hThu 3 Dec, 19:00 UTCFW
- 43d 7hFri 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 16 Oct, 04:32 UTC12d ago | M0.7▲rising | 5 | – | running | 0 | |
| Thu 1 Oct, 19:05 UTC FW27d ago | M0.6▲rising | 4 | halved by day 9 | 14.4 days | 0 | |
| Thu 17 Sep, 19:00 UTC41d ago | M0.8▲rising | 7 | halved by day 6 | 14 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Generated by the game, the map on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is procedural, size 4,500 with seed 930824030. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
You will find no gather rate in the name of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Under Community in the server browser, it runs as a community server. Its plugins are run through Carbon. It describes itself as vanilla, which means rates, kits and rules are as Facepunch ships them. Rust's premium status is required to join. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe right now?
At this moment, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe records 0 players across 150 slots. The seven-day average is 1 players, with a peak of 7. Averaged over the last 48 hours, the busiest hour was 10:00 UTC at 5 players.
How does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe rank against other Rust servers?
For player hours across the last seven days, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe takes #3,296 overall and #308 in Asia, inside the top 15% of all ranked servers.
Server facts
How reliably does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe stay online?
[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is up at the moment. Going by the uptime figure it reports, it restarted about 19 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. 13 September 2026 is when Rust Server Trends first recorded it.
Does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe hold a steady tick rate?
Across the last 48 hours it averaged 99 server fps, with a floor of 81. The world held up to 122,965 entities at its peak, buildings and deployables included. It reached a ceiling of 4,550 MB of memory. Low fps together with a growing entity count is what players experience as lag.
Which region does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe run from?
The EA tag is how [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe lists itself in Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 153.197.161.35:28017.
What build of Rust does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe use?
On Linux, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
The recent wipes averaged a busiest count of 5 players. 28 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell under half by day 7.5 in the wipes where it didn't hold.
On what timetable does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe run its wipes?
The prediction is taken from its tag, since [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe has too few wipes on record to confirm the schedule. The date of its next wipe is Friday 30 October at 04:32 UTC. 12 days 16 hours is how long the current world has been running. Its tags state that it wipes every two weeks.
Lists and tags
What do the server tags on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe mean?
Tags published by [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp150 (Max players): 150 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): Rates, kits and rules are as Facepunch ships them; ^y (Carbon): A plugin framework, Carbon, runs here; ^q (Premium): Rust's premium status is required to join; EA (East Asia): In the server browser it appears under East Asia. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe appear?
The Rust Server Trends lists that take in [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe are: Rust community servers without the side modes and Vanilla Rust servers, recorded live. 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?
Both [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe and 2 other servers we track publish a crypto-cheer.jp hostname, so the same operator most likely runs them.
How to join
What steps get you onto [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Enter client.connect 153.197.161.35:28017 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. Rust's premium status is required to join.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.