RUST METRICSFlight deck · live data
Data live Servers11,709 Players54,841 Populated3,244 Fresh wipes 3 h155 Scan5 min
‹ All servers197.88.250.25:28015
Offline Full Queue Fresh wipe Wipe due No query

Mikoshi | Solo PvE 10x

Offline 197.88.250.25:28015 checked 22h ago

10x moddedoxidepve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak 1
Rank#8,694top 39%
Last wipe2d agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75112:0014:0007:0008:0010:0012:00

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Oct27 Oct28 Oct29 Oct

Top 39% 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 07:09 UTC2d ago 1 – running 1

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 timing

What happens on Mikoshi | Solo PvE 10x when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does Mikoshi | Solo PvE 10x follow?

The rhythm of Mikoshi | Solo PvE 10x's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 2 days 3 hours ago.

Tag meanings

How should you read the tags on Mikoshi | Solo PvE 10x?

These are the tags Mikoshi | Solo PvE 10x publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Mikoshi | Solo PvE 10x?

These Rust Metrics lists carry Mikoshi | Solo PvE 10x: 10x Rust servers, Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days; Gather rate: 10x.

Player count

What position does Mikoshi | Solo PvE 10x hold among Rust servers?

Ranking for Mikoshi | Solo PvE 10x: #8,694 on seven-day player hours, top 39% of all ranked servers.

What is the population on Mikoshi | Solo PvE 10x?

Reading for Mikoshi | Solo PvE 10x: offline at this moment; last seen 22 hours ago. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 1 players, at 08:00 UTC over the last 48 hours.

Server details

Which location does Mikoshi | Solo PvE 10x run from?

No region comes from Mikoshi | Solo PvE 10x. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 197.88.250.25:28015.

What Rust version is Mikoshi | Solo PvE 10x on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by Mikoshi | Solo PvE 10x. Check: protocol. To join, your game must match; Steam handles the update.

Is Mikoshi | Solo PvE 10x up, and how often does it stay up?

Reading: offline. Mikoshi | Solo PvE 10x last answered 22 hours ago. Reading: 27% uptime over the last 2 full days. It was up 13 of 48 hours. Check: first contact. Rust Metrics logged it on 26 October 2026.

Settings and map

What settings and rules apply on Mikoshi | Solo PvE 10x?

Gather rate check: 10x. That comes from the name Mikoshi | Solo PvE 10x. The group cap is 8 players, which is the default in the game. pve, fighting between players is off — that is the game mode. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Mikoshi | Solo PvE 10x?

Procedural map on Mikoshi | Solo PvE 10x, made by the game's generator.

Join

How do you connect to Mikoshi | Solo PvE 10x?

Check: join. Open Rust, press F1, then enter client.connect 197.88.250.25:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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 It runs Oxide, also known as uMod.
^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.