RUST METRICSFlight deck · live data
Data live Servers11,699 Players51,000 Populated3,284 Fresh wipes 3 h142 Scan5 min
‹ All servers175.130.55.150:28015
Online Full Queue Fresh wipe Wipe due No query

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

Online 175.130.55.150:28015 checked 10m ago

moddedoxidepve
COM 1 · connect

Server instruments

last reading Tue 23:00 UTC
0 22 44 66 88 PAX 5 /88

Players now

6% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 150 SERVER FPS

Server fps

48 h low 31 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 207,723 ×1000

Entities

48 h range 189,508–211,099 · memory 4,806 MB
1239 ET SINCE RESTART 01:34

Uptime

1 h 34 min since its last restart, at the last reading
7-day average11peak 34
Rank#900top 4%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Memory4,806MB48 h peak 30 players
REC 1

Players

AveragePeak
01020304001:0010:0019:0005:0014:0023:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020001:0010:0019:0005:0014:0023: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.

REC 3

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.

PLAN

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.

LOG

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

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

An average of 62 players came at the busiest on its recent wipes. 20 hours after the wipe the crowd peaked on the latest wipe, with 17 more in the queue. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. When it didn't hold, by day 5 it fell below half.

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

To tell the rhythm of [JP][PvE]またーりRUST[BP], too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 26 days 6 hours ago.

Lists and filters

Which tags does [JP][PvE]またーりRUST[BP] carry, and what do they mean?

These are the tags [JP][PvE]またーりRUST[BP] publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp88 (Max players): 88 slots in total; ts10 (Group limit): Team cap: 10; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does [JP][PvE]またーりRUST[BP] appear in Rust Metrics lists and filters?

These Rust Metrics lists carry [JP][PvE]またーりRUST[BP]: Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: 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.

Player count

Where does [JP][PvE]またーりRUST[BP] sit in the rankings?

Player hours over seven days put [JP][PvE]またーりRUST[BP] at #900, in the top 4% of all ranked servers.

What player count does [JP][PvE]またーりRUST[BP] carry?

Current headcount on [JP][PvE]またーりRUST[BP]: 5 players, 88 slots available. Seven-day check: 11 players on average. Peak reading: 34. Check: 48-hour peak. 14:00 UTC, 28 players on average.

Operator and location

What location is [JP][PvE]またーりRUST[BP] hosted in?

Reading: location. Nothing in the tags, but the name of [JP][PvE]またーりRUST[BP] points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 175.130.55.150:28015.

What Rust version is [JP][PvE]またーりRUST[BP] on?

Reading: [JP][PvE]またーりRUST[BP], Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

Is performance on [JP][PvE]またーりRUST[BP] within range?

Check: fps. Average 126 server fps over the last 48 hours, low of 31. Within range. Peak entity count: 211,099. Buildings, deployables and all else included. Memory peak: 5,626 MB. Lag, as players feel it, is low fps plus a climbing entity count.

Is [JP][PvE]またーりRUST[BP] up, and how often does it stay up?

Check: connection. [JP][PvE]またーりRUST[BP] is online at this moment. By its reported uptime, the last restart was roughly 1 hours ago. Reading: 86% uptime over the last 7 full days. It was up 144 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

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

Reading the name gives no gather rate for [JP][PvE]またーりRUST[BP]. Check: group limit. Up to 10 players. Mode check gives pve; no combat against other players. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

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

Size 4,500 and seed 1337: the game generates the procedural map on [JP][PvE]またーりRUST[BP] from them. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name またーりカスタムMAP.

Join

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

Press F1 in Rust and enter client.connect 175.130.55.150:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://mtr-rust.jimdosite.com/ is where its website sits.

PLACARDS

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 plain Rust survival.
mp88
Max players 88 slots in total.
ts10
Group limit Team cap: 10.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.