[JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER
Online 115.179.53.170:28015 checked 6m ago
Measurements
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 9h. The force wipe · high confidence
Coming wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 10, 33 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 04:18 UTC27d ago | 10 | – | 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.
Quick answers
Player counts
How does [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER rank against other Rust servers?
The last seven days of player hours place [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER at #4,464, within the top 20% of all ranked servers.
How busy is [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER?
Of its 88 slots, [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER is using 0 right now. Averaged over seven days, it drew 0 players and reached a peak of 4. In the last 48 hours the peak hour came at 10:00 UTC, averaging 2 players.
Lists and tags
What do the server tags on [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER mean?
These are the tags [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER publishes, as read by the game's server browser: gmrust (Game mode): Survival in the standard Rust style; mp88 (Max players): 88 slots are available; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): Your game needs the same version, protocol 2635, to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): No region code is set; ^m (Monthly): This server wipes once a month, at the same time as Facepunch's force wipe; ^p (PvE): Players do not fight each other; the world supplies the danger; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER?
On Rust Population, [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER is filed under these lists: Modded Rust servers, counted and PvE servers, counted. These are the filters it appears under when you browse the list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Wipe schedule
What does wipe day look like on [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER?
The busiest point of its recent wipes averaged 10 players. 33 hours after the latest wipe the crowd peaked.
What is the wipe schedule on [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER?
Once a month [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER wipes, and that is with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe, which takes every Rust server. Counted from 27 days 3 hours ago, that is how long the current world has stood. A monthly wipe schedule is what its tags publish.
Settings
Which map does [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER run?
A procedural map of size 3,500 from seed 1337, generated by the game, is in use on [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER. The map follows from its size and seed, and RustMaps shows it from this page. The name on the map is Custom Map.
What are the rules and settings on [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER?
Nothing in [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER's name says how gather works. The group limit is 8 players, which is the default. pve is what it runs, no player combat. The server browser files it under Modded, where plugins or settings alter the game. The plugins it runs are Oxide. The anti-cheat VAC from Valve is enabled.
About the server
Which version of Rust does [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER run?
Rust network protocol 2635 and build 168909 on Windows is what [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER uses. Steam updates your game automatically, but you need the same protocol to join.
Does [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER run smoothly?
It ran at 245 server fps on average over the last 48 hours, and never went below 99. Up to 78,862 entities were present, counting buildings, deployables and everything else. The highest memory usage was 2,582 MB. Lag, as players feel it, is low fps combined with a climbing entity count.
Is [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER online, and how reliable is it?
Right now, [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER is online. Judging by the uptime it reports, the last restart was about 9 hours ago. It was up 99% of the time over the last 7 full days, 167 out of 168 hours. On 13 September 2026, Rust Population saw it for the first time.
Where is [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER located?
The name of [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER points to Asia, though it publishes no region tag. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 115.179.53.170:28015.
Getting in
How do I join [JP-PvE]まがど鯖 S47｜Plugins[170+] | MAGADO_SERVER?
To connect directly, open Rust's console with F1 and type client.connect 115.179.53.170:28015; or press Launch Rust on this page and Steam opens Rust and joins for you. You can find its website at https://twitter.com/magadonamekuji.