Working its way up from the back of the class: #15,229 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
28/ 100
F
Lost ground: down 6,726 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 70% 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 13h.
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
You'll find no region listed by #1 Rust Server Tool. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 111.240.71.169:28015 is the address to use.
How dependable is #1 Rust Server Tool, and is it online at the moment?
The server is down: #1 Rust Server Tool is offline now, with the last sighting 14 days 10 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 12 October 2026.
Which Rust version is #1 Rust Server Tool running?
The server #1 Rust Server Tool is on Rust network protocol 2634 and build 167781 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does #1 Rust Server Tool wipe, and how often?
The estimate for #1 Rust Server Tool's next wipe comes from the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 26 days 19 hours. Its tags list a monthly wipe schedule.
Player numbers
Where does #1 Rust Server Tool place in the wider field of Rust servers?
Over the last seven days, #1 Rust Server Tool has #15,229 for player hours, in the top 70% of all ranked servers.
How many players does #1 Rust Server Tool usually have?
The last sighting of #1 Rust Server Tool was 14 days 10 hours ago, and it is offline right now.
Lists and filters
What do #1 Rust Server Tool's tags stand for?
You'll see #1 Rust Server Tool tagged with gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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 Rust Server Tool appear in the Rust Server Score lists and filters?
Rust Server Score lists that include #1 Rust Server Tool: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
How is #1 Rust Server Tool set up, and what rules does it keep?
Nothing in the name of #1 Rust Server Tool states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
#1 Rust Server Tool runs which map?
The game generates a procedural map for #1 Rust Server Tool.
How to join
How do you get onto #1 Rust Server Tool?
Enter client.connect 111.240.71.169: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 asmp100,ptrak,$r?,v2634,^m,gmvanilla,cs167781,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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.