Working its way up from the back of the class: #13,782 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
33/ 100
F
Lost ground: down 4,698 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 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h.
The 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 #1. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 37.135.183.49:28015 is the address to use.
How reliable is #1, and is it up?
At this moment, #1 is offline; the last time it was seen was 22 days 19 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 5 October 2026, Rust Server Score saw it for the first time.
On what Rust version does #1 sit?
The server #1 is on Rust network protocol 2634 and build 166652 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does #1 reset?
The estimate for #1's next wipe comes from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 27 days 3 hours. Its tags list a monthly wipe schedule.
Population
Where does #1 sit among Rust servers?
Over the last seven days, #1 has #13,782 for player hours, in the top 61% of all ranked servers.
Is #1 a busy server?
It has been 22 days 19 hours since #1 was last seen, and it is offline right now.
Tags and filters
How should you read the tags on #1?
You'll see #1 tagged with gmvanilla (Game mode): This is vanilla survival; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month in the browser, which picks them up from the server. 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 #1 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count #1 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; Server tag: Monthly ^m; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
What settings and rules apply on #1?
You will find no gather rate in the name of #1. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
#1 runs which map?
#1 runs a procedural map, which the game generates.
Getting in
How do you get onto #1?
Enter client.connect 37.135.183.49: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 asmp5,ptrak,$r?,v2634,^m,gmvanilla,cs166652,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp5
Max playersThe server holds 5 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
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.