On the class lists: D (52), with population over 48 hours and no performance mark.
Players now0/ 880% full
7-day average0peak 4
Rank#4,644top 21%
Last wipe27d agomonthly schedule
Next wipe7d 2hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 88 on average. Plenty of space to grow.
Standingrank on player hours
79/ 100
B
Holds a respectable place: #4,644 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 241 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
36/ 100
F
Slipped a little: down 1,270 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
daily · 1 is best
RankRank in region
Top 21% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h.
The force wipe · high confidence
wipe-day peak10players, last three wipes
Coming wipes
7d 2hThu 5 Nov, 19:00 UTCFW
35d 2hThu 3 Dec, 19:00 UTCFW
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
newest first
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER sit?
You won't find a region tag on [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER, but its name indicates Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 115.179.53.170:28015.
Is [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER up, and how steady is its uptime?
Right now, [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER is online. About 16 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Is [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER smooth to play on?
It never fell below 99 server fps in the last 48 hours, averaging 249. At its peak, it held 78,862 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,582 MB. When fps is low and entities climb, that is lag to players.
On what Rust version does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER sit?
Rust network protocol 2635 and build 168909 on Windows is what [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER wipe its map?
The force wipe each month is the only wipe [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER takes. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 27 days 10 hours. Its tags record that it wipes monthly.
What happens on [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER when wipe day arrives?
Recent wipes have peaked at 10 players on average. 33 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER sit among Rust servers?
Over the last seven days, [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER has #4,644 for player hours, in the top 21% of all ranked servers.
How many players does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER usually have?
With 88 slots available, [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER currently has 0 players. It peaked at 4 and averaged 0 players over the last seven days. Over the last 48 hours, the peak hour was 04:00 UTC, averaging 2 players.
Lists and filters
What do [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp88 (Max players): 88 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: 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.
Server rules
Which rules does [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER enforce, and what are its settings?
You will find no gather rate in the name of [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER. With no change from the game default, groups take up to 8 players. pve is the mode here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER uses?
The game generates the procedural map on [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER at size 3,500 with seed 1337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.
Getting in
How do you get onto [JP-PvE]まがど鯖 S47|Plugins[170+] | MAGADO_SERVER?
Enter client.connect 115.179.53.170:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://twitter.com/magadonamekuji.
Server tags
what each one means
Published asmp88,ptrak,$r?,v2635,^m,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp88
Max players88 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).