Rust Data LabData lab · live
Live readings Servers11,701 Players40,419 Populated3,002 Fresh wipes · 3h95 Sampled every 5 min

Element card · group Vanilla · atomic number 3,324, its rank

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe

Online EA 153.197.161.35:28017 checked 7m ago

biweekly wipes vanillacarbonpremium
Join the experiment
Atomic mass · players now 1/ 150 1% full Room to join
7-day average1peak 7
Rank · atomic number#3,324top 15% · #310 in EA
Last wipe12d agobiweekly schedule
Next wipe1d 2hFri 30 Oct, 04:32 UTC
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0246802:0011:0020:0005:0014:0000:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
05010015020002:0011:0020:0005:0014:0000:00

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 15% of all ranked servers, top 55% in EA. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 04:32 UTC, in 1d 2h. Its biweekly schedule tag · low confidence

usual gap14.2 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak5players, last three wipes
crowd held0%else halves by day 7.5

Coming wipes

  1. 1d 2hFri 30 Oct, 04:32 UTC
  2. 7d 17hThu 5 Nov, 19:00 UTCFW
  3. 15d 2hFri 13 Nov, 04:32 UTC
  4. 29d 2hFri 27 Nov, 04:32 UTC
  5. 35d 17hThu 3 Dec, 19:00 UTCFW
  6. 43d 2hFri 11 Dec, 04:32 UTC

The first 48 hours of its last wipes

Fri 16 OctThu 1 OctThu 17 Sep
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 28 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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
  1. 1 Ru Rustoria.co - … 3
    Rustoria.co - SEA Medium EA · groups of 16+ · biweekly · 66 on average 3/ 200
  2. 2 Ja Japan Tokyo - … 15
    Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com EA · groups of 8+ · biweekly · 41 on average 15/ 215
  3. 3 Ru Rustafied.com … 5
    Rustafied.com - SEA Medium EA · groups of 16+ · biweekly · 27 on average 5/ 100
  4. 4 Ru [SEA/KR/JP] Ru… 0
    [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla EA · groups of 8+ · biweekly · 4 on average 0/ 200
  5. 5 Jp JP ONLY 2WEEK … 1
    JP ONLY 2WEEK SOLO/DUO/TORIO#84 EA · groups of 8+ · biweekly · 3 on average 1/ 60
  6. 6 Br [SEA] BRUNEI/M… 1
    [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 2 on average 1/ 100

Quick answers

from the figures on this page

Server setup

What map is in play on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

A procedural map of size 4,500 with seed 930824030 runs on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, generated by the game. Same size and seed give the same map, so this page lets you look at it on RustMaps.

What rules has [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe set, and what settings are in force?

Nothing in the name of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe gives a gather rate. With no change from the default, groups can hold up to 8 players. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. It appears under Community in the server browser. Plugins in use: Carbon. The server describes itself as vanilla: standard rates, kits and rules, exactly as Facepunch ships the game. Entry is limited to players who hold Rust's premium status. Anti-cheat is on: Valve's VAC.

Server facts

What region hosts [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe gives Asia as its location, using the EA tag. Rust Data Lab shows a server's stated location, not a verified position of the machine. You will find it at 153.197.161.35:28017.

What Rust version does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe currently run?

On Linux, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is running Rust network protocol 2635 and build 168909. The protocol must match for you to join; Steam will update your game.

Does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe stay up, and how reliable is its uptime?

Right now, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is reachable. About 3 hours ago is when it last restarted, based on its uptime. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. The first sighting by Rust Data Lab was on 13 September 2026.

Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe known for smooth running?

Server fps averaged 99 over the last 48 hours, with 81 as the lowest. The entity count reached 122,965, including buildings, deployables and all other world items. Memory use peaked at 4,550 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipe days

What is the wiping pattern on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

Its tag guides the prediction, since [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe's record holds too few wipes to confirm a schedule. The wipe after this one is due on Friday 30 October at 04:32 UTC. 12 days 21 hours ago the current world was made. A two-weekly wipe schedule is published in its tags.

On [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, what happens when wipe day arrives?

At their busiest, recent wipes averaged 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. Where it did not hold, the crowd dropped below half by day 7.5.

Where it appears

What should you understand from the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe carries?

These are the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe makes public for the server browser to read: gmrust (Game mode): Survival in the standard Rust style; mp150 (Max players): 150 is the slot count; ts8 (Group limit): This uses the game's default: 8 per team; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): It runs build 168909; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): No region code is set; ^b (Biweekly): Wipes come around once a fortnight; ^v (Vanilla): Standard rates, kits and rules, exactly as Facepunch ships the game; ^y (Carbon): The plugin framework here is Carbon; ^q (Premium): Entry is limited to players who hold Rust's premium status; EA (East Asia): East Asia is where the browser lists this server. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Where among the Rust Data Lab lists and filters does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe come up?

You will find [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe on the following Rust Data Lab lists: Rust community servers, measured and Vanilla Rust servers, measured. 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.

Whose server is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

2 other servers we track publish a crypto-cheer.jp hostname as well, which makes one operator the likely runner of them and [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe.

Player counts

How does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe compare with other servers in the rankings?

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is #3,324 on seven-day player hours, #310 in Asia, and in the top 15% of all ranked servers.

What does the current player count on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe tell you?

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe currently shows 1 players across 150 slots. A seven-day sample gives 1 players on average and 7 at the top. The busiest point in the last 48 hours came at 10:00 UTC, averaging 5 players.

How to join

What steps get you onto [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

You can connect by pressing F1 in Rust and entering client.connect 153.197.161.35:28017, or by pressing Launch Rust here, which starts the game through Steam and joins for you. Entry is limited to players who hold Rust's premium status.

Server tags

what each one means

Published as mp150,ptrak,$r?,v2635,^y,^b,^v,EA,gmrust,cs168909,^q,ts8

Game

gmrust
Game mode Survival in the standard Rust style.
mp150
Max players 150 is the slot count.
ts8
Group limit This uses the game's default: 8 per team.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs168909
Build It runs build 168909.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Wipes come around once a fortnight.

Difficulty

^v
Vanilla Standard rates, kits and rules, exactly as Facepunch ships the game.

Mods and access

^y
Carbon The plugin framework here is Carbon.
^q
Premium Entry is limited to players who hold Rust's premium status.

Region

EA
East Asia East Asia is where the browser lists this server.

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.