Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····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.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 18 Sep, 15:49 UTC39d ago
1
–
running
1
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 reports the location a server gives; it does not check where the machine actually is. Find it at 90.154.71.212:28015.
How reliable is LocalRustServer1337, and is it up?
At this moment, LocalRustServer1337 is offline; the last time it was seen was 39 days 13 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
Which Rust version is LocalRustServer1337 running?
The server LocalRustServer1337 is on Rust network protocol 2633 and build 162929 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does LocalRustServer1337 reset?
The record holds too few of LocalRustServer1337's wipes to tell its 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 39 days 13 hours.
What happens on LocalRustServer1337 when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 0 hours into the latest wipe.
Population
What position does LocalRustServer1337 hold in the rankings?
In the top – of all ranked servers, LocalRustServer1337 sits at #13,259 for player hours over the last seven days.
Is LocalRustServer1337 a busy server?
The last sighting of LocalRustServer1337 was 39 days 13 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on LocalRustServer1337?
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; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs162929 (Build): This runs on build 162929; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server are the tags LocalRustServer1337 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.
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.
Rules and settings
What settings and rules apply on LocalRustServer1337?
The name of LocalRustServer1337 gives no gather rate. With no change from the game default, groups take up to 8 players. 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. The server does not run VAC, Valve's anti-cheat.
Which map is in play on LocalRustServer1337?
The game generates a procedural map for LocalRustServer1337.
How to join
What is the way to join LocalRustServer1337?
Enter client.connect 90.154.71.212: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?,v2633,gmrust,cs162929,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.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs162929
BuildThis runs on build 162929.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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.
Not enough figures yet to write a report. Check back after a few days on the list.