Working its way up from the back of the class: #13,897 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
39/ 100
F
Slipped a little: down 3,034 places this week. Nothing a good wipe can't fix.
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.
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 23h.
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
#1 Rust Server Tool leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 79.254.175.52:28015 is the address to use.
How reliable is #1 Rust Server Tool, and is it up?
The server is down: #1 Rust Server Tool is offline now, with the last sighting 25 days 6 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 3 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 166586 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does #1 Rust Server Tool reset?
the force wipe gives the basis for estimating #1 Rust Server Tool's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 26 days 1 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Player numbers
Where does #1 Rust Server Tool sit among Rust servers?
In the top 61% of all ranked servers, #1 Rust Server Tool sits at #13,897 for player hours over the last seven days.
What does the population on #1 Rust Server Tool look like?
It has been 25 days 6 hours since #1 Rust Server Tool was last seen, and it is offline right now.
Tags and filters
What do #1 Rust Server Tool's tags stand for?
gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166586 (Build): Build number: 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags #1 Rust Server Tool publishes, and the game's server browser reads them. 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.
Which lists and filters on Rust Server Score show #1 Rust Server Tool?
Rust Server Score lists that include #1 Rust Server Tool: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
What settings and rules apply on #1 Rust Server Tool?
Nothing in the name of #1 Rust Server Tool states a gather rate. With no change from the game default, groups take up to 8 players. pve is the mode here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
#1 Rust Server Tool runs which map?
#1 Rust Server Tool runs a procedural map, which the game generates.
Getting in
How do you get onto #1 Rust Server Tool?
Enter client.connect 79.254.175.52: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,^p,gmvanilla,cs166586,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max playersIts slot count is 100.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166586
BuildBuild number: 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
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.