Working its way up from the back of the class: #16,111 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
24/ 100
F
Lost ground: down 8,251 places this week. A strong wipe could turn it round.
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.
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.
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 71% 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
No region is published for MACRO Local K. Rust Server Score takes the server's word for its location and does not trace the hardware. 45.183.80.187:28015 is the address to use.
Is MACRO Local K up, and how steady is its uptime?
At this moment, MACRO Local K is offline; the last time it was seen was 33 days 18 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 23 September 2026, Rust Server Score saw it for the first time.
Which Rust version is MACRO Local K running?
You will find MACRO Local K on Rust network protocol 2633 and build 163207, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does MACRO Local K wipe its map?
There are too few wipes on record for MACRO Local K 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. It has been running its current world for 53 days 18 hours.
Player count
Where does MACRO Local K place in the wider field of Rust servers?
In the top 71% of all ranked servers, MACRO Local K sits at #16,111 for player hours over the last seven days.
What does the population on MACRO Local K look like?
MACRO Local K is offline at the moment; the last time it was seen was 33 days 18 hours ago.
Tags
What is meant by the tags on MACRO Local K?
You'll see MACRO Local K tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp8 (Max players): Its slot count is 8; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs163207 (Build): This runs on build 163207; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does MACRO Local K appear in the Rust Server Score lists and filters?
Rust Server Score lists that include MACRO Local K: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does MACRO Local K enforce, and what are its settings?
You will find no gather rate in the name of MACRO Local K. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. You are not covered by VAC, Valve's anti-cheat.
Which map is in play on MACRO Local K?
MACRO Local K runs a procedural map, which the game generates.
How to join
How should you connect to MACRO Local K?
To connect, start Rust, press F1, and type client.connect 45.183.80.187:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp8,ptrak,$r?,v2633,gmrust,cs163207,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp8
Max playersIts slot count is 8.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163207
BuildThis runs on build 163207.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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.