DWG RG-S3297Server sheetchecked 8m ago
[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
Online EA 153.197.161.35:28017 checked 8m 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 15% of all ranked servers, top 55% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 30 October, 04:32 UTC, in 1d 7h. Its biweekly schedule tag · low confidence
Coming wipes
- 1d 7hFri 30 Oct, 04:32 UTC
- 7d 21hThu 5 Nov, 19:00 UTCFW
- 15d 7hFri 13 Nov, 04:32 UTC
- 29d 7hFri 27 Nov, 04:32 UTC
- 35d 21hThu 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
| 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
Quick answers
Server data
Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe online, and what uptime has been recorded?
[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is up at this moment. About 23 hours ago is when it last restarted, measured from the uptime it reports. 168 of 168 hours up over the last 7 full days, which is 100% of the time. First seen by Rust Graphs on 13 September 2026.
Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe stable in the figures recorded?
Average server fps over the last 48 hours is 98; the lowest was 81. Counted at its highest: 122,965 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 4,550 MB. Players feel low fps and a climbing entity count as lag.
What location is recorded for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
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 Graphs shows; no lookup of the machine's location is made. 153.197.161.35:28017 is its address.
What Rust version is recorded for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Rust network protocol 2635 and build 168909 on Linux: that is what [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe runs. To join, your game must be on the same protocol; Steam handles the update.
Population
What player count is recorded on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Current player count on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: 0, of 150 slots. Averaged across seven days, the player count is 1, with a peak of 7. The 48-hour peak falls at 10:00 UTC, averaging 5 players.
What rank has been recorded for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Across seven days, player hours give [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe #3,297 globally and #309 in Asia, a top 15% position among ranked servers.
Schedules
What is recorded on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe on wipe day?
The recent wipes averaged a busiest count of 5 players. At 28 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 7.5.
Which times and days are wipes plotted at on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Its tag is followed for the prediction: too few of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe's wipes are on record to confirm the schedule. Friday 30 October at 04:32 UTC is the date its next wipe is due. The world it runs now was made 12 days 16 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.
Settings
What settings and rules apply on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Gather rate for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. It appears under Community in the server browser. The plugin count is Carbon. Its own label is vanilla, meaning no changed rates, kits or rules: the game as Facepunch ships it. Rust's premium status is required to join. VAC is on: that is Valve's anti-cheat.
Which map has [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe loaded?
Size 4,500 with seed 930824030: that is the procedural map [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Lists and filters
Where does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe appear among the Rust Graphs lists and filters?
These Rust Graphs lists include [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: Rust community servers, plotted and Vanilla Rust servers. These filters on the server list return it: 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.
On [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, what is meant by each tag?
gmrust (Game mode): Survival in standard Rust style; mp150 (Max players): 150 player slots; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^y (Carbon): The plugin framework is Carbon; ^q (Premium): Rust's premium status is required to join; EA (East Asia): In the server browser it appears under East Asia are the tags [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Who is the operator of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
A crypto-cheer.jp hostname is published by [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, as it is by 2 other servers we track; the same operator most likely runs them.
Joining the server
By what method do you join [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Enter client.connect 153.197.161.35:28017 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. Rust's premium status is required to join.
Server tags
Published as mp150,ptrak,$r?,v2635,^y,^b,^v,EA,gmrust,cs168909,^q,ts8
Game
gmrust
mp150
ts8
v2635
cs168909
ptrak
$r?
Wipe schedule
^b
Difficulty
^v
Mods and access
^y
^q
Region
EA
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.