Working its way up from the back of the class: #15,437 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 264 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·WW····
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap0.6 daysbetween real wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Wed 21 OctTue 20 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 21 Oct, 14:29 UTC7d ago
0
–
running
0
Tue 20 Oct, 23:14 UTC8d ago
0
–
0.6 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
Which region is MGCDRP | RustPvEDE - TestServer based in?
You'll find no region listed by MGCDRP | RustPvEDE - TestServer. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 213.220.150.92:28025 is the address to use.
How reliable is MGCDRP | RustPvEDE - TestServer, and is it up?
At this moment, MGCDRP | RustPvEDE - TestServer is offline; the last time it was seen was 7 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 20 October 2026.
On what Rust version does MGCDRP | RustPvEDE - TestServer sit?
The server MGCDRP | RustPvEDE - TestServer is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does MGCDRP | RustPvEDE - TestServer wipe, and how often?
MGCDRP | RustPvEDE - TestServer has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 7 days 13 hours.
What happens on MGCDRP | RustPvEDE - TestServer when wipe day arrives?
Recent wipes have peaked at 0 players on average. Peak numbers came 0 hours into the latest wipe.
Player count
What position does MGCDRP | RustPvEDE - TestServer hold in the rankings?
Over the last seven days, MGCDRP | RustPvEDE - TestServer has #15,437 for player hours, in the top 69% of all ranked servers.
Is MGCDRP | RustPvEDE - TestServer a busy server?
MGCDRP | RustPvEDE - TestServer is offline at the moment; the last time it was seen was 7 days 12 hours ago.
Lists and filters
How should you read the tags on MGCDRP | RustPvEDE - TestServer?
gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): 100 slots are available; ts24 (Group limit): Teams cap out at 24; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags MGCDRP | RustPvEDE - TestServer publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature MGCDRP | RustPvEDE - TestServer?
These Rust Server Score lists count MGCDRP | RustPvEDE - TestServer among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
What settings and rules apply on MGCDRP | RustPvEDE - TestServer?
You will find no gather rate in the name of MGCDRP | RustPvEDE - TestServer. A group here can reach 24 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Connecting
How do you get onto MGCDRP | RustPvEDE - TestServer?
To connect, start Rust, press F1, and type client.connect 213.220.150.92:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmvanilla,cs167781,ts24,^z,^y
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max players100 slots are available.
ts24
Group limitTeams cap out at 24.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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 momentum (D); standing is the one to work on (F).