Rust Data

rustdata.spaceservers218.40.83.125:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 218.40.83.125:28015 checked 30d ago

Junichi & Saki PVE

moddedcarbonpve

Connect

srv = rust.server("218.40.83.125:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 1/4 # 25% full
7-day average 0 # peak –
rank #14,558 # top 61%
last wipe 36d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

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
15k10k15k20k20 Sep23 Sep26 Sep28 Sep1 Oct4 Oct

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

usual gap2.5 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 22 SepSat 19 Sep
00.511.52+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 22 Sep, 04:35 UTC36d ago 1 NaN running 1
1 Sat 19 Sep, 17:26 UTC38d ago 2 held half 2.5 days 2

# 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
218.40.83.125:28015
region
–
max players
4
group limit
8, the default
wipe schedule
–
last wipe
22 Sep 2026, 04:35 UTC
hostname
–
first seen
18 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 246 on average48/2000
1[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 236 on average159/2000
2Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 100 on average4/200
3【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 58 on average83/200
4TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 52 on average43/100
5[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 52 on average29/300

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Junichi & Saki PVE rank?

Player hours over seven days put Junichi & Saki PVE at #14,558, in the top 61% of the ranked set.

What population does Junichi & Saki PVE carry?

The current row shows Junichi & Saki PVE offline; the last response was 30 days 21 hours ago.

Server facts

Which Rust version is Junichi & Saki PVE on?

Rust network protocol 2633 and build 164530 on Windows is what Junichi & Saki PVE runs. Joining needs the same protocol on your game; Steam handles the update.

Is Junichi & Saki PVE up, and what does its uptime show?

The latest sample has Junichi & Saki PVE offline, with a last sighting 30 days 21 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 18 September 2026.

In which location is Junichi & Saki PVE hosted?

For Junichi & Saki PVE, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 218.40.83.125:28015 is its address.

Settings and map

Which rules apply on Junichi & Saki PVE, and what settings?

The name Junichi & Saki PVE carries no gather rate. No custom cap; the default of 8 players per group stands. pve is the game mode here, and no combat between players. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.

What is the map on Junichi & Saki PVE?

Junichi & Saki PVE runs a procedural map, which the game generates.

Wipe data

On what schedule does Junichi & Saki PVE wipe?

A rhythm cannot be read from the wipes of Junichi & Saki PVE on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 36 days 5 hours ago.

On Junichi & Saki PVE, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Lists and tags

Which Rust Data filters and lists contain Junichi & Saki PVE?

These Rust Data lists include Junichi & Saki PVE: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.

How should you read the server tags on Junichi & Saki PVE?

Read by the game's server browser, the tags Junichi & Saki PVE publishes are: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): Slot count: 4; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): The server runs build 164530; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^p (PvE): PvE: the world is the threat, not other players; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way to join Junichi & Saki PVE?

The manual route: launch Rust, F1, then client.connect 218.40.83.125:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp4,ptrak,$r?,v2633,^z,^y,^p,gmrust,cs164530,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp4
Max players Slot count: 4.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol To join, your game must run protocol 2633.
cs164530
Build The server runs build 164530.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

Mods and access

^z
Modded Modded listing: the game is changed by plugins or settings.
^y
Carbon The plugin framework in use is Carbon.

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 55,436 players 11,682 servers online