Skip to the page
Every Rust server graded on real, live numbers. 35,442 players on the roll · 11,620 servers present
Rust Server ScoreReport for the October 2026 term
Rust Server Score · Report for the term · marked 29 October 2026 Pupil no. 153.197.161.35:28017
Name of server

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

RegisterPresentOnline
RegionEA
Address153.197.161.35:28017
Last checked13m ago
biweekly wipes vanillacarbonpremium
Launch Rust and join
Overall grade

Getting there

57 out of 100, the average of 6 subjects

On the class lists: D (49), with population over 48 hours and no performance mark.

Players now 2/ 150 1% full
7-day average1peak 7
Rank#3,286top 15% · #294 in EA
Last wipe13d agobiweekly schedule
Next wipe21hFri 30 Oct, 04:32 UTC

Subjects

SubjectMarkGradeTeacher's comment
Populationplayers against slots, 7-day average 1/ 100 A quiet classroom so far: 1 of 150 on average. Plenty of space to grow.
Standingrank on player hours 85/ 100 Holds a respectable place: #3,286 on player hours.
Uptimehours on the list, last 48 96/ 100 Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours 100/ 100 Runs smoothly: 98 server fps on average.
Wipeskeeping the crowd after a wipe 0/ 100 Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago 62/ 100 Moving up: up 809 places this week.

A fair term, with more to come. Strongest in performance (A+); wipes are the one to work on (F).

How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.

Progress through the term

Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.

Players

AveragePeak
0246807:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

Server performance

05010015020007:0016:0001:0010:0020:0005: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.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Attendance: the wipe record

3 wipe days in the last 16 weeks

W wiped that day F the force wipe · today. From the wipes in the table below.

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 04:32 UTC, in 21h. 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

  • 21hFri 30 Oct, 04:32 UTC
  • 7d 12hThu 5 Nov, 19:00 UTCFW
  • 14d 21hFri 13 Nov, 04:32 UTC
  • 28d 21hFri 27 Nov, 04:32 UTC
  • 35d 12hThu 3 Dec, 19:00 UTCFW
  • 42d 21hFri 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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 04:32 UTC13d 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

classmates: the same kind of game, then region, group limit, rate and wipes
Rustoria.co - SEA Medium
EA · groups of 16+ · biweekly · 64 on average
26 / 200
Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com
EA · groups of 8+ · biweekly · 41 on average
13 / 215
Rustafied.com - SEA Medium
EA · groups of 16+ · biweekly · 27 on average
13 / 100
[SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla
EA · groups of 8+ · biweekly · 4 on average
9 / 200
JP ONLY 2WEEK SOLO/DUO/TORIO#84
EA · groups of 8+ · biweekly · 3 on average
0 / 60
[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

About the server

Where in the world is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

You'll see [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe listed in Asia, tagged EA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 153.197.161.35:28017.

How dependable is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe, and is it online at the moment?

You can join now: [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is online. About 8 hours ago, it restarted, based on the uptime it reports. It was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.

Does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe perform well?

The average over the last 48 hours was 98 server fps, and it never went below 81. Buildings, deployables and everything else in the world added up to as many as 122,965 entities. At its highest, it used 4,550 MB of memory. Lag is what players feel when fps is low and the entity count climbs.

What Rust version is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe on?

The server [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.

Resets

On what schedule does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe reset?

Too few wipes on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe are recorded to confirm the schedule, so its tag guides the prediction. Friday 30 October at 04:32 UTC is the date set for its next wipe. 13 days 2 hours have passed since this world was made. Its tags say it wipes every two weeks.

What should you expect from wipe day on [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

The average peak on its recent wipes was 5 players. Peak numbers came 28 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. Day 7.5 is when it sank below half in the wipes that did not hold.

Population

What position does [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe hold in the rankings?

In Asia, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe is #294, and overall it is #3,286 on player hours over the last seven days, in the top 15% of all ranked servers.

Is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe a busy server?

With 150 slots available, [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe currently has 2 players. It peaked at 7 and averaged 1 players over the last seven days. The highest average in the last 48 hours came at 10:00 UTC, with 5 players.

Tags and filters

What do [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe's tags stand for?

You'll see [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp150 (Max players): 150 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^y (Carbon): Plugin framework: Carbon; ^q (Premium): You need Rust's premium status to get in; EA (East Asia): In the server browser it appears under East Asia in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.

Who operates [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 tracked servers, which suggests one operator.

Which Rust Server Score filters and lists feature [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

Rust Server Score lists that include [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe: Best community servers, graded and Vanilla Rust servers, graded. It shows under the following 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.

Map and rules

How is [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe set up, and what rules does it keep?

The name of [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. Carbon plugins are running on it. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. You need Rust's premium status to get in. The server runs Valve's anti-cheat, VAC.

[JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe runs which map?

A procedural map of size 4,500 and seed 930824030, generated by the game, is what [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.

Connecting

How should you connect to [JP] INAKA Vanilla Bi-weekly | 10/16 MAP Wipe?

Enter client.connect 153.197.161.35:28017 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You need Rust's premium status to get in.

Server tags

what each one means

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

Game

gmrust
Game mode Rust survival, played by the standard rules.
mp150
Max players 150 slots are available.
ts8
Group limit Teams are capped at 8, the game's standard setting.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet handles it, the game's default network layer.
$r?
Region code A region code is not set here.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^v
Vanilla Nothing is altered here: rates, kits and rules are as Facepunch ships them.

Mods and access

^y
Carbon Plugin framework: Carbon.
^q
Premium You need Rust's premium status to get in.

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.