Working its way up from the back of the class: #14,538 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
39/ 100
F
Slipped a little: down 3,316 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
No daily history yet.
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 61% 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
You won't see a region from milky, whose region code is us3. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 186.247.161.119:28015.
Is milky up, and how steady is its uptime?
The server is down: milky is offline now, with the last sighting 31 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 27 September 2026, Rust Server Score saw it for the first time.
On what Rust version does milky sit?
The server milky is on Rust network protocol 2621 and build 142867 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does milky wipe its map?
milky has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 41 days 11 hours have passed since this world was made.
Player numbers
Where does milky sit among Rust servers?
Over the last seven days, milky has #14,538 for player hours, in the top 61% of all ranked servers.
Is milky a busy server?
milky is offline at the moment; the last time it was seen was 31 days 12 hours ago.
Lists and filters
How should you read the tags on milky?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp69 (Max players): The server holds 69 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2621 (Protocol): The game protocol is 2621, so your game must match that version to join; cs142867 (Build): The game build is 142867; ptrak (Networking): The network layer is RakNet, standard for the game; $rus3 (Region code): Region code: us3 are the tags milky 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 Rust Server Score filters and lists feature milky?
These Rust Server Score lists count milky among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
Which rules does milky enforce, and what are its settings?
You will find no gather rate in the name of milky. The default of 8 players applies as the group cap. survival is the mode 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. VAC, Valve's anti-cheat, is not enabled.
Can you tell me which map milky uses?
milky runs a procedural map, which the game generates.
Connecting
How do you get onto milky?
To connect, start Rust, press F1, and type client.connect 186.247.161.119:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp69,ptrak,$rus3,v2621,gmrust,cs142867,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp69
Max playersThe server holds 69 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2621
ProtocolThe game protocol is 2621, so your game must match that version to join.
cs142867
BuildThe game build is 142867.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$rus3
Region codeRegion code: us3.
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. Even marks across the subjects, from F to F.