Skip to the page
Every Rust server graded on real, live numbers. 65,813 players on the roll · 11,842 servers present
Rust Server ScoreReport for the October 2026 term
Rust Server Score · Report for the term · marked 27 October 2026 Pupil no. 175.130.55.150:28015
Name of server

[JP][PvE]またーりRUST[BP]

RegisterPresentOnline
Region–
Address175.130.55.150:28015
Last checked7m ago
moddedoxidepve
Launch Rust and join Website
Overall grade

Getting there

58 out of 100, the average of 6 subjects

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

Players now 0/ 88 0% full
7-day average11peak 34
Rank#894top 4%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet

Subjects

SubjectMarkGradeTeacher's comment
Populationplayers against slots, 7-day average 13/ 100 A quiet classroom so far: 11 of 88 on average. Plenty of space to grow.
Standingrank on player hours 96/ 100 Well up the rankings: #894 on player hours.
Uptimehours on the list, last 48 98/ 100 Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours 100/ 100 Runs smoothly: 126 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 44/ 100 Slipped a little: down 112 places this week. Nothing a good wipe can't fix.

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
01020304023:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

05010015020023:0008:0017:0003:0012:0021: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
12505007501k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 4% of all ranked servers. Ranked on player hours over the last seven days.

Attendance: the wipe record

2 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

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap6 daysbetween real wipes
wipe-day peak62players, last three wipes
crowd held0%else halves by day 5

The first 48 hours of its last wipes

Thu 1 OctFri 25 Sep
020406080+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 78, 20 hours in, with 17 in the queue.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 17:46 UTC FW26d ago 78+17 queue – running 19
Fri 25 Sep, 16:44 UTC32d ago 47+11 queue halved by day 5 6 days 15

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
【炮炮PVE启蒙】纯净｜特色｜突袭｜技能
EA · groups of 16+ · biweekly · 60 on average
17 / 200
[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本
EA · groups of 8+ · monthly · 36 on average
21 / 100
QS『鱼山路』pve｜耐玩｜升级｜突袭
EA · groups of 8+ · 36 on average
13 / 100
Japan Tokyo - Vanilla PvE|JP|Beginner
EA · groups of 16+ · 35 on average
11 / 100
Japan Tokyo - Chill PvE|JP
EA · groups of 16+ · 21 on average
7 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地
EA · groups of 8+ · monthly · 21 on average
17 / 88

Quick answers

from the figures on this page

About the server

In what location does [JP][PvE]またーりRUST[BP] sit?

The name of [JP][PvE]またーりRUST[BP] points to Asia, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 175.130.55.150:28015 is the address to use.

Is [JP][PvE]またーりRUST[BP] up, and how steady is its uptime?

Right now, [JP][PvE]またーりRUST[BP] is online. The uptime it reports puts the last restart at about 12 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.

Does [JP][PvE]またーりRUST[BP] perform well?

It averaged 126 server fps over the last 48 hours, with a low of 31. Buildings, deployables and everything else in the world added up to as many as 211,099 entities. Up to 5,626 MB of memory was used. When fps is low and entities climb, that is lag to players.

Which Rust version is [JP][PvE]またーりRUST[BP] running?

The server [JP][PvE]またーりRUST[BP] is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.

Wipe schedule

When does [JP][PvE]またーりRUST[BP] wipe, and how often?

There are too few wipes on record for [JP][PvE]またーりRUST[BP] to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 26 days 4 hours.

What happens on [JP][PvE]またーりRUST[BP] when wipe day arrives?

Across its recent wipes, the busiest moments averaged 62 players. 20 hours after the latest wipe began the crowd peaked, and 17 more were in the queue. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 5 in the wipes where it did not hold.

Player count

Where does [JP][PvE]またーりRUST[BP] sit among Rust servers?

Over the last seven days, [JP][PvE]またーりRUST[BP] has #894 for player hours, in the top 4% of all ranked servers.

Is [JP][PvE]またーりRUST[BP] a busy server?

With 88 slots available, [JP][PvE]またーりRUST[BP] currently has 0 players. The seven-day average is 11 players, with a peak of 34. Over the last 48 hours, the peak hour was 14:00 UTC, averaging 28 players.

Tags and filters

What do [JP][PvE]またーりRUST[BP]'s tags stand for?

The game's browser takes its cue from the tags [JP][PvE]またーりRUST[BP] has set: gmrust (Game mode): Rust survival, played by the standard rules; mp88 (Max players): 88 slots are available; ts10 (Group limit): Teams cap out at 10; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.

Which lists and filters on Rust Server Score show [JP][PvE]またーりRUST[BP]?

Rust Server Score lists that include [JP][PvE]またーりRUST[BP]: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Average players: 10+ on average.

Map and rules

How is [JP][PvE]またーりRUST[BP] set up, and what rules does it keep?

The name of [JP][PvE]またーりRUST[BP] gives no gather rate. You can play in groups of up to 10 players. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.

Which map is in play on [JP][PvE]またーりRUST[BP]?

A procedural map of size 4,500 and seed 1337, generated by the game, is what [JP][PvE]またーりRUST[BP] runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: またーりカスタムMAP.

Connecting

How do you get onto [JP][PvE]またーりRUST[BP]?

Enter client.connect 175.130.55.150:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://mtr-rust.jimdosite.com/.

Server tags

what each one means

Published as mp88,ptrak,$r?,v2635,^p,gmrust,cs168909,ts10,^o^z

Game

gmrust
Game mode Rust survival, played by the standard rules.
mp88
Max players 88 slots are available.
ts10
Group limit Teams cap out at 10.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build This runs on build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code A region code is not set here.

Gameplay

^p
PvE This is player against world: players do not fight each other.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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.