Offline 218.40.83.125:28015 checked 3d ago
Junichi & Saki PVE
Connect
srv = rust.server("218.40.83.125:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 bestTop 24% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 00:32 UTC4d ago | 1 | NaN | running | 0 |
# 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
- 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
- 25 Oct 2026, 00:32 UTC
- hostname
- –
- first seen
- 3 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 249 on average | 317/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 240 on average | 143/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 103 on average | 161/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 60 on average | 21/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 53 on average | 64/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 51 on average | 14/100 |
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 #5,376, in the top 24% of the ranked set.
How many players does Junichi & Saki PVE hold at once?
Offline now for Junichi & Saki PVE, with the last sample 3 days 13 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
About the server
What is the Rust version on Junichi & Saki PVE?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Junichi & Saki PVE. Joining needs the same protocol on your game; Steam handles the update.
Is Junichi & Saki PVE up, and what does its uptime show?
Junichi & Saki PVE is offline at this refresh; the last response came 3 days 13 hours ago. 39 of 168 hours up over the last 7 full days, or 23%. Its earliest recorded date in Rust Data is 3 October 2026.
In which location is Junichi & Saki PVE hosted?
For Junichi & Saki PVE, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 218.40.83.125:28015 is its address.
Rules, settings, map
What rules and settings are recorded for Junichi & Saki PVE?
You will not find a gather rate in the string Junichi & Saki PVE. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Junichi & Saki PVE loaded?
A procedural map runs on Junichi & Saki PVE, generated by the game.
Wipe data
On what schedule does Junichi & Saki PVE wipe?
The record for Junichi & Saki PVE holds too few wipes to show a rhythm. 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 4 days ago.
On Junichi & Saki PVE, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which Rust Data filters and lists contain Junichi & Saki PVE?
The Rust Data lists that Junichi & Saki PVE fits are: Modded Rust servers 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 Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on Junichi & Saki PVE?
The game's server browser reads these tags from Junichi & Saki PVE: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^p (PvE): PvE: the world is the threat, not other players; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^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.
Join steps
What is the way into Junichi & Saki PVE?
Enter client.connect 218.40.83.125:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.