[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe
EA 153.197.161.35:28017 checked 11m ago
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
Top 19% of all ranked servers, top 63% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 15 October, 19:05 UTC, in 1d 11h. Its biweekly schedule tag · low confidence
- usual gap
- 14 days between real wipes
- wipe-day peak
- 6 players, last three wipes
- crowd held
- 0% else halves by day 6
Coming wipes
- 1d 11hThu 15 Oct, 19:05 UTC
- 15d 11hThu 29 Oct, 19:05 UTC
- 22d 10hThu 5 Nov, 19:00 UTCFW
- 29d 11hThu 12 Nov, 19:05 UTC
- 43d 11hThu 26 Nov, 19:05 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 16 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 19:05 UTCFW 12d ago | 4 | – | running | 0 |
| Thu 17 Sep, 19:00 UTC 26d 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
Quick answers
Population
[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe ranking: what position does it hold?
Player hours over the last seven days place [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe at #332 in Asia, and at #4,241 in the top 19% of ranked servers.
Is [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe busy?
[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe: 0 players now, with 150 slots available. The average player count over the last seven days is 1, with a peak of 5. In the last 48 hours, 11:00 UTC saw the highest activity, with an average of 1 players.
Tags and Filters
How should the tags on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe be interpreted?
The game's server browser reads these tags from [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe: gmrust (Game mode): Rust survival, standard; mp150 (Max players): Slot count is 150; ts8 (Group limit): Teams are limited to 8, the default; v2634 (Protocol): Game protocol 2634; the same version is required to join; cs167781 (Build): Running build 167781; ptrak (Networking): Network layer: RakNet, the standard; $r? (Region code): Region code missing; ^b (Biweekly): Two-week wipe cycle; ^v (Vanilla): The game unmodified: rates, kits and rules as Facepunch ships them; ^y (Carbon): Uses Carbon for plugins; ^q (Premium): Access limited to those with Rust's premium status; EA (East Asia): Server browser category: East Asia. Current players, queue and world creation time come from the tags and appear at the top of this page.
[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe operator: who is it?
Both [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe and 2 other servers we track publish a crypto-cheer.jp hostname, so they are most likely run by the same operator.
Which lists and filters on BestRustServers.xyz contain [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
The BestRustServers.xyz lists that include [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe are: Rust community servers, ranked and Vanilla-tagged Rust servers. It appears 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.
Server Information
[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe Rust version: which one?
The combination is Rust network protocol 2634 and build 167781 on Linux for [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe. Steam updates your game automatically, but it needs to match the protocol to join.
Is the performance on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe smooth?
For the past 48 hours, server fps averaged 100, never dropping below 82. It held up to 115,624 entities: everything from buildings to deployables in the world. Memory use peaked at 4,365 MB. What players experience as lag is low fps combined with a rising entity count.
How reliable is [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe and is it online?
The server is online: [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe. The uptime it reports shows a restart roughly 9 hours ago. Over the past 7 full days, it was online 168 of 168 hours, 100% of the time. The first time BestRustServers.xyz saw it was on 13 September 2026.
What is the location of [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
Its EA tag places [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe in Asia. BestRustServers.xyz shows the stated location of a server; the actual location of the machine is not looked up. 153.197.161.35:28017 is its address.
Rules & Map
[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe map: which one is it?
Generated by the game, the map on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe is procedural, size 4,500, seed 452968691. On RustMaps, from this page, the same size and seed show the same map.
What are the settings and rules for [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
A gather rate is not given in the name [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe. With no stated limit, groups default to 8 players. It runs survival, gather, build, raid: the standard game. Raids and PvP are on. Community is its browser category. Plugins in use: Carbon. Self-described as vanilla: the game unmodified: rates, kits and rules as Facepunch ships them. Access limited to those with Rust's premium status. VAC: on.
Wipe Cycle
[JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe wipe schedule: what does it show?
As [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe's record holds too few wipes to confirm its schedule, its tag drives the prediction. Due next is a wipe on Thursday 15 October at 19:05 UTC. Its world dates from 12 days 12 hours. A two-week wipe schedule is given in its tags.
What happens on wipe day on [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
An average peak of 6 players was drawn by its recent wipes. 16 hours after the latest wipe, the crowd hit its peak. Half the peak was held until the next wipe in 0% of its recent wipes. When it fell, the crowd dropped under half by day 6.
How to Join
What is the process to join [JP] INAKA Vanilla Bi-weekly | 10/02 BP Wipe?
Enter client.connect 153.197.161.35:28017 in the console (F1 in Rust), or use Launch Rust on this page to open Steam and connect. Access limited to those with Rust's premium status.
Server tags
Published as mp150,ptrak,$r?,v2634,^y,^b,^v,EA,gmrust,cs167781,^q,ts8
Game
gmrust- Game mode Rust survival, standard.
mp150- Max players Slot count is 150.
ts8- Group limit Teams are limited to 8, the default.
v2634- Protocol Game protocol 2634; the same version is required to join.
cs167781- Build Running build 167781.
ptrak- Networking Network layer: RakNet, the standard.
$r?- Region code Region code missing.
Wipe schedule
^b- Biweekly Two-week wipe cycle.
Difficulty
^v- Vanilla The game unmodified: rates, kits and rules as Facepunch ships them.
Mods and access
^y- Carbon Uses Carbon for plugins.
^q- Premium Access limited to those with Rust's premium status.
Region
EA- East Asia Server browser category: East Asia.
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.