Rust Server TrendsSeismic network · station log
Recording Stations11,701 Players40,419 Active3,002 Wipes · 3 h95 48 h

Station XX-918 · recording

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

Online 175.130.55.150:28015 checked 10m ago

moddedoxidepve
Connect
Players now
6/ 88
7% full
Motion · 24 h
M0.0rising
+1 players on the day
7-day average
11
peak 34
Rank
#918
top 4%
Last wipe
27d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-918 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
6of 88 slots
Motion · 24 h
M0.0rising+1 players
Sharpest hour
+8into Tue 10:00 UTC
Peak · 48 h
30most players in any hour
Channel 1 · calibrated

Players

AveragePeak
01020304002:0011:0020:0005:0014:0000:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020002:0011:0020:0005:0014:0000: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12505007501k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Expected events

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 gap
6 daysbetween real wipes
wipe-day peak
62players, last three wipes
crowd held
0%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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 17:46 UTC FW27d ago M1.8rising 78+17 queue – running 19
Fri 25 Sep, 16:44 UTC33d ago M1.5rising 47+11 queue halved by day 5 6 days 15

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 60 on average
30/ 200
QS『鱼山路』pve|耐玩|升级|突袭 EA · groups of 8+ · 37 on average
42/ 100
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼 EA · groups of 8+ · monthly · 35 on average
30/ 100
Japan Tokyo - Vanilla PvE|JP|Beginner EA · groups of 16+ · 34 on average
19/ 100
Japan Tokyo - Chill PvE|JP EA · groups of 16+ · 21 on average
14/ 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 21 on average
16/ 88
Readings, in words

Quick answers

from the figures on this page

Rules and settings

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

[JP][PvE]またーりRUST[BP] runs a procedural map of size 4,500 with seed 1337, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. The name of its map is またーりカスタムMAP.

Which settings and rules apply on [JP][PvE]またーりRUST[BP]?

No gather rate appears in the name of [JP][PvE]またーりRUST[BP]. The group limit is 10 players. In pve mode, no player-versus-player fighting. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on [JP][PvE]またーりRUST[BP]?

At this moment, [JP][PvE]またーりRUST[BP] records 6 players across 88 slots. Averaged across the last seven days the population was 11 players, reaching a peak of 34. The last 48 hours show their highest activity at 14:00 UTC, averaging 28 players.

How does [JP][PvE]またーりRUST[BP] rank against other Rust servers?

On player hours for the past week, [JP][PvE]またーりRUST[BP] sits at #918, which puts it inside the top 4% of every ranked server.

Operator and location

How reliably does [JP][PvE]またーりRUST[BP] stay online?

As recorded now, [JP][PvE]またーりRUST[BP] is running. Going by the uptime figure it reports, it restarted about 2 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does [JP][PvE]またーりRUST[BP] perform under load?

Across the last 48 hours it averaged 126 server fps, with a floor of 31. Buildings, deployables and all the rest of the world's entities brought it to a high of 213,416. Memory use peaked at 5,626 MB. Low fps together with a growing entity count is what players experience as lag.

Which region does [JP][PvE]またーりRUST[BP] run from?

The name of [JP][PvE]またーりRUST[BP] points to Asia, even though it publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 175.130.55.150:28015 is the address it uses.

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

[JP][PvE]またーりRUST[BP] is running Rust network protocol 2635 and build 168909 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on [JP][PvE]またーりRUST[BP]?

On average, the busiest point of its recent wipes drew 62 players. 20 hours after the latest wipe the crowd peaked, with 17 waiting in the queue. Half that peak was held until the next wipe in 0% of its recent wipes. It fell under half by day 5 in the wipes where it didn't hold.

How often does [JP][PvE]またーりRUST[BP] wipe, and on which days?

The rhythm of [JP][PvE]またーりRUST[BP] cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 27 days 8 hours.

Server tags

What do the server tags on [JP][PvE]またーりRUST[BP] mean?

Tags published by [JP][PvE]またーりRUST[BP] and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp88 (Max players): Slots: 88; ts10 (Group limit): Teams are capped at 10 players; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does [JP][PvE]またーりRUST[BP] appear?

The Rust Server Trends lists that take in [JP][PvE]またーりRUST[BP] are: Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: 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.

How to join

How do you connect to [JP][PvE]またーりRUST[BP]?

Enter client.connect 175.130.55.150:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://mtr-rust.jimdosite.com/.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp88
Max players Slots: 88.
ts10
Group limit Teams are capped at 10 players.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.