Statistical profileOnline
[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
EA 153.197.161.35:28017 checked 12m ago
Connect to this server
1. Main points
Players now
0/ 150
0% full
7-day average
1
peak 7
Rank
#3,324
top 15% · #310 in EA
Last wipe
12d ago
biweekly schedule
Next wipe
1d 3h
Fri 30 Oct, 04:32 UTC
Main points
- There were 0 players on it, 0% of its 150 slots.
- Over the last seven days it averaged 1 players, with a peak of 7.
- It ranks #3,324 of all ranked servers, the top 15%, and #310 in EA, on player hours over the last seven days.
- Its current map went up 12d ago; the next wipe is expected Friday 30 October, 04:32 UTC, its biweekly schedule tag.
2. Players
Figure 1: Players on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 15% of all ranked servers, top 55% in EA. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternfrom its schedule tag
Next wipe Friday 30 October, 04:32 UTC, in 1d 3h. Its biweekly schedule tag · low confidence
Usual gap
14.2 days
between real wipes
On rhythm
100%
of its recent wipes
Wipe-day peak
5
players, last three wipes
Crowd held
0%
else halves by day 7.5
Table 1: Coming wipes
Expected from its own rhythm and the force wipe
| In | Date and time | Kind |
|---|---|---|
| 1d 3h | Fri 30 Oct, 04:32 UTC | Own schedule |
| 7d 17h | Thu 5 Nov, 19:00 UTC | Force wipe FW |
| 15d 3h | Fri 13 Nov, 04:32 UTC | Own schedule |
| 29d 3h | Fri 27 Nov, 04:32 UTC | Own schedule |
| 35d 17h | Thu 3 Dec, 19:00 UTC | Force wipe FW |
| 43d 3h | Fri 11 Dec, 04:32 UTC | Own schedule |
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 5, 28 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 2: Wipes, newest first
Every wipe seen on this server
| 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 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
4500 · seed 930824030
![Map of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe](https://files.facepunch.com/rust/map-images/000d130a8b16864a29201104d9f8362ccf02bcb5fec9e0d64495bdbc50a1db95/proceduralmap.4500.1792125126196.289_000d130a8b16864a29201104d9f8362c.jpg)
Table 3: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | 4500 |
| Seed | 930824030 |
8. Server characteristics
Table 4: Characteristics of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe
What the server publishes and what was recorded
| Address | 153.197.161.35:28017 |
|---|---|
| Region | EA |
| Max players | 150 |
| Group limit | 8, the default |
| Wipe schedule | biweekly |
| Last wipe | 16 Oct 2026, 04:32 UTC |
| Hostname | inaka2.crypto-cheer.jp |
| First seen | 13 Sep 2026 |
9. Operator
Hostnamecrypto-cheer.jp
Table 5: Other servers of this operator
The busiest servers publishing a crypto-cheer.jp hostname
| Server | Status | Players |
|---|---|---|
| [JP] まったりクマ鯖 x3 | 10/02 BP Wipe | Online | 0 / 100 |
| [JP]Rustテストサーバー | Online | 0 / 100 |
3 servers publish a crypto-cheer.jp hostname.
10. About this server
In its own words: the description the server publishes, unedited.
JP Only!! ※新規アカウント及びプロフィールが非公開の場合はログインできません Full wipe on force wipe. Map wipe on the 3rd, and 5th Friday of the month.. This server will reboot every morning at 5:30 (JST). IP address changes irregularly to avoid DDOS. Please speak Japanese or English in Global Chat.(speaking other languages may result in being kicked or banned.) Banned acts: spamming, hate speech, abusive language, racist remarks, harassment, goosing, sniping. Have a good time! Do not cheat! Have a good time. Do not cheating!! rs01$8:aozJ^0rAi4001$Y
11. Similar servers
Table 6: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 66 on average | 3 / 200 |
| Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 41 on average | 14 / 215 |
| Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 27 on average | 5 / 100 |
| [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 4 on average | 0 / 200 |
| JP ONLY 2WEEK SOLO/DUO/TORIO#84 | EA · groups of 8+ · biweekly · 3 on average | 1 / 60 |
| [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly | EA · groups of 8+ · biweekly · 2 on average | 1 / 100 |
12. Quick answers
From the figures on this page.
Wipe schedule
This release records the wipe timetable for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: what is it?
Too few wipes of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe are recorded to confirm its schedule, so its tag is followed by the prediction. On Friday 30 October at 04:32 UTC the next wipe is expected. This world was generated 12 days 20 hours ago. Its tags carry a wipe schedule of every two weeks.
On [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, what happens on wipe day?
Recent wipes drew an average peak of 5 players. On the latest wipe, 28 hours passed before the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. If not, it dropped below half by day 7.5.
Server record
How reliable is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, and is it online now?
[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is online at the time of this release. By its own reported uptime, it restarted about 2 hours ago. 167 of 168 hours on across the last 7 full days gives an uptime of 99%. It was first seen by Rust Census on 13 September 2026.
Does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe hold a steady frame rate and connection?
The figures for the last 48 hours give an average of 98 server fps and a minimum of 81. The world carried up to 122,965 entities, including buildings, deployables and all else. Memory use reached 4,550 MB at its peak. What players experience as lag is low fps combined with a climbing entity count.
In which location is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe based?
With its EA tag, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe lists itself in Asia. Rust Census does not look up where the machine stands; it shows where a server says it is. 153.197.161.35:28017 is its address.
Which Rust version is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe running?
This release lists [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe on Rust network protocol 2635 and build 168909, running on Linux. To join, your game has to be on the same protocol; Steam handles the update.
Player figures
How many players does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe carry?
The present count is 0 players on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, out of 150 slots. Averaged over seven days: 1 players, with a peak of 7. Over the past 48 hours the highest average fell at 10:00 UTC: 5 players.
How does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe compare with other servers in the rankings?
On player hours over the last seven days [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe stands at #3,324, #310 in Asia, in the top 15% of ranked servers.
Tag details
On Rust Census, which lists and filters carry [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Included in these Rust Census lists is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: Community servers and Vanilla 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.
Who is listed as 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 and by 2 other servers we track, so the same operator most likely runs them.
What is meant by each tag shown on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Read by the game's server browser, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe publishes these tags: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp150 (Max players): Slots: 150; ts8 (Group limit): This is the game default: 8 to a team; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): Build 168909 is installed; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): No region code is set; ^b (Biweekly): This server wipes on a two-week cycle; ^v (Vanilla): This is the unmodified game: rates, kits and rules as Facepunch ships them; ^y (Carbon): Plugins are handled by Carbon on this server; ^q (Premium): Joining requires premium status on Rust; EA (East Asia): In the server browser it appears under East Asia. At the top of this page you will find the tags for current players, queue and world creation time.
Settings and map
Which map has been recorded for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
The procedural map on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is generated by the game, measures 4,500 and carries seed 930824030. Because one size and seed give one map, RustMaps can display it from this page.
On [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, what rules and settings are in force?
No gather rate is recorded for [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe in its name. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. Community is its section in the server browser. The plugin count is Carbon. Vanilla is its own description: this is the unmodified game: rates, kits and rules as Facepunch ships them. Joining requires premium status on Rust. The server runs VAC, Valve's anti-cheat.
Join details
How can you connect to [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?
Enter client.connect 153.197.161.35:28017 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you. Joining requires premium status on Rust.
13. Server tags
What each tag this server publishes means: a glossary.
Published asmp150,ptrak,$r?,v2635,^y,^b,^v,EA,gmrust,cs168909,^q,ts8
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp150 | Max players Slots: 150. |
ts8 | Group limit This is the game default: 8 to a team. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs168909 | Build Build 168909 is installed. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code No region code is set. |
Wipe schedule
^b | Biweekly This server wipes on a two-week cycle. |
|---|
Difficulty
^v | Vanilla This is the unmodified game: rates, kits and rules as Facepunch ships them. |
|---|
Mods and access
^y | Carbon Plugins are handled by Carbon on this server. |
|---|---|
^q | Premium Joining requires premium status on Rust. |
Region
EA | East Asia In the server browser it appears under 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.