On the class lists: F (31), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak –
Rank#15,289top 69%
Last wipe5d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 40 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,289 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); 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
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.
AveragePeak
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 26 Oct. 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
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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 MunichGamers - Rust Server sit?
MunichGamers - Rust Server leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 93.104.168.84:28015.
How dependable is MunichGamers - Rust Server, and is it online at the moment?
You cannot join now: MunichGamers - Rust Server is offline, last seen 2 days 5 hours ago. It was up 10 of 48 hours over the last 2 full days, which is 21% of the time. On 26 October 2026, Rust Server Score saw it for the first time.
Which Rust version is MunichGamers - Rust Server running?
Rust network protocol 2635 and build 168909 on Linux is what MunichGamers - Rust Server runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does MunichGamers - Rust Server wipe, and how often?
MunichGamers - Rust Server has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 5 days 6 hours.
Player numbers
What position does MunichGamers - Rust Server hold in the rankings?
In the top 69% of all ranked servers, MunichGamers - Rust Server sits at #15,289 for player hours over the last seven days.
How many players does MunichGamers - Rust Server usually have?
The last sighting of MunichGamers - Rust Server was 2 days 5 hours ago, and it is offline right now. Over the past seven days, the average player count was 0.
Tags and filters
What do MunichGamers - Rust Server's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): Its slot count is 40; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon are the tags MunichGamers - Rust 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.
Which lists and filters on Rust Server Score show MunichGamers - Rust Server?
These Rust Server Score lists count MunichGamers - Rust Server among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Rules and settings
What settings and rules apply on MunichGamers - Rust Server?
Nothing in the name of MunichGamers - Rust Server states a gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
Which map is in play on MunichGamers - Rust Server?
A procedural map of size 3,500 and seed 1337, generated by the game, is what MunichGamers - Rust Server runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join MunichGamers - Rust Server?
To connect, start Rust, press F1, and type client.connect 93.104.168.84:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://munichgamers.de.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max playersIts slot count is 40.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: 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 standing (F); population is the one to work on (F).