[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
Online EA 153.197.161.35:28017 checked 7m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 16% of all ranked servers, top 61% 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 19h. Its biweekly schedule tag · low confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 1d 19h | Fri 30 Oct, 04:32 UTC | its own |
| 8d 10h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 15d 19h | Fri 13 Nov, 04:32 UTC | its own |
| 29d 19h | Fri 27 Nov, 04:32 UTC | its own |
| 36d 10h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 43d 19h | Fri 11 Dec, 04:32 UTC | its own |
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 FW26d ago | 4 | halved by day 9 | 14.4 days | 0 |
| Thu 17 Sep, 19:00 UTC40d 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 | Profile | Players now |
|---|---|---|
| Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 77 on average | 39 / 200 |
| Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 47 on average | 20 / 215 |
| Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 31 on average | 14 / 100 |
| [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 5 on average | 0 / 200 |
| JP ONLY 2WEEK SOLO/DUO/TORIO#84 | EA · groups of 8+ · biweekly · 3 on average | 2 / 60 |
| [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly | EA · groups of 8+ · biweekly · 2 on average | 0 / 100 |
Quick answers
from the figures on this pageWipe cycle
When does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe wipe?
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. A wipe is scheduled for Friday 30 October at 04:32 UTC, according to this server's cycle. 12 days 3 hours ago the current world was made. The tags carry an every-two-weeks wipe schedule.
Wipe day on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: what should you expect?
Recent wipes averaged a busiest count of 5 players. The highest player count on the latest wipe arrived 28 hours in. Above half that peak until the next wipe held in 0% of recent wipes. The fall below half arrived by day 7.5 when it didn't hold.
Server
What is the hosting location of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
The EA tag on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe lists it in Asia. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. You will find it at 153.197.161.35:28017.
Which Rust version is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe on?
On Linux, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe runs Rust network protocol 2635 and build 168909. The protocol has to match before you can join; Steam updates it automatically.
Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe up, and how steady is its uptime?
The current status of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is online. Its reported uptime indicates a restart roughly 10 hours ago. 100% uptime over the last 7 full days, equal to 168 of 168 hours. The first sighting of it by Rust Server Analytics was on 13 September 2026.
What performance does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe show?
Over 48 hours the average held at 98 server fps, and the minimum was 80. Entity count reached 122,965, covering buildings, deployables and the rest of the world. Peak memory was 4,466 MB. Players experience lag as low fps combined with a rising entity count.
Lists and tags
Which meanings do the tags on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe carry?
gmrust (Game mode): Survival in the standard Rust format; mp150 (Max players): Capacity of 150 slots; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): The region code is blank; ^b (Biweekly): Wipes come once a fortnight; ^v (Vanilla): Nothing altered from Facepunch's release: rates, kits and rules are stock; ^y (Carbon): It runs Carbon for plugins; ^q (Premium): Only premium-status players can connect; EA (East Asia): Its browser listing sits in East Asia are the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes, and the game's server browser reads them. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe fits are: Community Rust servers, live 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.
Who operates [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
2 other servers we track publish a crypto-cheer.jp hostname too, and so does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, which points to a shared operator.
Player numbers
What position does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe hold in the server rankings?
Ranked on seven-day player hours, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is #3,524 overall and #334 in Asia, within the top 16% of ranked servers.
How many players does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe carry?
Of 150 slots, 2 are filled on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe at this refresh. Averaging 1 players across seven days, the server reached a peak of 7. Across the last 48 hours, 10:00 UTC shows the highest average: 5 players.
Settings
How is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe configured, and what rules apply?
Gather rate is not mentioned in the name of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe. No custom group limit: 8 players is the standard. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. Community is its listing; it is a community server. The plugin framework is Carbon. Vanilla is its own description: nothing altered from Facepunch's release: rates, kits and rules are stock. Only premium-status players can connect. The server runs with VAC, Valve's anti-cheat, enabled.
What is the map for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe uses a procedural map of size 4,500 with seed 930824030, generated by the game. Size and seed fix the map, so a RustMaps view is available from this page.
Connection
How do you connect to [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 153.197.161.35:28017. Only premium-status players can connect.