On the class lists: C− (58), with population over 48 hours and no performance mark.
Players now3/ 2002% full
7-day average138peak 562
Rank#104top 0.5%
Last wipe6d agoweekly schedule
Next wipe11hFri 30 Oct, 10:01 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
69/ 100
C+
Draws a healthy crowd: 138 of 200 on average.
Standingrank on player hours
100/ 100
A+
Near the very top of the school: #104 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
80/ 100
B+
Mostly smooth: 48 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
84/ 100
B+
Climbing fast: up 71 places this week.
A steady term.
Strongest in standing (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
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 0.5% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····W··
····W··
····W··
····W··
····W··
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Friday 30 October, 10:01 UTC, in 11h.
Every Friday at 10:01 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak453players, last three wipes
crowd held0%else halves by day 3
Coming wipes
11hFri 30 Oct, 10:01 UTC
6d 20hThu 5 Nov, 19:00 UTCFW
7d 11hFri 6 Nov, 10:01 UTC
14d 11hFri 13 Nov, 10:01 UTC
21d 11hFri 20 Nov, 10:01 UTC
28d 11hFri 27 Nov, 10:01 UTC
34d 20hThu 3 Dec, 19:00 UTCFW
35d 11hFri 4 Dec, 10:01 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 562, 6 hours in, with 73 in the queue.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 10:01 UTC6d ago
562+73 queue
–
running
5
Fri 16 Oct, 10:01 UTC13d ago
374+61 queue
halved by day 3
7 days
6
Fri 9 Oct, 10:01 UTC20d ago
424+71 queue
halved by day 3
7 days
7
Fri 2 Oct, 10:02 UTC27d ago
355+21 queue
halved by day 3
7 days
4
Fri 25 Sep, 10:01 UTC34d ago
411+66 queue
halved by day 3
7 days
4
Fri 18 Sep, 10:01 UTC41d ago
430+67 queue
halved by day 2
7 days
8
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
EU · groups of 100+ · 2x · weekly · 122 on average
8 / 200
Quick answers
from the figures on this page
Server facts
Which region is Magic Rust #19 — 2x | Vanilla+ | Pyccкий based in?
The name of Magic Rust #19 — 2x | Vanilla+ | Pyccкий points to Europe, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 185.207.214.27:10000.
How reliable is Magic Rust #19 — 2x | Vanilla+ | Pyccкий, and is it up?
Right now, Magic Rust #19 — 2x | Vanilla+ | Pyccкий is online. The uptime it reports puts the last restart at about 15 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
It averaged 48 server fps over the last 48 hours, with a low of 48. Buildings, deployables and everything else in the world added up to as many as 192,373 entities. Memory use reached up to 5,980 MB. Players feel lag when fps drops and entities pile up.
What Rust version is Magic Rust #19 — 2x | Vanilla+ | Pyccкий on?
Rust network protocol 2635 and build 168909 on Windows is what Magic Rust #19 — 2x | Vanilla+ | Pyccкий runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does Magic Rust #19 — 2x | Vanilla+ | Pyccкий reset?
Wipes come every Friday at 10:01 UTC on Magic Rust #19 — 2x | Vanilla+ | Pyccкий. Expect the next wipe on Friday 30 October at 10:01 UTC. The world it runs now was created 6 days 12 hours. The tags carry a weekly wipe schedule.
What happens on Magic Rust #19 — 2x | Vanilla+ | Pyccкий when wipe day arrives?
Across its recent wipes, the busiest moments averaged 453 players. The latest wipe peaked 6 hours in, with 73 more players queued at that point. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 3 in the wipes where it did not hold.
Population
What position does Magic Rust #19 — 2x | Vanilla+ | Pyccкий hold in the rankings?
In the top 0.5% of all ranked servers, Magic Rust #19 — 2x | Vanilla+ | Pyccкий sits at #104 for player hours over the last seven days.
How many players does Magic Rust #19 — 2x | Vanilla+ | Pyccкий usually have?
Magic Rust #19 — 2x | Vanilla+ | Pyccкий is showing 3 players right now, with 200 slots in total. The seven-day average is 138 players, with a peak of 562. The highest average in the last 48 hours came at 17:00 UTC, with 60 players.
Tags
How should you read the tags on Magic Rust #19 — 2x | Vanilla+ | Pyccкий?
gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): 200 slots are available; ts50 (Group limit): A team can hold 50 players at most; 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): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; jp0 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner are the tags Magic Rust #19 — 2x | Vanilla+ | Pyccкий publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Who is behind Magic Rust #19 — 2x | Vanilla+ | Pyccкий?
The same operator most likely runs Magic Rust #19 — 2x | Vanilla+ | Pyccкий and the 35 other servers we track that also publish a magicrust.gg hostname.
Where does Magic Rust #19 — 2x | Vanilla+ | Pyccкий appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Magic Rust #19 — 2x | Vanilla+ | Pyccкий among them: 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x; Average players: 100+ on average.
Rules and settings
Which rules does Magic Rust #19 — 2x | Vanilla+ | Pyccкий enforce, and what are its settings?
Magic Rust #19 — 2x | Vanilla+ | Pyccкий sets gather at 2x, as its name suggests. A group here can reach 50 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Magic Rust #19 — 2x | Vanilla+ | Pyccкий runs a game-generated procedural map at size 4,000, seed 1112022. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: BAЙП ЧEPEЗ 12 Ч..
How to join
What is the way to join Magic Rust #19 — 2x | Vanilla+ | Pyccкий?
Enter client.connect 185.207.214.27:10000 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://magicrust.gg/serv19.
Server tags
what each one means
Published asmp200,ptrak,jp0,$r?,v2635,^w,gmrust,cs168909,ts50,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max players200 slots are available.
ts50
Group limitA team can hold 50 players at most.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
jp0
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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 steady term. Strongest in standing (A+); wipes are the one to work on (F).