Working its way up from the back of the class: #16,964 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
30/ 100
F
Lost ground: down 6,735 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.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 27 Sep. 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
LocalRustServer1337 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 178.44.170.98:28015.
Is LocalRustServer1337 up, and how steady is its uptime?
The server is down: LocalRustServer1337 is offline now, with the last sighting 30 days 14 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 27 September 2026.
What Rust version is LocalRustServer1337 on?
The server LocalRustServer1337 is on Rust network protocol 2633 and build 165217 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does LocalRustServer1337 reset?
The record holds too few of LocalRustServer1337's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 30 days 17 hours.
Population
What position does LocalRustServer1337 hold in the rankings?
Over the last seven days, LocalRustServer1337 has #16,964 for player hours, in the top 71% of all ranked servers.
What does the population on LocalRustServer1337 look like?
The last sighting of LocalRustServer1337 was 30 days 14 hours ago, and it is offline right now.
Tags
How should you read the tags on LocalRustServer1337?
gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Its slot count is 10; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): The game build is 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set are the tags LocalRustServer1337 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.
Where does LocalRustServer1337 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count LocalRustServer1337 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.
Map and rules
How is LocalRustServer1337 set up, and what rules does it keep?
You will find no gather rate in the name of LocalRustServer1337. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. 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.
Can you tell me which map LocalRustServer1337 uses?
LocalRustServer1337 runs a game-generated procedural map at size 4,500, seed 1337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to LocalRustServer1337?
To connect, start Rust, press F1, and type client.connect 178.44.170.98:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersIts slot count is 10.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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.