Rust Server IndexCard catalogue of Rust servers

Holdings11,792 servers68,594 players191 fresh wipes

Call no.4566 On the shelf · online

[JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER

Online 115.179.53.170:28015 checked 13m ago

Subjects 1. monthly wipes 2. modded3. oxide4. pve
Players now
0/ 88
0% full
7-day average
0
peak 4
Rank
#4,566
top 21%
Last wipeWiped2 OCT2026 · 27d 7h ago
27d ago · monthly schedule
Next wipe
7d 6h
Thu 5 Nov, 19:00 UTC FW
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
00.511.5213:0022:0007:0016:0002:0011:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

010020030040013:0022:0007:0016:0002:0011:00

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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 21% of all ranked servers. Ranked on player hours over the last seven days.

Record sheet D · loan terms

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h. The force wipe · high confidence

wipe-day peak
10players, last three wipes

Coming wipes

  1. in 7d 6hThu 5 Nov, 19:00 UTCFW
  2. in 35d 6hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

02.557.510+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 10, 33 hours in.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
2 OCT 2026Fri 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

EA
[坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱EA · groups of 8+ · monthly · 35 on average
40/ 100
EA
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average
22/ 88
EA
[熊猫PVE]修仙升级/召唤/据点/10月新档正式服EA · groups of 8+ · monthly · 12 on average
15/ 100
EA
[JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 11 on average
22/ 100
EA
【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 11 on average
19/ 200
EA
新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简EA · groups of 16+ · monthly · 10 on average
14/ 100
Reference desk

Quick answers

From the figures on this page.

Map and rules

What settings and rules does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER run?

You will find no gather rate in the name of [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER. The group limit is 8 players, the game's default. The server runs pve, no PvP fighting. Plugins or settings change the game; it is listed under Modded in the server browser. Filed under plugins: Oxide. VAC is on: Valve's anti-cheat is enabled.

Which map is in use on [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER?

Size 3,500, seed 1337: the game generates the procedural map on [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER. The map can be seen on RustMaps from this page, because the same size and seed give the same map. Filed under map name: Custom Map.

Tags and filters

On Rust Server Index, which lists and filters carry [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER?

The Rust Server Index lists that include [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER are Modded Rust servers, filed by play style and Rust PvE servers, filed A to Z. Filed under these filters on the server 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.

What is meant by the tags on [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER?

The server's own tags are listed here, and the game's server browser reads them: [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER gives gmrust (Game mode): Survival on standard Rust rules; mp88 (Max players): The queue ceiling sits at 88; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): Build on file: 168909; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): The region code field is left empty; ^m (Monthly): The wipe schedule is monthly, alongside the Facepunch force wipe; ^p (PvE): No fighting between players: the danger comes from the world; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): This one is Modded, since plugins or settings change how it plays. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.

Wipes and resets

What happens on wipe day at [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER?

Its recent wipes averaged 10 players at peak. 33 hours into the latest wipe, the crowd reached its peak.

Which wipe timetable does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER follow?

One wipe a month is all [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER runs, and it comes with the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Its present world dates from 27 days 7 hours. Filed in its tags: a monthly wipe schedule.

Players and ranking

Where does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER sit in the rankings?

Filed under rankings: #4,566 for [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER on seven-day player hours, top 21% overall.

What does the player count on [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER look like?

The live count for [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER stands at 0 players, out of 88 slots. The seven-day average is 0 players; the peak reached 4. The busiest point in the last 48 hours was 04:00 UTC, averaging 2 players.

Operator and status

What version does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER use?

Rust network protocol 2635 and build 168909 on Windows is what you will find on [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER. The protocol must match before you can join, and Steam takes care of updating it.

What is the uptime and current status of [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER?

Right now [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER is up and running. About 13 hours ago, by its own uptime figure, is when it last restarted. Uptime for the last 7 full days came to 99%, 167 hours out of 168. On 13 September 2026 it was first seen by Rust Server Index.

Is the performance on [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER good?

The last 48 hours give an average of 249 server fps and a floor of 99. Buildings, deployables and everything else in the world came to as many as 78,862 entities. The peak memory figure stood at 2,582 MB. What players feel as lag is low fps together with a rising entity count.

Where in the world is [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER hosted?

No region tag is published by [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER; the name it carries points to Asia. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 115.179.53.170:28015.

Connecting

What steps lead onto [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER?

Enter client.connect 115.179.53.170:28015 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you. The website can be found at https://twitter.com/magadonamekuji.

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Survival on standard Rust rules.
mp88
Max players The queue ceiling sits at 88.
ts8
Group limit Teams cap at 8, the default setting.
v2635
Protocol Your client must run protocol 2635 to connect.
cs168909
Build Build on file: 168909.
ptrak
Networking Networking runs on RakNet, the game's default layer.
$r?
Region code The region code field is left empty.

Wipe schedule

^m
Monthly The wipe schedule is monthly, alongside the Facepunch force wipe.

Gameplay

^p
PvE No fighting between players: the danger comes from the world.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded This one is Modded, since plugins or settings change how it plays.

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.