A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
57/ 100
C−
Working its way up from the back of the class: #9,592 on player hours.
Uptimehours on the list, last 48
6/ 100
F
Attendance needs work: on the list only 3 of the last 48 hours.
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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (C−); uptime 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.
AveragePeak
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 43% 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 LocalRustServer1337. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 37.29.22.70:28015.
Is LocalRustServer1337 up, and how steady is its uptime?
You cannot join now: LocalRustServer1337 is offline, last seen 44 hours ago. For the last 1 full day, it was up 0 of 24 hours, or 0% of the time. It was first seen by Rust Server Score on 26 October 2026.
On what Rust version does LocalRustServer1337 sit?
The server LocalRustServer1337 is on Rust network protocol 2635 and build 168909 under Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
When does LocalRustServer1337 wipe, and how often?
LocalRustServer1337 has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 2 days 12 hours have passed since this world was made.
Player numbers
Where does LocalRustServer1337 sit among Rust servers?
Over the last seven days, LocalRustServer1337 has #9,592 for player hours, in the top 43% of all ranked servers.
How many players does LocalRustServer1337 usually have?
It has been 44 hours since LocalRustServer1337 was last seen, and it is offline right now. Averaging 1 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 11:00 UTC, averaging 1 players.
Lists and filters
What do LocalRustServer1337's tags stand for?
You'll see LocalRustServer1337 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does LocalRustServer1337 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include LocalRustServer1337: 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 3 days.
Rules and settings
Which rules does LocalRustServer1337 enforce, and what are its settings?
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 and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server does not run VAC, Valve's anti-cheat.
Can you tell me which map LocalRustServer1337 uses?
The game generates a procedural map for LocalRustServer1337.
Getting in
How should you connect to LocalRustServer1337?
Enter client.connect 37.29.22.70: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 asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
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. Strongest in standing (C−); uptime is the one to work on (F).