Working its way up from the back of the class: #15,863 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 473 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.
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 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 72% 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 gap1.6 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Sat 3 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 16:26 UTC24d ago
1
–
running
0
Fri 2 Oct, 01:00 UTC25d ago
1
–
1.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
You'll find no region listed by Midwest Chesterfield. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 35.129.192.32:28015.
Is Midwest Chesterfield up, and how steady is its uptime?
You cannot join now: Midwest Chesterfield is offline, last seen 17 days 3 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 27 September 2026.
What Rust version is Midwest Chesterfield on?
The server Midwest Chesterfield is on Rust network protocol 2634 and build 167231 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Midwest Chesterfield wipe, and how often?
The record holds too few of Midwest Chesterfield's wipes to tell 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 24 days 6 hours.
What should you expect from wipe day on Midwest Chesterfield?
Across its recent wipes, the busiest moments averaged 1 players. 5 hours after the latest wipe began, the crowd hit its peak.
Population
Where does Midwest Chesterfield sit among Rust servers?
In the top 72% of all ranked servers, Midwest Chesterfield sits at #15,863 for player hours over the last seven days.
What does the population on Midwest Chesterfield look like?
Midwest Chesterfield is offline at the moment; the last time it was seen was 17 days 3 hours ago.
Lists and filters
What is meant by the tags on Midwest Chesterfield?
You'll see Midwest Chesterfield tagged with gmrust (Game mode): Survival in the standard Rust style; mp30 (Max players): The server holds 30 slots; 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; cs167231 (Build): The game build is 167231; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. 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 Rust Server Score filters and lists feature Midwest Chesterfield?
Rust Server Score lists that include Midwest Chesterfield: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
How is Midwest Chesterfield set up, and what rules does it keep?
The name of Midwest Chesterfield gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode 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. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Midwest Chesterfield uses?
The game generates the procedural map on Midwest Chesterfield at size 4,000 with seed 20260927. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How do you get onto Midwest Chesterfield?
Enter client.connect 35.129.192.32:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp30,ptrak,$r?,v2634,gmrust,cs167231,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp30
Max playersThe server holds 30 slots.
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.
cs167231
BuildThe game build is 167231.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 momentum (D); standing is the one to work on (F).