Working its way up from the back of the class: #16,709 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.
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 30 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% 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
Which region is Midwest Rust 2X [ Solo/Duo/Trio ] Weekly based in?
You'll find no region listed by Midwest Rust 2X [ Solo/Duo/Trio ] Weekly. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 168.100.61.69:28015 is the address to use.
How dependable is Midwest Rust 2X [ Solo/Duo/Trio ] Weekly, and is it online at the moment?
At this moment, Midwest Rust 2X [ Solo/Duo/Trio ] Weekly is offline; the last time it was seen was 28 days 5 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 30 September 2026.
What Rust version is Midwest Rust 2X [ Solo/Duo/Trio ] Weekly on?
You will find Midwest Rust 2X [ Solo/Duo/Trio ] Weekly on Rust network protocol 2633 and build 165217, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Midwest Rust 2X [ Solo/Duo/Trio ] Weekly reset?
There are too few wipes on record for Midwest Rust 2X [ Solo/Duo/Trio ] Weekly to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 28 days 6 hours.
Population
What position does Midwest Rust 2X [ Solo/Duo/Trio ] Weekly hold in the rankings?
In the top 70% of all ranked servers, Midwest Rust 2X [ Solo/Duo/Trio ] Weekly sits at #16,709 for player hours over the last seven days.
What does the population on Midwest Rust 2X [ Solo/Duo/Trio ] Weekly look like?
It has been 28 days 5 hours since Midwest Rust 2X [ Solo/Duo/Trio ] Weekly was last seen, and it is offline right now.
Tags
What is meant by the tags on Midwest Rust 2X [ Solo/Duo/Trio ] Weekly?
The game's browser takes its cue from the tags Midwest Rust 2X [ Solo/Duo/Trio ] Weekly has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): This runs on build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Midwest Rust 2X [ Solo/Duo/Trio ] Weekly appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Midwest Rust 2X [ Solo/Duo/Trio ] Weekly among them: 2x Rust servers, graded and Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Gather rate: 2x.
Server rules
Which rules does Midwest Rust 2X [ Solo/Duo/Trio ] Weekly enforce, and what are its settings?
Going by its name, Midwest Rust 2X [ Solo/Duo/Trio ] Weekly runs 2x gather. 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. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Midwest Rust 2X [ Solo/Duo/Trio ] Weekly runs which map?
Midwest Rust 2X [ Solo/Duo/Trio ] Weekly runs a game-generated procedural map at size 4,500, seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How do you get onto Midwest Rust 2X [ Solo/Duo/Trio ] Weekly?
To connect, start Rust, press F1, and type client.connect 168.100.61.69:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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.