Rust Data

rustdata.spaceservers197.88.250.25:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 197.88.250.25:28015 checked 1d ago

Mikoshi | Solo PvE 10x

10x moddedoxidepve

Connect

srv = rust.server("197.88.250.25:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak 1
rank #8,669 # top 39%
last wipe 2d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75107:0008:0009:0010:0011:0012:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 07:09 UTC2d ago 1 NaN 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
197.88.250.25:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
27 Oct 2026, 07:09 UTC
hostname
–
first seen
26 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[EU] RustValley 10x PVE+ |Legendary Weapons| Raidable Bases|EU · groups of 15+ · 10x · biweekly · 53 on average67/100
1[US] RustValley 10x PVE+ |Legendary Weapons| Raidable Bases| LoNA · groups of 15+ · 10x · biweekly · 44 on average35/100
2[BR/LATAM] RustValley 10x PVE+ |Armas Lendarias| Raidable BasesSA · groups of 15+ · 10x · biweekly · 26 on average33/100
3[EU] RustValley 10x PVE |#2| Legendary Weapons|RaidableBasesEU · groups of 15+ · 10x · biweekly · 19 on average20/100
4[BR/LATAM] MASTERS | 10X PVE++ |ARMAS LENDÁRIAS|EPIC TOOLS|SA · groups of 8+ · 10x · biweekly · 10 on average9/100
5[EU] RustValley 10x PVE |#3| Legendary Weapons|RaidableBasesEU · groups of 15+ · 10x · biweekly · 9 on average11/100

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Mikoshi | Solo PvE 10x rank?

Rank #8,669 on seven-day player hours for Mikoshi | Solo PvE 10x, within the top 39% of all ranked servers.

How full does Mikoshi | Solo PvE 10x run?

Offline now for Mikoshi | Solo PvE 10x, with the last sample 33 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 08:00 UTC is the busiest, at 1 players.

Server facts

What Rust version does Mikoshi | Solo PvE 10x run?

The build is Rust network protocol 2635 and build 168909 on Windows, run by Mikoshi | Solo PvE 10x. The protocol has to match before you can join, and Steam does the updating.

How reliable is Mikoshi | Solo PvE 10x, and is it online now?

The latest sample has Mikoshi | Solo PvE 10x offline, with a last sighting 33 hours ago. 13 of 48 hours up over the last 2 full days, or 27%. Rust Data logged it first on 26 October 2026.

Where does Mikoshi | Solo PvE 10x sit?

For Mikoshi | Solo PvE 10x, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 197.88.250.25:28015.

Settings and map

Which rules apply on Mikoshi | Solo PvE 10x, and what settings?

10x gather is what the name states, and the name is Mikoshi | Solo PvE 10x. Eight players per group: that is the game's default, and it applies here. Game mode pve, with this note: player combat is not allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has Mikoshi | Solo PvE 10x loaded?

A procedural map runs on Mikoshi | Solo PvE 10x, generated by the game.

Wipes and dates

On what schedule does Mikoshi | Solo PvE 10x wipe?

A rhythm cannot be read from the wipes of Mikoshi | Solo PvE 10x on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 2 days 14 hours ago.

What is wipe day on Mikoshi | Solo PvE 10x like?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.

Tags, lists

Where does Mikoshi | Solo PvE 10x appear among Rust Data lists and filters?

On Rust Data, Mikoshi | Solo PvE 10x appears in these lists: Modded Rust servers, 10x Rust servers: the live sample and Rust PvE servers. These filters bring it up on the server list: 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.

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

Read by the game's server browser, the tags Mikoshi | Solo PvE 10x publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

What is the way to join Mikoshi | Solo PvE 10x?

In Rust, F1 opens the console: type client.connect 197.88.250.25:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players 10 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Gameplay

^p
PvE Players do not fight each other here; the world supplies the danger.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 85,544 players 11,830 servers online