Station XX-14558 · no signal
Junichi & Saki PVE
Offline 218.40.83.125:28015 checked 30d ago
- Players now
- 1/ 4
- 25% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,558
- top 61%
- Last wipe
- 35d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 4 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 2.5 daysbetween real wipes
- wipe-day peak
- 2players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 22 Sep, 04:35 UTC35d ago | M0.0■steady | 1 | – | running | 1 | |
| Sat 19 Sep, 17:26 UTC38d ago | M0.0■steady | 2 | held half | 2.5 days | 2 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on Junichi & Saki PVE?
Junichi & Saki PVE uses a procedural map, which the game generates.
Which settings and rules apply on Junichi & Saki PVE?
You will find no gather rate in the name of Junichi & Saki PVE. At the game's default, groups can have up to 8 players. In pve mode, no combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on Junichi & Saki PVE?
A reading taken now finds Junichi & Saki PVE offline; the most recent activity was 30 days 8 hours ago.
How does Junichi & Saki PVE rank against other Rust servers?
On player hours for the past week, Junichi & Saki PVE sits at #14,558, which puts it inside the top 61% of every ranked server.
Operator and location
How reliably does Junichi & Saki PVE stay online?
As recorded now, Junichi & Saki PVE is not reachable, the last contact having been 30 days 8 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 18 September 2026 is when Rust Server Trends first recorded it.
Which region does Junichi & Saki PVE run from?
Nothing about a region comes from Junichi & Saki PVE. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 218.40.83.125:28015.
Which Rust version is Junichi & Saki PVE running?
On Windows, Junichi & Saki PVE runs Rust network protocol 2633 and build 164530. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on Junichi & Saki PVE?
The recent wipes averaged a busiest count of 2 players. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 100% of its recent wipes.
How often does Junichi & Saki PVE wipe, and on which days?
Too few wipes of Junichi & Saki PVE are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 35 days 16 hours is how long the current world has been running.
Lists and tags
What do the server tags on Junichi & Saki PVE mean?
These are the tags Junichi & Saki PVE publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp4 (Max players): 4 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs164530 (Build): It runs game build 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^p (PvE): The danger comes from the world, not from other players; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Junichi & Saki PVE appear?
These Rust Server Trends lists include Junichi & Saki PVE: Modded Rust servers, tracked live 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.
How to join
What steps get you onto Junichi & Saki PVE?
You can connect by pressing F1 in Rust and typing client.connect 218.40.83.125:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.