Working its way up from the back of the class: #15,983 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
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
21/ 100
F
Lost ground: down 9,112 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (D); momentum 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.
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
····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 Sunday 1 November, 13:38 UTC, in 3d 14h.
Its biweekly schedule tag · low confidence
usual gap7.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 12
Coming wipes
3d 14hSun 1 Nov, 13:38 UTC
7d 19hThu 5 Nov, 19:00 UTCFW
17d 14hSun 15 Nov, 13:38 UTC
31d 14hSun 29 Nov, 13:38 UTC
35d 19hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Sun 4 OctFri 2 OctFri 18 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 13:38 UTC24d ago
1
–
running
0
Fri 2 Oct, 11:11 UTC26d ago
1
✓ held half
2.1 days
0
Fri 18 Sep, 17:08 UTC40d ago
1
halved by day 12
13.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 MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad sit?
No region is published for MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 116.202.139.157:28015.
Is MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad up, and how steady is its uptime?
At this moment, MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad is offline; the last time it was seen was 23 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 13 September 2026.
Which Rust version is MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad running?
Rust network protocol 2634 and build 166652 on Windows is what MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad reset?
Its tag sets the prediction, as the record holds too few of MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad's wipes to confirm its schedule. It is due to wipe next on Sunday 1 November at 13:38 UTC. The world it runs now was created 24 days 9 hours. Its tags say it wipes every two weeks.
What happens on MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 0 hours after it began. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. Day 12 is when it sank below half in the wipes that did not hold.
Population
Where does MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad place in the wider field of Rust servers?
In the top 71% of all ranked servers, MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad sits at #15,983 for player hours over the last seven days.
How many players does MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad usually have?
MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad is offline at the moment; the last time it was seen was 23 days 12 hours ago.
Tags and filters
How should you read the tags on MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad?
The game's browser takes its cue from the tags MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^b (Biweekly): Every two weeks it wipes; ^y (Carbon): Carbon provides the plugin framework here; ^q (Premium): Joining requires premium status on Rust. 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.
Where does MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad appear in the Rust Server Score lists and filters?
Rust Server Score lists that include MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and Plugins, not modded; Game mode: Premium; Server tag: Biweekly ^b, Premium ^q and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks.
Rules and settings
How is MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad set up, and what rules does it keep?
Nothing in the name of MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Carbon. Joining requires premium status on Rust. You are covered by VAC, Valve's anti-cheat.
Which map is in play on MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad?
A procedural map of size 4,500 and seed 88235019, generated by the game, is what MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How do you get onto MGCDRP | DE Biweekly | Solo/Duo/Trio/Quad?
To connect, start Rust, press F1, and type client.connect 116.202.139.157:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. Joining requires premium status on Rust. You can find its website at https://link.mgcdrp.de/discord.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^y,^b,gmrust,cs166652,^q,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^y
CarbonCarbon provides the plugin framework here.
^q
PremiumJoining requires premium status on Rust.
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 wipe hold (D); momentum is the one to work on (F).