On the class lists: F (37), with population over 48 hours and no performance mark.
Players now1/ 1001% full
7-day average16peak 57
Rank#833top 4% · #68 in EA
Last wipe5d agoweekly schedule
Next wipe1d 11hFri 30 Oct, 08:54 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
16/ 100
F
A quiet classroom so far: 16 of 100 on average. Plenty of space to grow.
Standingrank on player hours
96/ 100
A+
Well up the rankings: #833 on player hours.
Uptimehours on the list, last 48
8/ 100
F
Attendance needs work: on the list only 4 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 150 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
79/ 100
B
Climbing fast: up 483 places this week.
A term to build on.
Strongest in performance (A+); wipes are 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
No five-minute samples in the last two hours.
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 4% of all ranked servers, top 12% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
W··WW··
····W··
····W··
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Friday 30 October, 08:54 UTC, in 1d 11h.
Its weekly schedule tag · low confidence
usual gap7 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak37players, last three wipes
crowd held0%else halves by day 5
Coming wipes
1d 11hFri 30 Oct, 08:54 UTC
7d 21hThu 5 Nov, 19:00 UTCFW
8d 11hFri 6 Nov, 08:54 UTC
15d 11hFri 13 Nov, 08:54 UTC
22d 11hFri 20 Nov, 08:54 UTC
29d 11hFri 27 Nov, 08:54 UTC
35d 21hThu 3 Dec, 19:00 UTCFW
36d 11hFri 4 Dec, 08:54 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 54, 28 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 08:54 UTC5d ago
54
–
running
0
Fri 16 Oct, 08:57 UTC12d ago
20
halved by day 5
7 days
2
Fri 9 Oct, 08:36 UTC19d ago
36
halved by day 3
7 days
8
Thu 8 Oct, 15:57 UTC20d ago
36
–
0.7 days
0
Mon 5 Oct, 05:15 UTC23d ago
3+1 queue
–
3.4 days
0
Fri 18 Sep, 09:18 UTC40d ago
4
halved by day 6
16.8 days
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 [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 sit?
In Asia, according to its own listing, sits [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23, with the EA tag. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 61.79.202.112:28015 is the address to use.
How reliable is [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23, and is it up?
The server is down: [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 is offline now, with the last sighting 44 hours ago. The uptime it reports puts the last restart at about 2 hours ago. For the last 7 full days, it was up 146 of 168 hours, or 87% of the time. It was first seen by Rust Server Score on 17 September 2026.
How well does [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 run?
It never fell below 110 server fps in the last 48 hours, averaging 150. Buildings, deployables and everything else in the world added up to as many as 161,420 entities. Memory use reached up to 3,360 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 sit?
You will find [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 wipe its map?
The prediction follows its tag, because too few of [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23's wipes are on record to confirm the schedule. Expect the next wipe on Friday 30 October at 08:54 UTC. It has been running its current world for 5 days 12 hours. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23?
The average peak on its recent wipes was 37 players. Peak numbers came 28 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. Day 5 is when it sank below half in the wipes that did not hold.
Player numbers
Where does [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 place in the wider field of Rust servers?
Over the last seven days, [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 has #833 for player hours, in the top 4% of all ranked servers and #68 in Asia.
How many players does [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 usually have?
[KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 is offline at the moment; the last time it was seen was 44 hours ago. The seven-day average is 16 players, with a peak of 57. Over the last 48 hours, the peak hour was 22:00 UTC, averaging 3 players.
Lists and filters
What do [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23's tags stand for?
You'll see [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^w (Weekly): A wipe happens every week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; EA (East Asia): In the server browser it appears under East Asia in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23: 2x Rust servers, graded, Best community servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Weekly ^w and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x; Average players: 10+ on average.
Rules and settings
Which rules does [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 enforce, and what are its settings?
[KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 sets gather at 2x, as its name suggests. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
[KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 runs which map?
The game generates the procedural map on [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23 at size 3,600 with seed 168576. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto [KR/JP] MAGI서버 / 자원X2 / WIPE 10.23?
Enter client.connect 61.79.202.112:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,^v,EA,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Region
EA
East AsiaIn the server browser it appears under East Asia.
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 term to build on. Strongest in performance (A+); wipes are the one to work on (F).