Working its way up from the back of the class: #15,322 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
34/ 100
F
Lost ground: down 4,993 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in momentum (F); wipes are 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 70% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·····W·
·······
····
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 gap7.6 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2
The first 48 hours of its last wipes
Sat 17 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 10:46 UTC12d ago
2
–
running
1
Fri 9 Oct, 20:49 UTC19d ago
3
halved by day 2
7.6 days
2
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
No region is published for MILRUST. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 185.9.145.146:20904 is the address to use.
How reliable is MILRUST, and is it up?
The server is down: MILRUST is offline now, with the last sighting 11 days 8 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 9 October 2026.
What Rust version is MILRUST on?
The server MILRUST is on Rust network protocol 2634 and build 167781 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does MILRUST wipe, and how often?
There are too few wipes on record for MILRUST to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 12 days 8 hours.
What happens on MILRUST when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. 1 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 2 in the wipes where it did not hold.
Population
Where does MILRUST place in the wider field of Rust servers?
Over the last seven days, MILRUST has #15,322 for player hours, in the top 70% of all ranked servers.
How many players does MILRUST usually have?
It has been 11 days 8 hours since MILRUST was last seen, and it is offline right now.
Tags
What do MILRUST's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): 10 slots are available; 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; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here are the tags MILRUST publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show MILRUST?
These Rust Server Score lists count MILRUST among them: 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; Last wipe: In the last 2 weeks.
Rules and settings
What settings and rules apply on MILRUST?
Nothing in the name of MILRUST states a 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. Fighting and raiding between players are both allowed. 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.
Which map is in play on MILRUST?
MILRUST runs a procedural map, which the game generates.
Getting in
What is the way to join MILRUST?
To connect, start Rust, press F1, and type client.connect 185.9.145.146:20904. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max players10 slots are available.
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.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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. Strongest in momentum (F); wipes are the one to work on (F).